Namespace Eco.Gameplay.Systems.Chat

Classes

QACommands

UserRPCButtonTestExtensions

Interfaces

IChatClient

The interface that something needs to implement in order to perform chat commands. Used by User and RCON currently. Chat commands can accept either a User or an IChatClient

Difference between using User vs. IChatClient as the first argument include:

• If they accept a User, they are allowed to have full access to that User's interface, but those chat commands cant be called by headless clients like RCON
• If they accept an IChatClient, they have a limited set of properties (below) which they can access from the chatClient, but both Users in game and headless clients such as RCON can call these functions.

Generally if you only need to issue return displays and make modifications to the world, you should make the chat command accept IChatClient, so headless clients like RCON can call it.