All game data is being applied twice, once by the mod you're running, and once by your test map calling your mod.
Let's say you have a set effect that creates a zergling and a roach.
Your mod tells the set effect to create these two units. It does so.
However since your test map is loading data from your mod a second time, it's duplicating the set effects and spawning a second zergling and roach.
Just assume that everything in the "effect" editor is being run twice, and it'll help. It spills over to other things, such as if you have an effect that applies a stackable behavior, it'll apply double the number of stacks.
Interestingly, the trigger editor seems to be immune to this.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Can you search for it now? I've refreshed the upload and I'm hoping that fixes it!
Edit: Just found it on page 15. Seems it's popularity was reset on US servers.
Is that still the case? I've only had a week-old email about it!
All game data is being applied twice, once by the mod you're running, and once by your test map calling your mod.
Let's say you have a set effect that creates a zergling and a roach.
Your mod tells the set effect to create these two units. It does so.
However since your test map is loading data from your mod a second time, it's duplicating the set effects and spawning a second zergling and roach.
Just assume that everything in the "effect" editor is being run twice, and it'll help. It spills over to other things, such as if you have an effect that applies a stackable behavior, it'll apply double the number of stacks.
Interestingly, the trigger editor seems to be immune to this.