Fixing the /unstuck command

[[R] Nerva]

Okay, right now, the /unstuck command doesn't even work most of the time. In the past ten times I've needed to use it, it's worked maybe twice. That's an eighty percent failure rate, and that's honestly inexcusable. Each time it's failed, I've had to abort a mission completely due to being hopelessly stuck.

Here's the latest example of its failure:
https://steamcommunity.com/sharedfiles/filedetails/?id=1383942924
Worse yet, it's on a cooldown, which is irritating as hell.

So, my proposal is simple - the /unstuck command is no longer allowed to place you at any location within two Warframes' height of where you currently are. It must move you, and you must arrive on a valid, walkable location on the enemy's valid travel paths when used. This should vastly improve the performance of /unstuck and prevent it from "unsticking" you by placing you back right where you were, simply because the game deems your current location walkable even when it's clearly not.

If used while on cooldown, /unstuck should give you a prompt to burn a revive in order to be placed back at the beginning of the mission. Burning a revive prevents the command from being used as an easy escape. While placing you back at the beginning of the mission ensures that you go back to a valid, good location in the event of a catastrophic failure of the /unstuck command.