Posted: Sun Sep 28, 2025 11:31 pm Post subject:
Cumulative.MaxCount works per unit and not AttachEffect
Cumulative.MaxCount works per unit. As in if it was set to 3, A unit can stack the effect 3 times, not that the effect stacks only 3 times.
So if Unit A attaches an effect, then Unit B attaches the same effect, the effect wouldn't stack 3 times, it would stack 6 times.
I've made a workaround where I used the MultiWeapon system from Phobos and just made 3 weapons that can attach
(not Cumulative=yes so it wouldn't stack even if it got hit multiple times by the same effect)
effects that would check if it had already attached the effect, then if it does,
it would use the weapon with a higher AttachEffect and remove the lower one as well.
My unit has an Arcing=yes and Floater=yes. This makes the projectile slow. So if multiple units attack the same target,
it would use the same AttachEffect and instead of changing into the higher one.
That makes sense for Cumulative=no, but that is why I wanted to ask if this is how the Cumulative.MaxCount works.
Is Cumulative.MaxCount suppose to be per unit instead of being applied to the AttachEffect?
I wanted my AttachEffect to stack 3 times. But Cumulative.MaxCount makes it so each unit can stack it 3 times.
Workaround VS Cumulative.gif
Description:
The tint is for showing off that the workaround does only change. It's not what it would actually look like
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum