This flag indicates that the client should not provide the option
to choose a new name, because all names will fail, rather than just
the one specified.
The new default is that the hostname contained in the first assertion
sent to the server will be accepted, and it (and the corresponding IP
address, if it is a domain name) will be added to tokenhosts.
In addition, I have also added a better error message in the case of
an invalid token hostname, which should point users to the relevant
documentation.
This commit requires the client to present its signed assertion from
the login server to the Pokemon Showdown server within one minute
after it was generated, rather than the previous allowance of two
days. A new signed assertion is generated for each action that
requires one, so this 60 second window is actually quite generous.
The console feature allows users with the 'console' permission
to execute arbitrary JavaScript in the context of the server
process. This allows for the execution of arbitrary code on the
local computer running the Pokemon Showdown server. As such,
the console permission is different from all other permissions
in that it gives power over more than just Pokemon Showdown.
It is likely that most users do not realise how powerful the
console permission is. As such, this commit alters the 'root'
permission so that it does not include the 'console' permission.
If a user intends to give a usergroup the console permission,
the server operator must add
console: true
to a usergroup's permissions in config.js.
This implementation also has the effect of disabling the
console feature on all current servers that pull this commit,
unless they explicitly enable it for a usergroup.
Please do not enable the console permission unless you fully
understand how powerful it is.
This one's less obtrusive since it doesn't require Zarel to appear as
an admin.
The purpose is to give Zarel the ability to provide tech support. As
always, comment it out if it makes you feel uncomfortable.
Battles now occur in a separate process.
Hopefully, this results in a substantial increase in network stability.
WARNING: Battle crashes are now practically unrecoverable.
