There are some map projects I'm working on and I would love to be able to use special commands to debug a game in a live environment. My fear of course is that any code I created could be done by another player to ruin the game for other people.
I did some search and saw some other threads concerning this where the ruling was pretty much "not possible" because banks could be hacked and chat commands could be found within a map's triggers.
With the latest patch I saw some notes about "cheat codes". Does this help to achieve what I want? Does the latest patch change anything that would allow me to use debug commands without other people being able to use them?
I heard someone on the IRC talk a day or two ago about how he would save a password in a bank that only he had, and the load that password (but encrypted or something so that it's not recognizeable in the maps script by anyone who doesn't have the bank) everytime you use a debug trigger as a condition. Its an idea at the very least.
Or, if you want to debug during a multiplayer game, create cheat code triggers, publish a new version, when youre done playing, disable the triggers and publish a new version again. No one will have enough time to hack your map (and use some sort of bank with an encrypted password as a condition), especially if you keep changing the password everytime you enable the triggers again for a new test.
There is no way to prevent others from using the same password. There is no way to do anything like
if (triggering player's name) == Lucavious
Then do whatever
I believe this is because blizzard wants to avoid this:
if ( picked player's name) == zeldarules28
then message player 'you suck, i hate u, dont play my map' + kick player from game
But like Almaity said, you can disable the trigger and then just enable real quick when you test the map. Or you could make the chat command you enter hard to guess (like "debug_command_87042") and you could just copy and paste that from a document on your cpu. Others can only use the command if they know what it is. So you should be safe if you change the code to trigger it each time you want to test and get rid of it whenever your done testing,
There are some map projects I'm working on and I would love to be able to use special commands to debug a game in a live environment. My fear of course is that any code I created could be done by another player to ruin the game for other people.
I did some search and saw some other threads concerning this where the ruling was pretty much "not possible" because banks could be hacked and chat commands could be found within a map's triggers.
With the latest patch I saw some notes about "cheat codes". Does this help to achieve what I want? Does the latest patch change anything that would allow me to use debug commands without other people being able to use them?
the cheat codes only work in test documents.
I heard someone on the IRC talk a day or two ago about how he would save a password in a bank that only he had, and the load that password (but encrypted or something so that it's not recognizeable in the maps script by anyone who doesn't have the bank) everytime you use a debug trigger as a condition. Its an idea at the very least.
Or, if you want to debug during a multiplayer game, create cheat code triggers, publish a new version, when youre done playing, disable the triggers and publish a new version again. No one will have enough time to hack your map (and use some sort of bank with an encrypted password as a condition), especially if you keep changing the password everytime you enable the triggers again for a new test.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThere is no way to prevent others from using the same password. There is no way to do anything like
I believe this is because blizzard wants to avoid this:
But like Almaity said, you can disable the trigger and then just enable real quick when you test the map. Or you could make the chat command you enter hard to guess (like "debug_command_87042") and you could just copy and paste that from a document on your cpu. Others can only use the command if they know what it is. So you should be safe if you change the code to trigger it each time you want to test and get rid of it whenever your done testing,