[Command] .killself

[HM9cPhABFctJ]

There are situations in which .unstuck will not help much; for example, a combat state which simply does not end in a place that does not allow you to leave while in combat. At which point an HS might also fail; particularly if you also happen to be in motion. Earlier today I was stuck like that in Throne of the Four Winds, automatically being bounced back and forth between winds. Never reaching a platform.

Fortunately, Fel Strike allowed me to jump just far enough to fall to my death.

Another case like that was in Blackwing Descent, where I somehow ended up stuck below the lava layer in Onyxia/Nefarian's central room. Literally, I could not swim to the surface because of collision detection. And because I was both in combat as well as in motion, I could not HS out. And the damage I received, if any at all, was so marginal it would've taken hours to kill me off. /camp and /quit also failed, because of the combat state. All I had left was hard killing the application with wineserver -k (I'm on Linux). This gave the server the time to flush my character's state. Upon logging back on, I was back in the room's entrance, barely alive.

So, it might be benefitial to implement a .killself command. Which would ignore combat state, movement state and whatever other state. As there simply are moments, particularly on a private server (although I have experienced some amazing bugs on retail as well, particularly during vanilla) where a death is the only way to recover control.

The method of killing off the character is incidental but something like Int.MaxValue damage would do an easy job of accomplishing it.

To prevent abuse, I would suggest something like a 2 to 5 minute cooldown.

[Power]

Definitely no, there are way too many ways in which this command could be exploited. (CD won't prevent anything)

Use unstuck from site, it works 100%. (alt-f4 => login to the character selection screen => unstuck => log on your char)