I have map with over 2mb compressed trigger size.
I think you reached the maximum lines in A trigger. You should break the trigger you last edited into 2 or more triggers.
If you actually reached the maximum triggers size (You may reach maximum in the future as your map seems quite large). Than you should use data tables instead of big array variables. (you can have unlimited sized data table...)
emm nope :p around 54-64k variables in data table and SC2 freeze saying it crashed and you need to restart. (i had message in game in debug area being in my own language even when sc2 is in English;side fact). I guess there must be a limit since it runs at server side, still is a nice secondary space
Did I just hit the max amount of triggers?
I do have a problem if so.
I have map with over 2mb compressed trigger size.
I think you reached the maximum lines in A trigger. You should break the trigger you last edited into 2 or more triggers.
If you actually reached the maximum triggers size (You may reach maximum in the future as your map seems quite large). Than you should use data tables instead of big array variables. (you can have unlimited sized data table...)
No, you aren't.
You have a trigger/function/action definition which is to long as Hookah604 said.
@Ahli634: Go Omfg your diablo map is fucking big.D
emm nope :p around 54-64k variables in data table and SC2 freeze saying it crashed and you need to restart. (i had message in game in debug area being in my own language even when sc2 is in English;side fact). I guess there must be a limit since it runs at server side, still is a nice secondary space
I split my two largest triggers into half, and it worked.
Thanks alot guys, I am now able to continue working on Amira. :)