Yes, I wrote the scripts.
What I meant regarding the chat opening with **“I”** is that this is not normal/default behavior.
Natively, the default chat is opened with **“T”**. This behavior is hardcoded in the multiplayer itself, so under normal conditions pressing “T” is what should activate the default chat input.
If the chat opens with **“I”**, then it most likely means that the chat script/resource was not loaded or initialized correctly, or there is some other issue interfering with the normal behavior.
So when I said I wasn't sure why it opens on “I”, I meant that this is not behavior that normally happens and I cannot reproduce it with the default setup.
And yes, I meant **“I”**, not “T”.
Regarding point 3:
If a function or event is not documented on the wiki, then it means that we currently do not expose it as part of the public API.
`g1r:chatOutput` is not a native/public event that you should rely on or call directly. The communication between `outputChatBox` and the default chat resource is handled internally.
At the moment, chat customization is possible, but only within the limitations of the API that we currently provide.
So if there is no function, event or method described on the wiki for doing something, then there is currently no officially supported way to do it.
The chat system can be modified to some extent, but certain parts of it are intentionally not exposed yet. We may add more possibilities in the future, but for now you should only rely on the functions and events that are documented on the wiki.
What I meant regarding the chat opening with **“I”** is that this is not normal/default behavior.
Natively, the default chat is opened with **“T”**. This behavior is hardcoded in the multiplayer itself, so under normal conditions pressing “T” is what should activate the default chat input.
If the chat opens with **“I”**, then it most likely means that the chat script/resource was not loaded or initialized correctly, or there is some other issue interfering with the normal behavior.
So when I said I wasn't sure why it opens on “I”, I meant that this is not behavior that normally happens and I cannot reproduce it with the default setup.
And yes, I meant **“I”**, not “T”.
Regarding point 3:
If a function or event is not documented on the wiki, then it means that we currently do not expose it as part of the public API.
`g1r:chatOutput` is not a native/public event that you should rely on or call directly. The communication between `outputChatBox` and the default chat resource is handled internally.
At the moment, chat customization is possible, but only within the limitations of the API that we currently provide.
So if there is no function, event or method described on the wiki for doing something, then there is currently no officially supported way to do it.
The chat system can be modified to some extent, but certain parts of it are intentionally not exposed yet. We may add more possibilities in the future, but for now you should only rely on the functions and events that are documented on the wiki.