The client side for that chat resource is performed every frame. By using the button pressed logic, you will find that the actual resmon logic will run at 0 resmon.
GH:
The only file that needs to be updated is the client file. This is a client side only modification. Removed the code explanations and fluff, so there is maximum efficiency and Read Write times.
From all the things that you could’ve fixed from the chat resource, you decided to:
Remove code comments, which explain the code.
Remove function exports, which breaks all resources that depend on them.
Remove chatMessage event, which although deprecated, is still very much needed because a lot of resources, including escrowed ones, still rely on it.
Move the chat button to a custom keybind, which breaks all resources that want to block the chat button, and all resources that want to show the chat keybind as tooltip, and of course existing player’s chat keybind.
Still not remove the while-loop at least???
All of that to… cut 0.03ms… basically nothing.
Removed the code explanations and fluff, so there is maximum efficiency and Read Write times.
What do you mean by this? What Read Write times?
There are definetely things that can be improved in the chat resource, including bugs, but imo this ain’t it. This mostly breaks things, and it breaks things in ways that you can’t see at first, because people expect chat to work the same across servers.