- `writeUpdate` state is now stored in a global variable, so hotpatching doesn't crash it
- throttling now writes on the tail (so two throttled `writeUpdate` calls will write one update, not two)
- room settings, punishments, and helptickets are now throttled
`checkLearnset` has been renamed `checkCanLearn`.
`reconcileLearnset` has been replaced with `validateMoves`, which
bundles the actual `checkCanLearn` calls with the old
`reconcileLearnset`, making for a better name.
* Add multi-hit as a parameter to /ms
* Revert /help ds, add multihit to /help ms, fix TS
Code linted, let's go
'Tis coding at midnight
Save what had been tossed...
Bring back the older line...
The older line.
* ;-;
1465 passing (25s)
53 pending
> pokemon-showdown@0.11.4 posttest /home/partman/Documents/Code/pokemon-showdown
> npm run tsc
> pokemon-showdown@0.11.4 tsc /home/partman/Documents/Code/pokemon-showdown
> tsc
No idea why this wasn't caught.
* Fingers crossed
I wrote a `forceWrap` method to support break-word wrapping in table
cells for scavengers, but apparently code blocks need it too, so I'm
moving it to Utils.
Fixes#7854
- Polls were always starting as quizzes even when they weren't
- Hotpatching chat would reset poll/announcement timers
- A lot of bugs relating to minute/millisecond confusion in timer code
- Poll answers were called `questions` in the source code for some
reason; they've been renamed to consistently be `answer`.
- Refactor out an extremely unnecessary manual iteration
* Fix Autoresponder Refresh button bug
Currently if you go into ``/autoresponder view`` and choose to view autoresponder Stats, it opens a menu where no date is specified and you can choose a date from there. If, however, you press the Refresh button (where no date is specified), it opens a new page called "view-autoresponder-room-stats-" (note the extra hyphen at the end). This is because the "refresh" function is called (on line 458) with [date], which would equal [""]. This is a truthy value, unlike [] and unlike "". This patch changes the conditional statement to look at the first item in the array's truthfulness - it is either an empty string (falsey) or a non-empty string (truthy) - instead of always being truthy.
* Fix failing test
* Fix failing test
Sorry if this isn't ideal, it's certainly not as elegant as it originally was.
* Update responder.ts
* Update responder.ts
* Update responder.ts
* Chat monitor: Improve the handling of usernames
This PR ignores word boundaries in evasion regexes when filtering usernames, preventing the use of usernames with evasions of slurs in them.
* properly fix merge conflicts
