You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
unitDefIDs happen to be assigned to unit defs in an alphabetical order according to their name, so many unit defs tend to receive the same unitDefID within a game even if the set of units changes between matches, e.g. armaak in BAR or amphaa in ZK are basically always ID 1 regardless of modoptions or updates. Newbie devs often notice this, and with most engine interfaces providing and expecting the numerical ID they often end up hardcoding numbers in wupgets instead of going via the name. Then later the ID changes after all and they get screwed.
Consider shuffling the IDs per-match to avoid this.
The text was updated successfully, but these errors were encountered:
unitDefIDs happen to be assigned to unit defs in an alphabetical order according to their name, so many unit defs tend to receive the same unitDefID within a game even if the set of units changes between matches, e.g.
armaak
in BAR oramphaa
in ZK are basically always ID 1 regardless of modoptions or updates. Newbie devs often notice this, and with most engine interfaces providing and expecting the numerical ID they often end up hardcoding numbers in wupgets instead of going via the name. Then later the ID changes after all and they get screwed.Consider shuffling the IDs per-match to avoid this.
The text was updated successfully, but these errors were encountered: