Register a free account today to Ignite your Adventure! Once signed in, you'll be able to participate with the Embers Adrift community. Your active account will also be the same account used to purchase, download, and login to the game.
It's best not to view this as a "relog timer". Instead, it should be viewed as something that gets refreshed periodically to ensure that you are the proper owner of your character when logged in. When someone crashes, their session key does not get gracefully removed from the database, which is why you have to wait for it to time out.
I understand all of that, but it needs to be reduced since it already take me lets say 30-45 sec to restart my PC and relog, players don't want to wait another minute or so. Could you separate those two functions?
We cannot. If we allowed for multiple session keys then the whole point of having a unique "key" that validates you are who you say you are goes out the window. Again, we can try reducing it a bit, but I also don't want to make it so people have trouble zoning.
Ok but how other games achieve that? I can crash in wow for example and be back in a second.
We are not WoW nor other games. This is how our security is setup. Also I don't know the answer to this question because I don't work for them
While I do appreciate the suggestions, our system is fully custom - there aren't any quick turnkey fixes for this. If we get too sloppy with this stuff it can lead to multiple of the same character being logged in at the same time which in turn would lead to some nasty issues with the database. To maintain the integrity of the db and prevent man-in-the-middle attacks (where someone might hijack your character) this is the system we designed. We knew that this relogging delay might occur from time to time but we deemed the inconvenience of a short wait far more desirable than the inconvenience of corrupted characters.