You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 1, 2020. It is now read-only.
If a user manages to get an Invalid Captcha/Closes the window during registration.
The nick will no longer be able to be registered. "Cannot register, nick already registered."
Not able to /login to this nick as registration failed.
You will not be able to /reset this nick because it's not actually listed as registered.
Only resolution is currently to manually register them a password via SQL.
When Registration is completed:
Uncaught ReferenceError: addWarning is not defined(anonymous function) @ client.js:69
Update:
Looked into this further. Upon every registration this error is taking place.
Aside from that, registration is done before verification; Which is absolutely retarded. Upon failed verification the registered nick is not removed and therefore becomes inaccessible.
Disregard that, I suck cocks.
The text was updated successfully, but these errors were encountered:
If a user manages to get an Invalid Captcha/Closes the window during registration.
The nick will no longer be able to be registered. "Cannot register, nick already registered."
Not able to /login to this nick as registration failed.
You will not be able to /reset this nick because it's not actually listed as registered.
Only resolution is currently to manually register them a password via SQL.
When Registration is completed:
Uncaught ReferenceError: addWarning is not defined(anonymous function) @ client.js:69
Update:

Looked into this further. Upon every registration this error is taking place.
Aside from that, registration is done before verification; Which is absolutely retarded. Upon failed verification the registered nick is not removed and therefore becomes inaccessible.
Disregard that, I suck cocks.
The text was updated successfully, but these errors were encountered: