Way to disable "server may be cheating" pukename message?

[foxx]

Is there some way to disable the scary server message, "server may be cheating, it's run puke [...]?" It's referenced in this ticket (http://zandronum.com/tracker/view.php?id=1031) however there hasn't been activity on it in some time so I didn't want to dredge up ancient history if not appropriate.

I'm writing a wrapper that basically works kinda like RCON, allowing a web server to run commands on a live-running game. Affecting the game directly via pukeable script is intentional and the players of this game are quite aware of it and expecting its behavior. With that said, it's annoying to have a message printed on the players screens and console every time it happens with essentially debugging-info.

Is there some way to mitigate this? Perhaps if not would it be acceptable perhaps to implement a one-time message when you join a server that it "could be cheating" and then leave it alone?

If not, is there a way to set a server to allow "cheats" but, perhaps via ACS script, send a notice to the server console if a player uses one? If possible this would be totally fine for my purposes.

If it's help I can link to the project but I don't want to give the impression I'm stumping for my own project.

[Hypnotoad]

Consider requestscriptpuke first, it may help. http://wiki.zandronum.com/RequestScriptPuke

[foxx]

Hmm, interesting, but it looks like this always has to be activated by a player. Unfortunately that'd imply that players were triggering the server-side scripts, something I need to expressly avoid. Am I not understanding the documentation correctly? It looks like the only way I'd be able to get that done is to have some sort of extra spectator user which I'm not entirely fond of either for a number of reasons.

[Dark-Assassin]

Maybe compile a personal server binary with that message removed?

[foxx]

Maybe compile a personal server binary with that message removed?

Yeah, I found the line in question that I'd need removed so I can just comment, make a patch, and then just do a custom build I think. I just wanted to see if perhaps we could just have a CLI option to disable it so I wouldn't have to go "off the reservation" and recompile.

Not a big deal, and I think that's probably going to be the way I'm going to have to go, it just would be nice if there's a "better" way to do it.

[Dark-Assassin]

If you want it to be an official feature, make a ticket on the tracker about it.
Though, it should be handled like sv_cheats and require a map restart to take effect.