* Don't show "More..." button if the amount of results is already less than the max
* Properly pass on whether an exact search was performed to the prettifying function
* Improve phrasing in reaction to whether an exact search was performed
* Allow "More..." button to do a literal modlog query instead of always doing a username search
* Reorder some lines pertaining to the line count so they're not needlessly scattered all over the place
Before, if you wanted to specify how many results you wanted from a modlog search:
1. You could not search for any text
2. It was capped at 100 results
Now, we drop support for the old means of specifying lines, and instead we have a "More results..." button in modlog's UI.
We also support an undocumented means of specifying lines in the form of: /modlog [roomid], [search] [lines=integer], where integer is the number of lines of results you would like to see.
NOTE: We purposely are not documenting this behavior, as it is mostly made use of in the UI
We also update the help command here to reflect these changes.
* Change Scavengers multiple answer separator to a semicolon
Commas turned out to be problematic for many reasons, in particular
list answers where users could have submitted answers with commas as
separators - and if staff member didn't notice the commas, the hunt
could be easily started with wrong answer to frustration of a room.
This is the reason why this commit entirely disallows commas.
During the policy discussion with room staff, it was decided that
`;` was the best alternative separator. The other options that were
voted for were `/`, `\` and `,,`, but they weren't anywhere near
as popular as a semicolon.
Also for consistency with answers, list of hosts was changed to
also allow `;` as separator. However, there is no real reason to
stop accepting `,` here. Neither of `;` and `,` is allowed in
usernames so there is no problem with accepting both.
The error message was provided by Flerovium from Scavengers room,
thanks a lot :).
* Questions should be trimmed too
This should lower the number of reports in the thread that just turn out to be misunderstood uncommon mechanics, and hopefully will lessen the number of reports in Dev
without `&& !template.isMega`, it still gave uber megas in the first argument the error message about them not being able to mega evolve non natively even though they cant be used in real play at all
