Besides being uncomfortable, when you are not in a rest place there is a long time you have to wait for relogging. Also, there is a system that keeps you online while you press Exit Now or ALT+F4. So, what happens if during that wait time server crashes? You still lose your data. ".save" command is instant.
Enable ".save" command
- Thread starter tristan
- Start date
Besides being uncomfortable, when you are not in a rest place there is a long time you have to wait for relogging. Also, there is a system that keeps you online while you press Exit Now or ALT+F4. So, what happens if during that wait time server crashes? You still lose your data. ".save" command is instant.
If you are completing quests, there will probably be an inn near, so it will instant.
20 seconds to save a preciate loot like a elite quest item or a Uncommon/Rare/Epic/Legendary item.
If im not wrong, this only happens when you exit game and you are in combat.
If it is implemented, everybody will make macros with each spell and this command. This will result in lag and server's saturation.
What we must do is to know what is causing these falls and correct it.
Most quests are very far of any Inn. If server crashes during the time you are on your way to turn in a quest to the quest giver who can maybe be near an Inn, you still can lose your progress.
During that 20 sec. server can crash. Bye bye item.
Yes, that's true. So for logging out, you need 20 sec plus not being in combat. If you loot something nice and can't get out of combat right away, you will need much more than 20 sec to log out. Uncomfortable, and unefficient.
As I've stated many times before on this very thread, I've seen and tested it before on several other private servers with 1.5k or more people, with no problems with latency. But, in case that with much more people it could generate latency problems, I think a good solution is have the command available with a few minutes of cooldown.