Well thats very easy to figure out. Just look at the bank file XML and see which attributes get saved per unit. I believe the default unit store action is very basic though.
I know some things don't save in banks when a unit is saved.
I'm still lost on what exactly banks are used for. I know it stores information to be recalled later, but is it specifically meant to carry information from one map to the next in a campaign scenario? Single Player games store information in the game save, correct? So I guess it could be used to store character info in a multiplayer RPG style map.
Mille, you need to save specific parts of a unit in the bank? I assume it just saved the whole unit. Would you have to check the XML of the map script? Or of the bank file? I'm sure for you guys, bank protection is going to be a big issue, but for the common man, do you have any simple steps an average man could take to remove the whole "only need a players ID and mapmaker ID" for the folks over at d3scene to get into your bank file altered? Anything can be unbuilt, but to deter someone from creating a work around that could work for any player who downloads a fake map and entered a text trigger or something.
On the question by bigdon, a bank can save anything, from one game to another. It saves a text file on your computer which can only be opened by the map it was saved in, in the name of the account it was saved for. Mostly pretty secure. But yeah, you can save game stats, like wins, kills, points, played, ect. Simple things. You can also save far more complex things, yes, like everything in an RPG. If you plan to get into stuff like that, you want to make your own compression and decompression to keep bank file size small.
@GlornII: Go
Well thats very easy to figure out. Just look at the bank file XML and see which attributes get saved per unit. I believe the default unit store action is very basic though.
I'm still lost on what exactly banks are used for. I know it stores information to be recalled later, but is it specifically meant to carry information from one map to the next in a campaign scenario? Single Player games store information in the game save, correct? So I guess it could be used to store character info in a multiplayer RPG style map.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumMille, you need to save specific parts of a unit in the bank? I assume it just saved the whole unit. Would you have to check the XML of the map script? Or of the bank file? I'm sure for you guys, bank protection is going to be a big issue, but for the common man, do you have any simple steps an average man could take to remove the whole "only need a players ID and mapmaker ID" for the folks over at d3scene to get into your bank file altered? Anything can be unbuilt, but to deter someone from creating a work around that could work for any player who downloads a fake map and entered a text trigger or something.
On the question by bigdon, a bank can save anything, from one game to another. It saves a text file on your computer which can only be opened by the map it was saved in, in the name of the account it was saved for. Mostly pretty secure. But yeah, you can save game stats, like wins, kills, points, played, ect. Simple things. You can also save far more complex things, yes, like everything in an RPG. If you plan to get into stuff like that, you want to make your own compression and decompression to keep bank file size small.
Skype: [email protected] Current Project: Custom Hero Arena! US: battlenet:://starcraft/map/1/263274 EU: battlenet:://starcraft/map/2/186418