Feature: Basic Chat Functionality

[0xlsca]

The chat should be implemented.
Since there is a plethora of channels, only a selection should be considered for the moment so we have a good starting point to iterate on later.

Known channels are listed in the documentation and specifics can be read up on the linked steam guide.
Note: In general, chat messages can only be delivered to logged in (playing) players on the same server as the sender of a message.

The following channels should be included in the first iteration:

• 1: "zone"
  Receivers: Players in the same zone and on the same shard as the sender
• 6: "say"
  Receivers: Any player within a 50m range of the sender.
• 7: "yell"
  Receivers: Any player within a 150m range of the sender.
• 9: "army"
  Receivers: All players in the army of the sender

In the future, the following channels should be implemented:

• 3: "team"
  Receivers: Everyone in the same PVP-team as the sender
  Blocker: Missing team-management logic
• 2: "community"
  Receivers: Presumably all players on a shard
  Blocker: Missing community event implementation
• 4: "zone_lang"
  Receivers: The same as 1: "zone", limited to players using the same localization as the sender
  Blocker: Missing handling of the used localization of a player
• 5: "encounter"
  Receivers: Any other players currently taking part in the same encounter as the sending player
  Blocker: Missing encounter implementation
• 8: "whisper"
  Receivers: The target player specified in the whisper message. The target needs to be on the same server as the sender.
• 10: "officer"
  Receivers: Presumably all players in the army which have the "officer" rank
  Blocker: Confirmation needed
• 11: "debug"
  Receivers: Unknown
  Blocker: Investigations needed, it's unclear what this channel is used for. "debug" can mean many things.
• 12: "squad"
  Receivers: Every player in the squad of the sender
  Blocker: Missing squad implementation
• 13: "platoon"
  Receivers: Every player in the platoon of the sender
  Blocker: Missing platoon implementation
• 14: "friends"
  Note: System channel, players can not send to this channel. If a friend of the player logs on or off, the server sends a respective message to the player.
  Receivers: Individual players
• 15: "sin_speaker"
  Receivers: Presumably everyone on the same server
  Blocker: More investigation needed (lookup in the SDB!)
• 16: "sin_messenger"
  Receivers: Unknown
  Blocker: More investigation needed (lookup in the SDB!)
• 17: "admin"
  Receivers: The sender and all currently playing administrators, presumably bound to the server
  Note: Replies from admins are only visible to the sender
• 18: "unknown"
  Receivers: Unknown
  Blocker: Investigation needed
• Twitch Chat
  Blocker: Requires investigation
• PVP Lobby (TBD)
  Blocker: Requires investigation and an implementation of PVP lobbies / matchmaking

[eXpl0it3r]

I'd exclude army for now, given that would probably need a bigger setup to make it "useful" in a sense, i.e. supporting armies natively to begin with and setting up the relationship.

[zSleepwalker]

Wouldn't channel 18 be the Mentors chat?