Cooldown Stack Refresh Policy Lookup
Replay explicit cooldown events under keep-current, reset-from-now or extend-expiry policy; expired cooldown starts anew, refresh may shorten remaining time, no hidden stacking charges or game-specific rules.
Description
Cooldown event policies differ when an event arrives before the current expiry.
Cooldown event policies differ when an event arrives before the current expiry. An event at expiry starts a fresh interval.1
Enter aligned nonempty nonnegative nondecreasing event times/durations, observation time at least the last event, and keep/refresh/extend policy. Expired events start a new cooldown regardless of policy. Return expiry history, final expiry and clipped remaining time.
When to use Cooldown Stack Refresh Policy Lookup
Use Cooldown Stack Refresh Policy Lookup when you need to evaluate the supplied records under the calculation and evidence rules below. Refresh may shorten a cooldown. No event generation or overlapping ability registry is maintained.
Prepare the supplied game state, observations and explicit variant settings. Follow the card, board, coordinate and state conventions in the calculation rules.
How to use Cooldown Stack Refresh Policy Lookup and understand its results
- Prepare the supplied game state, observations and explicit variant settings. Follow the card, board, coordinate and state conventions in the calculation rules.
- Enter eventTimesSeconds, eventDurationsSeconds, refreshPolicy, observedAtSeconds using the field table and calculation rules, then run the tool.
- Read expiryAfterEachEventSeconds, finalExpirySeconds, remainingCooldownSeconds. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| eventTimesSeconds | Event times seconds | list of number | Required |
| eventDurationsSeconds | Event durations seconds | list of number | Required |
| refreshPolicy | Refresh policy | string | Required |
| observedAtSeconds | Observed at seconds | number | Required |
Enter aligned nonempty nonnegative nondecreasing event times/durations, observation time at least the last event, and keep/refresh/extend policy. Expired events start a new cooldown regardless of policy. Return expiry history, final expiry and clipped remaining time.
active keep=end; refresh=time+duration; extend=end+duration Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| expiryAfterEachEventSeconds | Expiry after each event seconds | list of number |
| finalExpirySeconds | Final expiry seconds | number |
| remainingCooldownSeconds | Remaining cooldown seconds | number |
{
"input": {
"eventTimesSeconds": [
0,
5
],
"eventDurationsSeconds": [
10,
10
],
"refreshPolicy": "refresh",
"observedAtSeconds": 6
},
"output": {
"expiryAfterEachEventSeconds": [
10,
15
],
"finalExpirySeconds": 15,
"remainingCooldownSeconds": 9
}
} Limitations and assumptions
Refresh may shorten a cooldown. No event generation or overlapping ability registry is maintained.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use DPS Rotation Cycle Calculator: Damage per second over heterogeneous phases is a pooled ratio. Averaging phase DPS values would use different weighting. For a complementary task, use XP Quadratic Next-Level Curve: A quadratic experience curve assigns cumulative XP thresholds to levels. Integer arithmetic avoids rounding a boundary into the wrong level.
References
-
Cooldown Stack Refresh Policy Lookup — tool.io
Similar or alternative tools
- DPS Rotation Cycle Calculator
Damage per second over heterogeneous phases is a pooled ratio. Averaging phase DPS values would use different weighting.
- XP Quadratic Next-Level Curve
A quadratic experience curve assigns cumulative XP thresholds to levels. Integer arithmetic avoids rounding a boundary into the wrong level.