- /trivia status no longer crashes if a username is provided as a target
- Timer mode no longer gives users scores of NaN
- /trivia start no longer displays that the game is starting in 30000 seconds,
- rather than 30 seconds
- Questions no longer appear as escaped html during games
- Corrected misleading documentation on why the noop methods of trivia exist.
Part 1 of the rewrite for the entire plugin
This is the rewrite of the classes and commands that handle running
trivia games. Several bugs that happened when running trivia games were
fixed, and unit tests were added to help keep them gone.
This was inspired by https://github.com/Zarel/Pokemon-Showdown/pull/2471
We are also removing the github-specific code from /htmlbox as well, removing the modchat alias of * for player, and we are giving room owners and leaders the roombot permission so they can promote to it.
By having ``return`` in these instances, the line ``room.update();`` never happens, so it gives the illusion that the server is lagging when it's probably not.
Lists the rooms that a user is muted in: http://i.imgur.com/xaO8sCx.png
Similar to "banned from", this can be useful to determine if a user is
hitting multiple rooms.
Unless we want to change the syntax for data tables like pokedex.js,
'constructor' will always exist as a table key.
These changes represent the bare minimum to prevent this from
causing too-weird behavior.
Among the newly added rules, there are quite a few intended to enforce
compliance of CONTRIBUTING.md-blessed idioms, as well as ensure
safe usage of classes and constant bindings.
We are also now enforcing usage of early return in commands.js,
which has 100% compliance as of fd2c45c.
The on-site FAQ and beginner's guide have been moved to a forum thread
to ease maintenance. This removes several entries from /faq because you
can't link to specific sections of a forum post. Unmatched targets now
link to the general FAQ post instead of giving error messages for
somewhat backwards compatibility with removed entries.
Before, if a button text spanned over one line, it would default to the OS buttons.
Using the button class with in-line CSS, this makes the buttons remain consistent regardless of how many lines the button spans for a poll question.
