SCRMaps
/
Sign in

DatEdit: the unit tab

Where a unit's own data is changed - and why what you change here does not reach units already on the map.

7 min read

DatEdit changes a unit type's own data. It looks like ScmDraft's unit settings but differs in one decisive way: what DatEdit holds is applied by triggers after the game has started.

So most of it does not reach units already placed on the map. Weapon, whether shields are enabled, and armour do reach them; the rest - including graphics, appearance and movement speed - do not. Not knowing this is hours of "I definitely changed it and it did not change".

So set in ScmDraft whatever ScmDraft can set. Hit points, armour, damage and cost can be set in both places, and changing them on the EUD side leaves the pre-placed units on the old value - all cost, no benefit.

Units to know
체력StarCraft counts hit points times 256. A 40 hit point unit is 10,240 inside.
생산 시간Frames. 24 frames is one real second; one StarCraft second at Normal is 15.
타격 수The 2 for a Zealot or 3 for a Firebat - and it does nothing. The real number of hits comes from the projectile count or the image script.

Giving a unit a weapon does not make it able to attack: only a unit with an attack motion attacks, and without one you get a dolmen. Shields are the same - add one to a unit whose image has no shield script and it crashes the moment it is attacked, which is crash list #24.

dat writes do not stay written
Sign in to track your progress