well if you see any features from _debug mod that is working in linux versions
let me know, it will be for me with pleasure that i will correct it immedialty
but normally execpt i missed something, it should be just fine...
send me a message on my email if you find any problem
thanks for your time
yeah you can do all kinda of weird combos with the set saber move.... any move that causes you to pause at the end you can auto escape the freeze by hitting a bind of one of the debug move
my favorite combo with that is single saber side kick/lunge/saberbutt o-o
Don't post the actual commands please.
If you're right and "everybody knows them already" then there's no need.
But for now, just.... no.
Screw around with your cheats on your private server, and email the mod authors and tell 'em to fix their code up without the debug, if you want to make yourselves useful...
so, no one has this prob with basejka ? :rolleyes:
Apparently it's a simple matter of mods that forget to remove the "debug" functions when they compile.
Since that's all it seems to be, it shouldn't be a problem... except for those server admins who continue to (ignorantly) use the goofed up mods, leaving themselves open to exploit abuse.
i'm a bit confused, Renagade and Slider, how do we fix this in our mods? Do we just remove all functions with the #ifdef _DEBUG and #endif things around them?
All you have to do is compile your public releases in "final" configuration instead of "debug" mode.
I've known about these from JA Reloaded 1.2 for a long time, many people know about it.
There is definately no need to block each debug command individually in a mod, releasing final builds should do the trick. I believe this is how Ja 1.4 has fixed it (It's definately fixed, play on a server that runs it).
Originally posted by razorace
All you have to do is compile your public releases in "final" configuration instead of "debug" mode.
An important lesson for all mod makers then it sounds like!
I'm moving this to General Editing for future reference.