Class Commitment
Why one object. F1 had 13 equip bursts in 84 ticks, seven of them spec-freeze-spec swaps inside 8 ticks, because only the style plan had a commitment window: the spec, freeze and Tele Block sets were re-decided from scratch every tick, and the spec set's equips renewed the MELEE style commitment on the way (its weapon is a melee weapon), so GEAR held "wearing Melee (committed)" on T56-T58 while srtutor prayed melee. Here the style and the episode are separate facts folded from the same plans:
- a plan whose commit set is a STYLE set (any style, the same one included) ends the episode, and
restarts
styleSinceonly when the style changes; - a plan whose commit set is a fixed plan (SPEC, FREEZE, TELEBLOCK) other than the running episode starts a new episode at its tick, and leaves the style alone; so does a SPEC commit after the running SPEC episode's spec fired (a second spec is its own episode, C3 review round 1);
- a new opponent resets both;
- a plan with no commit set changes nothing: a GEAR hold that names no set, and every hold the engine invents (the arbiter's deferrals, the stale-state filter) never starts, ends or renews anything.
ActionPlan.commitSet), which GEAR writes on every equip and every hold
it makes in a set, from PvPPolicy.GearPlan.set(): the style's name, or the fixed plan's kind.
Which breakers end a running episode is the policy's (PvPPolicy, D45, D47, D50): this is only the
record of what was committed to and since when.
Immutable and pure; no client reads, any thread. Lifted from ElorinPvP model/Commitment, with its
Style replaced by CombatStyle (same constant names, so the commit-set strings are unchanged).
-
Nested Class Summary
Nested Classes -
Field Summary
FieldsModifier and TypeFieldDescriptionfinal intThe opponent this commitment belongs to; -1 before the first.final Commitment.EpisodeThe fixed-plan episode running on top of it, and the tick it started.final intstatic final int"Never happened".final CombatStyleThe style we are committed to, or null; and the tick it was chosen.final int -
Method Summary
Modifier and TypeMethodDescriptionFolds one plan's commit set, decided ontickagainstopponentId(-1: no opponent in the state, which keeps the one we have).As above, withspecFiredTick: the tick the last spec fired as the decision on this state saw it, orNEVER(the engine passesNEVERwhile the orb is still latched, so an armed read lagging the fire is that spec, not a second one).static Commitmentempty()static Commitment.EpisodeThe fixed-plan episode a commit set names, or null for a style set.facing(int opponentId) The commitment as a decision on a state againstopponentIdreads it: the same one, or nothing when that is a different opponent from the one it belongs to (a new fight; -1 is no opponent, which is a one-tick blip and keeps it).summary()The commitment part of the capture's memory map (plan T9.5): plain data, never read back.intticksIntoEpisode(int tick) Ticks into the running episode attick, or -1 when none runs.toString()
-
Field Details
-
NEVER
public static final int NEVER"Never happened".- See Also:
-
style
The style we are committed to, or null; and the tick it was chosen. -
styleSince
public final int styleSince -
episode
The fixed-plan episode running on top of it, and the tick it started. -
episodeSince
public final int episodeSince -
against
public final int againstThe opponent this commitment belongs to; -1 before the first.
-
-
Method Details
-
empty
-
facing
The commitment as a decision on a state againstopponentIdreads it: the same one, or nothing when that is a different opponent from the one it belongs to (a new fight; -1 is no opponent, which is a one-tick blip and keeps it). -
after
Folds one plan's commit set, decided ontickagainstopponentId(-1: no opponent in the state, which keeps the one we have).commitSetis null for a plan that committed to nothing. No spec has fired:after(int, int, String, int)withNEVER. -
after
As above, withspecFiredTick: the tick the last spec fired as the decision on this state saw it, orNEVER(the engine passesNEVERwhile the orb is still latched, so an armed read lagging the fire is that spec, not a second one). A SPEC commit when the running SPEC episode's spec has fired (specFiredTick >= episodeSince, exactly whenPvPPolicy.specPhasestops calling the episode running) is a SECOND spec and starts its own episode here (C3 review round 1, C3-2). Without it a double spec (100% energy at a 50% cost) kept the first episode's start, so the second never had a window or the 60/75 band and flipped on the tick-by-tick start rules. -
ticksIntoEpisode
public int ticksIntoEpisode(int tick) Ticks into the running episode attick, or -1 when none runs. -
episodeOf
The fixed-plan episode a commit set names, or null for a style set. -
summary
-
toString
-