Synther, on 07 February 2013 - 01:06 PM, said:
But that's just ********. Why would you override something that hasn't even happened yet? The definition of override would be to stop the automated process. If the process hasn't been initiated yet, there's nothing to override! That's just stupid.
Thontor, on 07 February 2013 - 01:09 PM, said:
I'm pretty sure with every example of similar "override" mechanics in the real world... You override before the thing you are overriding has happened. Because if it happens, its kinda late to override it because it has already happened
Here is an example of the word "override" that has nothing to do with technology. In the United States, the way a bill becomes law, is it has to be passed by both houses of Congress, and then it goes to the President, who can either sign it into law, or veto it and return it to the Congress. If he vetoes it, it can still become law if both houses of congress vote in a two thirds majority for it. This has been called for a long time a "congressional override". Basically, the President has to act by vetoing the bill, and only then can the congress act by voting to override the veto. The Congress can not pass a bill twice to override a Presidential veto in advance. Just as the President cannot veto a bill, which itself is a kind of override, before a bill is even passed. The person you were responding to with that comment is completely correct, an override, when that word is used correctly, is always reactionary not preemptive as you claim. And if you and other people would like to keep arguing that, you're gonna have to provide some real world examples.
Now considering the example of the congressional override, which of the override systems that we've had and have in this game sounds more like that? The old one, where the emergency shutdown would start and try to shutdown your mech, and by pressing the o key, you could override that action and not shutdown. Or the new system, in which you press the o key, and you preempt the action of the emergency shutdown from shutting down your mech. The correct answer is the first one, because it is reactionary, which is the correct usage of the word override, while the second is preemptive, which is not. If way back when the override emergency shutdown was first put into a pc mechwarrior game, if it worked like this new one does, the person designing it probably would never have called it an override, he probably would have called it something else, like a delay or something.
Edited by Sajuk Kar, 11 February 2013 - 04:20 AM.