Limiting AttachEffect.Cumulative

Registered by codyfun123

Add a tag that acts as a limit to AttachEffect.Cumulative=yes AttachEffects. If the number of AttachEffect instances on the target is already equal to the value of this tag, the existing instance with the lowest remaining duration will be modified/replaced to have the full duration again, instead of an extra instance being applied. The tag's default value will preserve the existing behavior where new instances are added without limit.

The tag may be called AttachEffect.Cap. This is the same name as the tag proposed in https://blueprints.launchpad.net/ares/+spec/attacheffect-stacking-duration. Because the stacking duration blueprint states that AttachEffect.Cap will not function as described when AttachEffect.Cumulative is enabled, this will act as an instance where the tag is reused for a similar but fundamentally separate purpose without creating a conflict.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
codyfun123
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

It probably doesn't need a new tag. This could be achieved by "expanding" AttachEffect.Cumulative= to accept numerical values, with "yes" and "no" being interpreted as "no instance limit" and "limit to 1 instance" respectively (which is basically what it does already, just allows a specific number for instance limit). - mevitar

I feel like there's a precedent that a tag name (at least, for a given section type) should never have more than one accepted type of value. Are there any blatant exceptions that I'm missing? -codyfun123

EMP logic (EMP.Threshold= in particular) is like that, so it's hardly a precedent. There might be something else that follows this pattern, but i don't remember right now. - mevitar

Ah, yes. I see. I also just remembered that the Pips= extension that Ares adds does the same thing. -codyfun123

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.