Map Limits
From Staredit Network Wiki
Revision as of 23:25, 20 March 2015 by DevliN (Talk | contribs) (1 revision imported: Restoring SC1 backup)
There are several limits that a mapper may encounter when creating maps (particularly UMS maps) for StarCraft. Most of these limits are numeric, such as the maximum amount of units that may exist during gameplay, or the number of locations a map may contain.
List of map limits
- Location limit: 254 (+ Anywhere = 255)
- String limit: 1024 in StarEdit/XtraEdit
- Variable in other editors, see Strings.
- Trigger limit: 65534 per player
- This is the number of triggers that a player in a map can have until StarCraft crashes while saving the game.
- Minimum working map size: 1x6
- Maximum working map size: 256x256
- StarEdit Unit limit: 1650
- CHK load Unit limit: 1700
- This does not include Start Locations.
- StarCraft Unit limit: 1700
- This does not include Start Locations.
- This limit is also known as map max.
- StarEdit Sprite limit: 250
- CHK load Sprite limit: 499
- This is the number of Pure Sprites StarCraft will load which obviously includes the sprites that are on some doodads like the tree doodads. If ever you over-pass this limit, StarCraft will ignore the last sprites created.
- StarCraft Sprite limit: 2500
- StarCraft Image limit: 5000
- StarCraft Weapon limit: 100
- Cutoff of 80 for Terran Valkyries.
List of general limits
- Unit HP range (1+3 Bytes)
- -8 388 608 to 8 388 607.5
- Protoss Shield range (2 Bytes)
- 0 to 65 535
- Mineral/Gas cost range (2 Bytes)
- 0 to 65 535
- Build time range (2 Bytes)
- 0 to 65 535
- Armor range (1 Byte)
- 0 to 255 (+255 with upgrades)
- Upgrades range (1 Byte)
- 0 to 255
- Resource range for Mineral Fields and Vespene Geysers (2 Bytes)
- 0 to 65 535
- Damage range (2 Bytes)
- 0 to 65 535 (+ 65 535 bonus * 255 upgrades)
- Number Value (Wait, Set Deaths, Set Mineral Amount, Scores, etc.) range (4 Bytes)
- -2 147 483 648 to 2 147 483 647 signed
- 0 to 4 294 967 295 unsigned