Difference between revisions of "Talk:Query"
(→Session ID: new section) |
m (→Session ID) |
||
| Line 8: | Line 8: | ||
== Session ID == | == Session ID == | ||
| − | I just ran some quick tests, and Minecraft seems to expect it to be a 4-byte long valid UTF-8 sequence. If it is, the ID returns unchanged in the response, and if it isn't, each invalid byte is replaced by sequence <code>0xEF 0xBF 0xBD</code>, resulting in session ID sections that are longer than 4 bytes. It'd be nice if someone else could confirm this too. | + | I just ran some quick tests, and Minecraft seems to expect it to be a 4-byte long valid UTF-8 sequence. If it is, the ID returns unchanged in the response, and if it isn't, each invalid byte is replaced by sequence <code>0xEF 0xBF 0xBD</code> (replacement character, UTF-8), resulting in session ID sections that are longer than 4 bytes. It'd be nice if someone else could confirm this too. |
| + | [[User:Milesand|Milesand]] ([[User talk:Milesand|talk]]) 08:39, 8 September 2020 (UTC) | ||
Latest revision as of 08:39, 8 September 2020
Endianess
Here you state that "All data types are little-endian, with the exception of short". But in dinnerbones blog he says "Shorts are little-endian, whereas everything else is big-endian.". The UT3 definition talks very little about endianess but saying that a 4 byte integer is big endian which sort of supports the dinnerbone blog.
This is somewhat confusing.... What is it and please provide a link to the information..
- My mistake - fixed. Barneygale 14:44, 20 November 2011 (MST)
Session ID
I just ran some quick tests, and Minecraft seems to expect it to be a 4-byte long valid UTF-8 sequence. If it is, the ID returns unchanged in the response, and if it isn't, each invalid byte is replaced by sequence 0xEF 0xBF 0xBD (replacement character, UTF-8), resulting in session ID sections that are longer than 4 bytes. It'd be nice if someone else could confirm this too.
Milesand (talk) 08:39, 8 September 2020 (UTC)
