* 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
- spawning and setting up child processes is now handled by
ProcessManager#constructor rather than needing to be done manually for
each module that uses ProcessManager
- direct references to ProcessManager in ProcessWrapper were removed to
prevent dead ProcessWrapper instances from being leaked when hotpatching
- process-manager.js and verifier.js now use Typescript
add dragon ascent as a possible "Mega Stone", allowing pokemon to inherit Mega Rayquaza's properties (delta stream, its increased stats, etcetera). Also, at the request of Spandan, the banned stones check has been removed to let the command be less restrictive.
Previously, passing anything that started with a number to /dt would
make it look it up as a dex number.
This made it impossible to look up "10,000,000 Volt Thunderbolt".
Now, it has to be exactly a number and nothing else, to be considered
a dex number for the /dt lookup.
