Please make it so you have to type the entire command. ( or remove it entirely ) This feature request brought to you after getting killed because I was trying to type something like: /rs a ... and ended up dropping the s and getting "/saf" Thank you kindly, ps. rez please.
Sept 2019 *** Miscellaneous *** - The /safelock command now requires typing the full command in order to function to prevent accidental locking of the game. This should help in real life when kerrans are frisking your keyboard and manage to lock the game with a secret safelock password. https://everquest.allakhazam.com/story.html?story=37765 Perhaps this should be a bug report instead if yours is not working?
In that case I have no idea how I did it, but while in combat I was trying to type something in /rs and got "safe locked". It happens about once a year and every time I curse the one who thought this was a good feature.
You are the only person ... ever ... that I have heard of this happening to. [edit - after the patch] You must be very talented. Check your logs. If the game is taking a shortcut for /safelock, then as mentioned, you should bug it. Otherwise ... live with it once a year. Tunare knows there are many stupid things I do in game that I've just learn to accept and live with.
This was reported in 2019, as well as accidentally typing /sy instead of /say which would trigger the potentially dangerous /system command. Anyway, people kept reporting being somehow safelocked even after the patch.
I wonder if the command parser is not using the space as a deliminator and is just continuing to look down the line and when it sees all the letters anything after is the lock.
Since requesting the change, I had a few instances where I was still being safelocked. However, I've not had an issue since late 2021, thankfully. That's not to say any changes were implemented since the full command flag was placed on that has removed the chance of an accidental lock happening. It's a curious one for anyone who experiences the unintentional locking - just comes out of the blue.
essentially, you would type /safelock [random password] to lock and then /safelock [random password] to unlock
This happened to me on raids many times last year. I'd attempt to type in raid say and would actually be safelocking my pc with the password being whatever it was I just typed to the raid. It was fun times trying to figure out what exactly I just said to unlock my game without exiting out completely.
Which is really fun because you can't type /camp, /exit, even hitting the close button doesn't work when "safe locked". In my panic to get reset I open the task manager to kill the process.
You know you can just shift up and it puts the last text you type in chat. I don't know if safelock is hidden from that ability but I would guess it isn't so if you safelock by mistake and don't know the password just hit shift up and enter and it should unlock. For those who don't know about pulling up last command you can go through multiple lines you have typed doing this but not sure what the max limit is but I use it all the time when playing and I would assume anyone who is posting LFG or WTB message just uses shift up so they don't have to retype the entire command again.
