I published it here. My question is, as my map has a leaderboard, can other people mess up the bank somehow and cheat their way inside it like this?
I'd like to keep my map unlocked for people to learn from it, but then again, this is an issue.
Also can a different user post a new version of my map under the same name?
I'm guessing that every map has it's own bank so one shouldn't be able to mess up the bank of my map by publishing my map again, which will probably have a different name.
Banks are stored in the folder names after the publishers ID. So if a new person publishes the map, it will be the same bank name, but it will be in a different folder, so it shouldn't conflict.
However, if you're worried about people cheating their way onto the leaderboard, you might want to try encrypting your bank because anyone can go and find a bank and open it in notepad and edit it. It's simpler than writing a word document.
Banks are stored locally? This can't be true as I know that Blizzard has a limit on the Bank size of 10mb or something like that, which makes me think it is stored on their servers. I hope.
No its locally, if you for example play on the same account on a different PC you start fresh, unlesh you send your folder with and open it in the new folder for SC2.
That kinda sux. Well okay, I will obfuscate my banks.
But then again, if the map is unlocked one will be able to see how the obfuscation is done and that kinda ruins the whole deal.
Why did Blizzard decide to store the banks locally..
A map like Runling Run uses an encryption that is a great deterrent if you absolutely cannot have people getting into the bank. There are libraries here for it I'm pretty sure. If someone is willing to go through the effort to read complicated code to try to figure out how that encryption works, then they honestly should just be let to modify stuff how they please, cause it's just a game, it's not worth your effort to stop that much effort on their part. But encryption should stop 99% of any "hacking"
Just keep in mind that very few people care enough to hack bank files, and those that do care will hack your map no matter what (they will literally just open the map from the bnet cache, inject new triggers to give them what they want, run the map to generate a new bank file and use a signature forger to sign the bank file, there is no counter to this).
There is an alternative though. Put the leaderboard triggers in a mod, and publish it as locked. Now have your map reference this mod, and execute the triggers from there. This way your map will be unlocked while your leaderboard assets will be locked (keeping in mind the above, though).
I published it here. My question is, as my map has a leaderboard, can other people mess up the bank somehow and cheat their way inside it like this?
I'd like to keep my map unlocked for people to learn from it, but then again, this is an issue.
Also can a different user post a new version of my map under the same name?
I'm guessing that every map has it's own bank so one shouldn't be able to mess up the bank of my map by publishing my map again, which will probably have a different name.
Banks are stored in the folder names after the publishers ID. So if a new person publishes the map, it will be the same bank name, but it will be in a different folder, so it shouldn't conflict.
However, if you're worried about people cheating their way onto the leaderboard, you might want to try encrypting your bank because anyone can go and find a bank and open it in notepad and edit it. It's simpler than writing a word document.
New to the Editor? Need a tutorial? Click Here
Want data assets? Click Here
@fishy77: Go
Banks are stored locally? This can't be true as I know that Blizzard has a limit on the Bank size of 10mb or something like that, which makes me think it is stored on their servers. I hope.
@breakthewind:
No its locally, if you for example play on the same account on a different PC you start fresh, unlesh you send your folder with and open it in the new folder for SC2.
Its the same concept as the server, switching.
@AppleFee: Go
That kinda sux. Well okay, I will obfuscate my banks. But then again, if the map is unlocked one will be able to see how the obfuscation is done and that kinda ruins the whole deal. Why did Blizzard decide to store the banks locally..
@breakthewind: Go
A map like Runling Run uses an encryption that is a great deterrent if you absolutely cannot have people getting into the bank. There are libraries here for it I'm pretty sure. If someone is willing to go through the effort to read complicated code to try to figure out how that encryption works, then they honestly should just be let to modify stuff how they please, cause it's just a game, it's not worth your effort to stop that much effort on their part. But encryption should stop 99% of any "hacking"
New to the Editor? Need a tutorial? Click Here
Want data assets? Click Here
Just keep in mind that very few people care enough to hack bank files, and those that do care will hack your map no matter what (they will literally just open the map from the bnet cache, inject new triggers to give them what they want, run the map to generate a new bank file and use a signature forger to sign the bank file, there is no counter to this).
There is an alternative though. Put the leaderboard triggers in a mod, and publish it as locked. Now have your map reference this mod, and execute the triggers from there. This way your map will be unlocked while your leaderboard assets will be locked (keeping in mind the above, though).
@TyaArcade: Go
Wow I've never thought of doing it like that before. That's a cool way to do it. I may do that on future maps.
Though usually, I just try not to make features using banks that will have much of an impact on the game if hacked.
New to the Editor? Need a tutorial? Click Here
Want data assets? Click Here