{"action":"created","issue":{"url":"https://api.github.com/repos/artemis-nerds/protocol-docs/issues/9","labels_url":"https://api.github.com/repos/artemis-nerds/protocol-docs/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/artemis-nerds/protocol-docs/issues/9/comments","events_url":"https://api.github.com/repos/artemis-nerds/protocol-docs/issues/9/events","html_url":"https://github.com/artemis-nerds/protocol-docs/issues/9","id":86382067,"number":9,"title":"Document changes in v2.2.0","user":{"login":"IvanSanchez","id":1125786,"avatar_url":"https://avatars.githubusercontent.com/u/1125786?v=3","gravatar_id":"","url":"https://api.github.com/users/IvanSanchez","html_url":"https://github.com/IvanSanchez","followers_url":"https://api.github.com/users/IvanSanchez/followers","following_url":"https://api.github.com/users/IvanSanchez/following{/other_user}","gists_url":"https://api.github.com/users/IvanSanchez/gists{/gist_id}","starred_url":"https://api.github.com/users/IvanSanchez/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/IvanSanchez/subscriptions","organizations_url":"https://api.github.com/users/IvanSanchez/orgs","repos_url":"https://api.github.com/users/IvanSanchez/repos","events_url":"https://api.github.com/users/IvanSanchez/events{/privacy}","received_events_url":"https://api.github.com/users/IvanSanchez/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":{"login":"rjwut","id":5790951,"avatar_url":"https://avatars.githubusercontent.com/u/5790951?v=3","gravatar_id":"","url":"https://api.github.com/users/rjwut","html_url":"https://github.com/rjwut","followers_url":"https://api.github.com/users/rjwut/followers","following_url":"https://api.github.com/users/rjwut/following{/other_user}","gists_url":"https://api.github.com/users/rjwut/gists{/gist_id}","starred_url":"https://api.github.com/users/rjwut/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rjwut/subscriptions","organizations_url":"https://api.github.com/users/rjwut/orgs","repos_url":"https://api.github.com/users/rjwut/repos","events_url":"https://api.github.com/users/rjwut/events{/privacy}","received_events_url":"https://api.github.com/users/rjwut/received_events","type":"User","site_admin":false},"milestone":null,"comments":10,"created_at":"2015-06-09T00:17:08Z","updated_at":"2015-07-20T16:49:12Z","closed_at":null,"body":"According to the forums, 2.2.0 is out. This means:\r\n\r\n* [X] New monsters\r\n * [x] Investigate whether new packet, or reuses the \"ZZ\" monster packet\r\n  * Whales and monsters are combined into a new creature object type. Wrecks are also considered creatures. Fields documented in the 5 July 2015 comment below.\r\n * [X] Investigate whether the space whale packet has changed to accommodate non-hostile monsters\r\n * See above\r\n * [X] Document the NSECT monster\r\n  * Same as all other creatures\r\n* [X] Anomalies are now \"pickups\"\r\n * [X] Investigate new fields\r\n * Documented in 5 July 2015 comment below\r\n* [ ] Working upgrade system (apparently some consoles can \"activate\" the pickups/upgrades)\r\n * [ ] Investigate now the upgrades packet works\r\n * [ ] Investigate how to trigger abilities from clients\r\n * [ ] Check whether the popup when a pickup is picked up comes from the upgrades packets, or from a separate (and already known) game server message.\r\n* [X] One new type of torpedo (plasma shock)\r\n * [X] One more enum\r\n * [X] Changes in the structure of the WeaponsUpdate packet"},"comment":{"url":"https://api.github.com/repos/artemis-nerds/protocol-docs/issues/comments/122946806","html_url":"https://github.com/artemis-nerds/protocol-docs/issues/9#issuecomment-122946806","issue_url":"https://api.github.com/repos/artemis-nerds/protocol-docs/issues/9","id":122946806,"user":{"login":"dthaler","id":6547784,"avatar_url":"https://avatars.githubusercontent.com/u/6547784?v=3","gravatar_id":"","url":"https://api.github.com/users/dthaler","html_url":"https://github.com/dthaler","followers_url":"https://api.github.com/users/dthaler/followers","following_url":"https://api.github.com/users/dthaler/following{/other_user}","gists_url":"https://api.github.com/users/dthaler/gists{/gist_id}","starred_url":"https://api.github.com/users/dthaler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dthaler/subscriptions","organizations_url":"https://api.github.com/users/dthaler/orgs","repos_url":"https://api.github.com/users/dthaler/repos","events_url":"https://api.github.com/users/dthaler/events{/privacy}","received_events_url":"https://api.github.com/users/dthaler/received_events","type":"User","site_admin":false},"created_at":"2015-07-20T16:49:12Z","updated_at":"2015-07-20T16:49:12Z","body":"Regarding, in the Comms packets:\r\n\"Priority (int)\r\n    Values appear to range from 0x00 (high priority) to 0x08 (low priority). In the stock client, this affects the message's background color.\"\r\n\r\nIs there any reason this needs to be called \"priority\"?  Based on observations of what messages actually appear with which values, I'm not sure that the numbers are actually in order by priority.  For example \"docking complete\" is sent on 0x04 is not really higher priority than accepting a docking request (0x05) or a notice of \"transfer complete\" (0x07).   Another example is that a base under direct attack (0x04) is not really lower priority than a taunt coming in from an enemy (0x00).  Can we call this number the \"channel\" instead of \"priority\"?"}}