08-28-2015, 05:37 PM
I really like the idea to limit their bank until they validate. Its simple and, most likely, effective. The questions that remain are:
#1: What should the limit be?
The limit will determine how soon after registering they will have to validate.
#2: How to we communicate that there is a limit in place?
Upon registration, login, bank, only when they reach the limit? How do we phrase it?
We don't want to be to annoying but we really want them to validate.
What I also would really like is that all this can be done in one single session. Join, register and validate without having to rejoin like you have to do now. Would this be difficult to achieve?
Also, it should be possible to resend the validation mail to another mail address in case they mistyped theirs from within the gamemode.
We have to keep in mind that validating emails is a hassle but we are requiring it to offer them a service to reset their password, which otherwise would be way more difficult and time consuming for us.
#1: What should the limit be?
The limit will determine how soon after registering they will have to validate.
#2: How to we communicate that there is a limit in place?
Upon registration, login, bank, only when they reach the limit? How do we phrase it?
We don't want to be to annoying but we really want them to validate.
What I also would really like is that all this can be done in one single session. Join, register and validate without having to rejoin like you have to do now. Would this be difficult to achieve?
Also, it should be possible to resend the validation mail to another mail address in case they mistyped theirs from within the gamemode.
We have to keep in mind that validating emails is a hassle but we are requiring it to offer them a service to reset their password, which otherwise would be way more difficult and time consuming for us.