Hi there guys! After some optimization actions my bank refused to work correctly. That's why I want to clarify some aspects:
1) Bank name must be as string name like "MySupeDupperBank" or I can put this name as variable (the variable is more convenient)?
2) Can I preload bank as loop or I must personally preload it for each player (copy copy copy)?
3) Can I save/load info to/from bank as loop...or also personaly for each player (it's just awful)?
4) I must check signature after preload. Ok. But what I must to do with signature when I save my bank?
Rollback Post to RevisionRollBack
OMG! New hero in 'Heroes of the Storm' is Dustin Browder. Watch here!
Hi there guys! After some optimization actions my bank refused to work correctly. That's why I want to clarify some aspects:
1) Bank name must be as string name like "MySupeDupperBank" or I can put this name as variable (the variable is more convenient)?
2) Can I preload bank as loop or I must personally preload it for each player (copy copy copy)?
3) Can I save/load info to/from bank as loop...or also personaly for each player (it's just awful)?
4) I must check signature after preload. Ok. But what I must to do with signature when I save my bank?
1) I think it needs to be written out as preload is a fake-action. It makes the editor create a file in the map called "BankList.xml" which contains the bank name and player slot that needs to load the bank.
2) Due to the reason stated before, the preload cannot be a part of a loop.
3) Everything else regarding banks should work with variables and loops just fine.
4) When the signature option is enabled, saving the bank will create a signature for the file automatically. You only need to check the signature once. Also, you need to enable the signature once per game for that bank, else the game does not know if it should generate one or not.
Checking, if a bank is verified (which checks the signature), and dealing with broken banks is up to the map's author.
Btw, new banks are unverified, but they are empty. That is how you can differ between broken/edited banks and new players' banks.
Hi there guys! After some optimization actions my bank refused to work correctly. That's why I want to clarify some aspects:
1) Bank name must be as string name like "MySupeDupperBank" or I can put this name as variable (the variable is more convenient)?
2) Can I preload bank as loop or I must personally preload it for each player (copy copy copy)?
3) Can I save/load info to/from bank as loop...or also personaly for each player (it's just awful)?
4) I must check signature after preload. Ok. But what I must to do with signature when I save my bank?
1) yes do it once and save the bank in a varaible for use
2) preload is done in preload options of the editor (file menu where map info is; the trigger actions are deprecated)
3) i do it with a loop
4) there is a trigger action for bank options (contains only signature), just active it and there is a condtion in triggers to check if the signature is valid.
but if you google sc2 bank signature you will be able to download a software which validates any bank for you. if you need protection from the noobs you have to use custom encryption so only ppl who can read code are able to hack your bank.
@willuwontu: Go
I know about preload that way. But I tried preload several models and units in this way and the game still slowed down a bit when there was preloaded units. Therefore, I concluded that it's not working)
Rollback Post to RevisionRollBack
OMG! New hero in 'Heroes of the Storm' is Dustin Browder. Watch here!
Banks need to be synchronized in multiplayer which only occurs during the preload. All other actions that sound like they do the same thing (reload bank, etc) do not work in multiplayer so it is not possible to dynamically load banks during a session.
The "Preload Actions" are not really Galaxy, they are instead special macros which add the bank to the preload file. Hence they do not work in loops. All other Bank actions are Galaxy natives so do work in loops.
To use Bank signatures you enable the setting after loading the bank and then check the signature if it passes. If not it was tampered with by someone inexperienced otherwise it might have not. Due to the algorithm being standard SHA-1 everybody knows how to forge the signatures so you are advised to use some third party system to do extra encryption that is not easily guessed. For example my Imperial Bank system used SHA-1 hashes and AES Encryption with some arbitrary key logic. Such systems place bank security weakness on the actual map script itself (no out of the box third party program can break it) which is more than enough for all SC2 maps. People like myself can still break it from the actual map script but generally we do not because there really is no need for a well designed map (it spoils it).
Why would you pre-load the units? Do you have stuff that you needs to be loaded before triggers? If you don't know, then the answer is no.
Only preload the banks otherwise of course the game will slow down (you have data loaded into it that you are not using that is just sitting there taking up space)
Hi there guys! After some optimization actions my bank refused to work correctly. That's why I want to clarify some aspects:
1) Bank name must be as string name like "MySupeDupperBank" or I can put this name as variable (the variable is more convenient)?
2) Can I preload bank as loop or I must personally preload it for each player (copy copy copy)?
3) Can I save/load info to/from bank as loop...or also personaly for each player (it's just awful)?
4) I must check signature after preload. Ok. But what I must to do with signature when I save my bank?
OMG! New hero in 'Heroes of the Storm' is Dustin Browder. Watch here!
1) I think it needs to be written out as preload is a fake-action. It makes the editor create a file in the map called "BankList.xml" which contains the bank name and player slot that needs to load the bank.
2) Due to the reason stated before, the preload cannot be a part of a loop.
3) Everything else regarding banks should work with variables and loops just fine.
4) When the signature option is enabled, saving the bank will create a signature for the file automatically. You only need to check the signature once. Also, you need to enable the signature once per game for that bank, else the game does not know if it should generate one or not.
Checking, if a bank is verified (which checks the signature), and dealing with broken banks is up to the map's author.
Btw, new banks are unverified, but they are empty. That is how you can differ between broken/edited banks and new players' banks.
1) yes do it once and save the bank in a varaible for use
2) preload is done in preload options of the editor (file menu where map info is; the trigger actions are deprecated)
3) i do it with a loop
4) there is a trigger action for bank options (contains only signature), just active it and there is a condtion in triggers to check if the signature is valid.
but if you google sc2 bank signature you will be able to download a software which validates any bank for you. if you need protection from the noobs you have to use custom encryption so only ppl who can read code are able to hack your bank.
Use map -> preload info to preload your banks
Still alive and kicking, just busy.
My guide to the trigger editor (still a work in progress)
@willuwontu: Go I know about preload that way. But I tried preload several models and units in this way and the game still slowed down a bit when there was preloaded units. Therefore, I concluded that it's not working)
OMG! New hero in 'Heroes of the Storm' is Dustin Browder. Watch here!
Banks need to be synchronized in multiplayer which only occurs during the preload. All other actions that sound like they do the same thing (reload bank, etc) do not work in multiplayer so it is not possible to dynamically load banks during a session.
The "Preload Actions" are not really Galaxy, they are instead special macros which add the bank to the preload file. Hence they do not work in loops. All other Bank actions are Galaxy natives so do work in loops.
To use Bank signatures you enable the setting after loading the bank and then check the signature if it passes. If not it was tampered with by someone inexperienced otherwise it might have not. Due to the algorithm being standard SHA-1 everybody knows how to forge the signatures so you are advised to use some third party system to do extra encryption that is not easily guessed. For example my Imperial Bank system used SHA-1 hashes and AES Encryption with some arbitrary key logic. Such systems place bank security weakness on the actual map script itself (no out of the box third party program can break it) which is more than enough for all SC2 maps. People like myself can still break it from the actual map script but generally we do not because there really is no need for a well designed map (it spoils it).
@xxxNEARBYxxx: Go
Why would you pre-load the units? Do you have stuff that you needs to be loaded before triggers? If you don't know, then the answer is no.
Only preload the banks otherwise of course the game will slow down (you have data loaded into it that you are not using that is just sitting there taking up space)
Still alive and kicking, just busy.
My guide to the trigger editor (still a work in progress)