This article builds up on the existing, well-iterated specification of the communication protocol, aiming to detail the new developments and to provide a place for current and relevant discussion going forwards. For the core structure of the protocol though, the linked article remains the reference and although the discussion of that part moves out of necessity here as well, I see no need at the moment to copy its content too. If your question concerns the parts that are not directly described here, simply link precisely the part you are talking about, as needed.

The first further addition to the communication protocol enables chat in Eulora2 and is currently implemented and fully working. Worth making it explicit and right from the start that the chat in Eulora2 is by default encrypted ¹ whenever in transit and effectively authenticated as well, as it fully benefits from the whole existing infrastructure supporting the game’s world ². The WoT layer that is currently in the works will further provide the means to seamlessly keep out any automated noise, spam and the like while simultaneously enabling all users to effectively retain both control and accumulating benefits for everything that they put into participating. To the extent possible, I fully intend to further align the incentives as much as I can to support meaningful conversations that are worth re-reading, too – without any unnecessary restrictions and with fully owned responsibility as well as benefits for each participant, too. It is to my eye the only way in which having a chat capability is even worth it in the first place.

To add the chat capability to Eulora2, there are two new message types added in section 4 (Serpent packets), to request and receive chat lines, respectively, as well as one new action type added to section 7 (Character actions) describing the “Say” action. Using the same specification format, the newly added sections are the following:

4.9 Line Request

• uint8 (type ID, =12), followed by
• uint8 (count of lines), followed by
• n times uint32 (id of chatroom), uint64 (lowest line number requested), uint64 (highest line number requested), followed by
• padding to Serpent-message length

4.10 Line Info

• uint8 (type ID, =13), followed by
• text (line content), followed by
• uint32 (chatroom ID), followed by
• uint32 (speaker ID), followed by
• uint64 (line number), followed by
• uint64 (keccak hash of the line’s content and number), followed by
• padding to Serpent-message length

Updated 30 Oct 2024: ratings are now fully integrated and used in-game, being fully handled via the relevant Rating node in the data hierarchy. Consequently there is no need anymore to have dedicated message types for discovery and retrieval, so the “rating request” and “rating info” message types below are removed entirely. See in any case the protocol specification for the full protocol.

4.11 Rating Request

• uint8 (type ID, =14), followed by
• uint8 (count of requests), followed by
• n times uint32 (source ID), uint32 (target ID), followed by
• uint16 (message count), followed by
• padding to Serpent-message length

4.12 Rating Info

• uint8 (type ID, =15), followed by
• text(rating comment ³), followed by
• uint32 (source ID), followed by
• uint32 (target ID), followed by
• uint8 (rating value ⁴ ), followed by
• uint16 (message count), followed by
• padding to Serpent-message length

7.9 Say ⁵:

• uint8 (type ID, =9), followed by
• text (line content), followed by
• uint32 (room ID), followed by
• uint64 (keccak hash of the line’s content)

7.10 Rate

• uint8 (type ID, =10), followed by
• text (rating comment), followed by
• uint32 (target ID)
• uint8 (rating value)

A line of chat in Eulora2 has a maximum length of 1445 characters. This is fixed and unchangeable as it is the maximum that fits in a 4.10 message (which has the least space for the line’s content out of all the messages relevant to chat lines and therefore effectively decides the *maximum* allowed line length). This limit is unlikely to be perceived all that often in practice but even if it is, note that it’s anyway more generous than most other existing chat protocols, irc included. Any client implementation is however entirely free to take its own approach as to how it handles this – whether it splits some user input into several lines if needed or whether it restricts input to this maximum of 1445 characters to start with, to give some concrete examples.

Beyond the above specific characteristics, for all intents and purposes chat rooms in Eulora2 are otherwise like any other game entities and thus the above additions to the communication protocol itself are both minimal and all that’s truly needed for a practical, working implementation. The speakers themselves are also characters (whether player controlled or not) in the game, hence fully described otherwise through the existing messages.

Messages 4.10 (Rating Request), 4.11 (Rating Info) and 7.10 (Rate) provide, respectively, a way to request and obtain from the server any desired ratings between two known entities in the WoT and to register/update one’s own rating of another. The comment part of a rating is meant to provide some context for the chosen value but as the value itself, the actual meaning and use is up to each individual and likely to be different from one person to another.

Worth noting that messages 4.10 and 4.11 are provided mainly as a basic and potentially last resort means of requesting and obtaining specific ratings. They are however quite unlikely to be the best choice for exploring or obtaining the full set of existing ratings, especially across a relatively large WoT, since each rating will require its own message and the traffic thus generated is to be paid for by the requesting client. A much cheaper and more convenient way to explore and update a local copy of the WoT will be provided in-game through an abstract object providing the full representation of the WoT in a single file and taking thus advantage of all the existing infrastructure, without requiring any new types of messages or other changes to the existing protocol.

Feel free to ask any relevant questions in the comments section below.

1. Serpent keys[↩]
2. Obviously, any of the users can otherwise make public the chat logs they have when and as they see fit but if you rely on something outside Eulora2 for that, it’s strictly between you and that provider, nothing to do anymore with either Eulora2 or the support and protection it provides.[↩]
3. Limited to at most 1445 characters, matching the maximum length of a chat line.[↩]
4. Valid rating values are integers between -10 and 10. For a given rating value here GR, the corresponding actual rating value RV is therefore calculated as: Min(GR, 20) – 10.[↩]
5. Note that this is an action and as such just a part of a 4.5 message, Client Action, where the overall message structure is specified.[↩]