I am however capable of making NEWB GameOp errors. I accidently set a time limit on "Game A" last night that was intended for "Game R". This kicked Farley out of the game, while his opponents continued to play.

My appologies to Farley and anyone else this affected.

How can I make it more "idiot proof", so to speak? ;) The Command Center says what game it is, but a remote connection doesn't show the game. I could maybe show that in the editor main screen. I've been confused at times as to which game I was editing.

I think I was just insulted j/k

NEVER UNDERESTIMATE THE INGENUITY OF COMPLETE FOOLS

A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. - Douglas Adams

Having the game name in the title would be nice, but not foolproof.
How about a popup warning, that you are about to edit a live game when the game has been activated?

Another nice option would be the ability to "Lock" a game. No edits of any kind could be preformed on a locked game and it would require an act of God to unlock it.

That's an interesting thought about locking a game. Of course, it may not take an act of God, but merely the act of a hacker (3rd party app developer) to modify a locked game. I think a lot about this issue of gameop trust and game tampering, and I think there really isn't a way to keep a motivated gameop from cheating. Things like locking the editor, I think they'll give players a false sense of security. Reputation really is the only thing that matters, I think. And even that can be damaged unfairly. But over time, a gameop will be proved good or bad by the general feel of the games on his or her server. If the gameop's friends always seem to win, players will get a sense of that. In an isolated case like this with your server, I think people are willing to give the benefit of the doubt.

Yeah, to take this to the next level, you would have to encrypt the data files when this option is enabled. I think that is a built in feature of MS SQL.
And even then a GameOp could still cheat by monitoring the NIC, and probably a dozen other things I haven't even thought of.
I would still like the ability to lock out tedit.

Depending on how well it's handled, it would decrease the potential for edit-based cheats, even if it can't eliminate them entirely. I will give it some more thought.