There's a public bank signer out there so I wouldn't just rely on bank signatures. Some additional form of encryption or obfuscation would help much more.
Just found a new limit. Not sure if this is already known (wasn't to me anyway). There seems to be a soft-cap on upgrade levels. You can't set the maximum level of an upgrade higher than 127. The hard-cap is 255 but going beyond 127 causes errors (for me, I couldn't set the level via triggers. The level stayed at 0). If you're planning on using lots of levels for your upgrades, increment accordingly.
I remember this limitation. I encountered another one with # of upgrades for an upgrade object. Adding another upgrade beyond the limit will cause the field to not save. Not sure if it's similar for other fields that store multiple attributes like +abilities. There's probably more kinds of data limitations that people can encounter reasonably.
Since you don't like data, here's some new data stuff. You can define "User Types" in the data editor and then modify them with triggers. Useful if you don't really like making absurdly big records and arrays to hold data for your map.
Found a topic from 2010 that says there's a 10,000 doodad limit. Don't know if Blizzard increased the limit since then. 10k doodads seems overkill for a map anyway but it doesn't seem too far-fetched for a large RPG map with pretty visuals.
http://www.sc2mapster.com/forums/development/map-development/10422-doodad-limit/
Nobody will ever reach the script size limit once 1.5 hits. (SCU @ 20% :D)
Memory limit is pretty big aswell, you will most likely never touch this.
Is the memory limit added up between all players in the map? Like let's say the map allocates an array of 100,000 integers and 15 human players. Will the map run into problems?
0
Anyone test to see if there's a new string length limit?
0
We'll ask blizz tomorrow for details on other limitations. Hopefully they answer.
0
There's a public bank signer out there so I wouldn't just rely on bank signatures. Some additional form of encryption or obfuscation would help much more.
0
@Clord: Go
what map is this
0
That's great, we don't get many developers directly answering questions.
0
Same problem here. I'm getting permission errors when I try to open them from the folder.
0
I remember this limitation. I encountered another one with # of upgrades for an upgrade object. Adding another upgrade beyond the limit will cause the field to not save. Not sure if it's similar for other fields that store multiple attributes like +abilities. There's probably more kinds of data limitations that people can encounter reasonably.
0
Is that HOMM 3? :)
0
What about point, region, and doodad limits?
Found a topic from 2010 that says there's a 10,000 doodad limit. Don't know if Blizzard increased the limit since then. 10k doodads seems overkill for a map anyway but it doesn't seem too far-fetched for a large RPG map with pretty visuals. http://www.sc2mapster.com/forums/development/map-development/10422-doodad-limit/
0
I agree, but I'd be nice to know the technical limitations of an SC2 map as well.
0
Any notable data limits?
Is the memory limit added up between all players in the map? Like let's say the map allocates an array of 100,000 integers and 15 human players. Will the map run into problems?
0
There's no bank limit on single player playing on battlenet?
0
Something like script limit, bank size limit, memory limit, etc. All things to consider when designing for a large ambitious project.
I'll start with a list based on 1.5:
0
This was a pretty common issue among novice map editors in the US/EU too.
0
Why would people get banned for using this?