Skip to content

Conversation

@KKosty4ka
Copy link
Contributor

@KKosty4ka KKosty4ka commented Dec 8, 2025

this should remove redundant code (server side command parsing) and allow scripts to use simple network functions instead of messing with command strings and fishing out responses from chat (like in #46)

also, this will make #111 easier (the server won't have to keep track of lang settings)

@KKosty4ka
Copy link
Contributor Author

KKosty4ka commented Dec 8, 2025

commands roughly in order of complexity:

  • /uptime
  • /whoami
  • /test
  • /delete
  • /worlds
  • /channel
  • /mute & /clearmutes
  • /tell
  • /block(user) & /unblock(user/all)

@KKosty4ka
Copy link
Contributor Author

KKosty4ka commented Dec 8, 2025

other things after that:

  • fix bug: using /tell adds extra entry to chatWriteHistory with only the message content
  • /passive can just be removed
  • completely move /help (it's done on the server, but the client hacks its commands into the message)
  • hide some commands (/worlds, /mute, /delete, etc.) from /help if the user can't use them
  • hide /uptime from /help if the user isn't an operator (even though they can use it..?)
  • really make sure chat ratelimits affect /tell
  • catch invalid commands on the client
  • add a response to invalid args (e.g. /block dsfds)
  • test blocking/unblocking even more thoroughly

@KKosty4ka
Copy link
Contributor Author

there's probably a better place for stuff i put into chat_mgr.js and utils.js

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant