Class PvpMovement
java.lang.Object
privbot.mechanics.PvpMovement
Detached proposal for the flagship PvP closing and step-out rules. No client reads or walking are performed.
Server ranges, freeze facts, reachability and timing must be supplied by the caller.
- Since:
- 1.2.0
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic final classstatic enum -
Method Summary
Modifier and TypeMethodDescriptionstatic PvpMovement.Decisiondecide(int tick, net.runelite.api.coords.WorldPoint us, net.runelite.api.coords.WorldPoint opponent, CombatStyle ourStyle, Boolean selfFrozen, Boolean walkInFlight, Boolean meleeThreat, Boolean opponentFrozen, Boolean pending, Boolean swingsUnseen, AttackTiming.Window stepWindow, int engageRange, int rangedDistance, long seed, Function<net.runelite.api.coords.WorldPoint, Boolean> reachable) Choose a destination using server planning tiles.
-
Method Details
-
decide
public static PvpMovement.Decision decide(int tick, net.runelite.api.coords.WorldPoint us, net.runelite.api.coords.WorldPoint opponent, CombatStyle ourStyle, Boolean selfFrozen, Boolean walkInFlight, Boolean meleeThreat, Boolean opponentFrozen, Boolean pending, Boolean swingsUnseen, AttackTiming.Window stepWindow, int engageRange, int rangedDistance, long seed, Function<net.runelite.api.coords.WorldPoint, Boolean> reachable) Choose a destination using server planning tiles. The supplied reachability function must use detached, same-tick collision evidence and return true only for a confirmed reachable destination. Unknown facts hold. Closing is before an attack; stepping out is after it, subject to the arbiter's conflict rules.
-