Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reimplement decay, recovery, and allow decay from captured state on control points #803

Closed
lefckntea opened this issue Feb 12, 2021 · 3 comments
Labels
feature New feature or request

Comments

@lefckntea
Copy link

image
make it so capture points have those

@Pablete1234 Pablete1234 added the feature New feature or request label Feb 12, 2021
@Pablete1234
Copy link
Member

1.9+ PGM had decay and recovery attributes added, which handled how quick points uncaptured or re-captured, replacing incremental (which simply resets progress to 0% if set to false, or doesn't change progress at all if set to true), additionally, it'd be nice to have a new flag for a point uncapturing on its own (if no one is standing on it) which was the original feature-request when decay & recovery were implemented, but got lost in the way

@lefckntea
Copy link
Author

*Also a way to have decay from captured state but not decay from an uncaptured state. So your progress while capturing a point stays but it can then automatically uncapture from the capture state

@Pablete1234
Copy link
Member

Then the proposal would be decay, recovery and owned-decay, which defaults to infinity.
decay applies when it's not owned and partially captured and no one stands on it (or only non-capturing competitors are on it)
recovery applies when it's owned and partially uncaptured, but the capturers all left (eg: no one on it anymore)
owned-decay applies when it's owned, and owning competitor isn't on it.

recovery and owned-decay are mutually exclusive as one is ticking up and the other ticking down, while owned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Development

No branches or pull requests

2 participants