Uses of Package
privbot.mechanics
Packages that use privbot.mechanics
Package
Description
ctx.* facades: inventory, bank, NPCs, widgets, and the other one-liners.Pure game-mechanic rules shared by plugins on every server: the same name and meaning on Impact, Elorin, Orion,
SpawnPK and Roat Pkz.
-
Classes in privbot.mechanics used by privbot.hooksClassDescriptionDetached historical damage distribution.Detects the local player's death and respawn by POLLING, one
DeathWatch.observe(java.lang.Integer, java.lang.Integer, net.runelite.api.coords.WorldPoint, int)call per game tick.A place to travel to: a name, a tile, how close counts as "there", and optionally a teleport to try first.Detached observations for one PvP decision.One fight frame plus newly observed local hits and graphics from the same client-thread batch.An immutable description of the gear a fight needs, the same on every server: what is worn, or what is carried.The tiles that hurt right now: timed ones (a graphic or a telegraphed attack that lasts a few ticks) and persistent ones (ground the fight never lets you stand on).A multi-tick piece of work a task node drives by callingJob.step(privbot.task.PrivTaskContext)once per pass until it is finished.Which ground items are worth picking up: by exact name, by id, or by stack value.One NPC reduced to what targeting and hazard maths need.What actx.pvp.snapshot(..)call should include.A detached copy of one tick of a PvP fight: the local player and the other players around it.Whatctx.recovery.afterDeathdoes once the player is back: an optional restock, then an optional trip back.What a restock should end with, the same on every server: an optional worn setup, an optional carried setup, whether to empty the backpack of unwanted items first, and an optional server preset to try before withdrawing.Value and death treatment for one item ID, from a caller-verified server-specific source.Freeze, Vengeance and Tele Block on us and on opponents, tracked from the graphics and animations a PvP snapshot reads each tick.What one call ofctx.sustain.maintaindid.What to eat and drink, and when.What onectx.loadouts.switchTo(..)call sent.Chooses which NPC to fight and sticks to it, so a bot does not flip between two targets every tick.What actx.threats.snapshot(..)call should include.A detached copy of one tick of a fight: the local player, the NPCs, projectiles and graphics around them, and the prayers that were checked.Explicit, caller-verified wilderness coordinate rules. -
Classes in privbot.mechanics used by privbot.mechanicsClassDescriptionMaps the cues an NPC shows when it attacks (its animation id, its projectile id) to the
CombatStylethe attack demands, plus the animation ids that are known to be harmless and how many cycles pass between an animation and its projectile launching.Collects cues.A step-out interval, inclusive at both ends.Decides when to drink another dose of a stat boost (overload, super combat, and so on) from the boost the account actually shows.Detached boosted and real combat levels; null means an individual read was unavailable.The three combat styles and the overhead prayer that blocks each.What the engine is committed to: a STYLE, and on top of it at most one fixed-plan EPISODE (plan fix 6, D44).A fixed-plan episode, or none.Detached current inputs from one decision tick.What one observation says.A place to travel to: a name, a tile, how close counts as "there", and optionally a teleport to try first.Observes a potion-family dose total before and after an accepted drink.Detached observations for one PvP decision.One fight frame plus newly observed local hits and graphics from the same client-thread batch.A bounded observation of one accepted food action, using a pre-send count and later detached inventory snapshots.How a move of theirs relates to a running freeze.An immutable description of the gear a fight needs, the same on every server: what is worn, or what is carried.One wanted item.Whether a setup describes worn equipment or carried supplies.What a carried item is for.A detached copy of one graphics object (a ground effect such as a falling rock or a pool) taken at the tick of aThreatSnapshot.The tiles that hurt right now: timed ones (a graphic or a telegraphed attack that lasts a few ticks) and persistent ones (ground the fight never lets you stand on).Detached recent health observations for the eat decision.A null style means the inputs do not establish a style; keep the current protection.Where aJobstands.One independently justified possible attack.KEEP also covers an accepted equip that has not yet appeared in the worn read; it is not a new dispatch.Which ground items are worth picking up: by exact name, by id, or by stack value.Builds aLootSpec.Detached result of a bounded NPC attacker scan.One NPC reduced to what targeting and hazard maths need.Conservative observed-swing timing for one locked opponent.The locked opponent.Facts about one observed player.An opponent's overhead prayer, debounced: "has their prayer blocked this style long enough to act on it".Combines a cue detector and confirmed-action history for our attack cycle.One player reduced to what a PvP fight needs.Planner settings.One unconfirmed toggle: the direction asked for and when it was sent.The original consume decision is explanatory; dispatch only non-held entries fromPvpActionPlanner.Plan.actions().Current decision facts.Detached inputs derived from the same observation.Immutable results for one sampled tick.What actx.pvp.snapshot(..)call should include.A detached copy of one tick of a PvP fight: the local player and the other players around it.Whatctx.recovery.afterDeathdoes once the player is back: an optional restock, then an optional trip back.Builds aRecoveryPlan.What a restock should end with, the same on every server: an optional worn setup, an optional carried setup, whether to empty the backpack of unwanted items first, and an optional server preset to try before withdrawing.Builds aRestockTarget.One physical entry.Value and death treatment for one item ID, from a caller-verified server-specific source.What aGearSetupstill lacks, compared with the player's real containers, the same on every server.One projectile in flight, reduced to what attack tracking needs.All flags are nullable: null is unreadable.One carried item matched to a missing equipment slot.WhatSustainPolicysays to do about hitpoints, prayer or a boost this tick.The kinds of answer.What one call ofctx.sustain.maintaindid.The kinds of outcome.What to eat and drink, and when.Builds aSustainPlan.A verdict on the outstanding switch.What onectx.loadouts.switchTo(..)call sent.Which NPCs count as a target: by name, by id, minus an ignore list, optionally inside an area.A verified magic tell and its lead in client cycles; callers perform server-ID matching before construction.What actx.threats.snapshot(..)call should include.A detached copy of one tick of a fight: the local player, the NPCs, projectiles and graphics around them, and the prayers that were checked.