Security though obscurity,
doesn't last! (though it does sometimes last just long enough, most such cases haven't been in alpha for 4 years)
Some clever asshole will inevitably figure out one (or more!) of the commands, and
will use them to fuck-up a server.
(oh, and by stating how many buttons are used for one of them,
you've greatly increased the odds that someone is going to try, because now they have a defined goal)
(special circumstances? Yes, that helps, and you might get lucky and never have those commands get found without someone de-compiling the game)
That one (or more) of your hard-coded commands can
nuke a sector and
not log what it did, is not a "player" level problem, it's a problem of "the dev-team forgot that
documenting every step of every process is beyond critical". That
never, ever ends well.
(seriously, even something as simple as "command [insert name here] activated by: [insert name here]" is enough to know what just broke everything)
In fact, it is exactly the kind of "problem" where (were I the boss) I'd
fire the programmer who coded it, the idea-guy who thought it was a good idea, and instruct the rest of the team to
delete that command. Oh, and I'd cock-block the release of any new versions of the game which contain said code.
That, however, is a bit off of the original post, and I still fully support that post. (even though they've apparently changed the command in question to F1 + F8)
I absolutely agree with not publishing exploits, at least until they are fixed, but stuff that can happen by accident should be documented so accidents don't happen.
Documenting, for player/admin use, every key combination is both an excercise in futility (as many button combos WILL change) and one of
idiocy, because as
many people have been pointing out for literal centuries: People are assholes.
Now, the simplest, EASIEST way to stop all of this? (yes, I'm aware this isn't really either, but it absolutely works)
Locking the command to a specific hardware+software configuration.
EX: you have to be sitting at one of the dev-team's own work computers, with a specific external authentication program running, in order to execute the command,
on top of whatever special in-game circumstances are allso required. (for example, having run some other command first)
