Getting Stuck In Walls - Update /Stuck Command

So, I haven't been seeing this happen as much lately but it still does from time to time. 30s wait on /stuck command is waaaay too long of a timer for this command to work, considering you go on full respawn timer afterwards anyway. The /stuck command should work instantly if it's going to put us on a full respawn timer. Here is why:

• 30s + full respawn timer is more than enough time for your team to get screwed in a 4v5, such to the point that you can't come back from the bad play. In very balanced matches, where the nodes look 1 red, 1 blue, 1 neutral the entire match, a 45-60s instance of one person getting stuck in the walls is enough time for the opposing team get a triple cap, hold and win easily due to a bug that is not their fault.
• No one is going to abuse the /stuck command for purposes of trying to teleport back to the spawn or anything like that. There is no advantageous reason at all, for a player to ever use the /stuck command to instantly kill themselves for some reason of mobility around the map. The full respawn timer already prevents this from being useful for any reason other than actually getting unstuck from walls.
• Some of us do not have fast enough of PCs/Laptops to quickly log out and back in, to get around the 30s wait.

All you'd need to do is update /stuck command so it instantly downstates a player first and then when they bleed out, they respawn as normal.That or could the engine read when a vector is clipping into a wall? If it can, it should let players who are clearly identified as stuck in a wall, to instantly respawn.I don't know, you figure it out anet, but the 30s wait is too long.