Uses of Class
privbot.mechanics.TargetSpec
Packages that use TargetSpec
Package
Description
Pure game-mechanic rules shared by plugins on every server: the same name and meaning on Impact, Elorin, Orion,
SpawnPK and Roat Pkz.
-
Uses of TargetSpec in privbot.mechanics
Methods in privbot.mechanics that return TargetSpecModifier and TypeMethodDescriptionTargetSpec.alsoIds(int... ids) Also matches these NPC ids, whatever their name (adds ids to a spec built withnamed(java.lang.String...)).static TargetSpecTargetSpec.any()A spec matching every NPC; narrow it withignore(java.lang.String...)orwithin(net.runelite.api.coords.WorldArea).TargetSpec.contains(boolean contains) true(default): plain entries match by containment;false: every entry is an exact match.static TargetSpecTargetSpec.ids(int... ids) A spec matching these NPC ids, whatever their name.Never matches an NPC whose name matches one of these (same rules as names).static TargetSpecA spec matching these names.ThreatQuery.npcSpec()TargetSpec.within(net.runelite.api.coords.WorldArea area) Only matches NPCs whose tile is insidearea.Methods in privbot.mechanics with parameters of type TargetSpecModifier and TypeMethodDescriptionTargetLock.choose(List<NpcView> npcs, int currentTargetIndex, net.runelite.api.coords.WorldPoint player, TargetSpec spec) Picks the target, in this order: the current target, if it matches and is alive and not busy; the locked NPC, if present with the same index and id, still matching the spec, alive and not busy; the first matching NPC that targets us and is alive; the nearest matching NPC that is alive and not busy, ties to the lower index. A locked NPC seen dead counts a kill if it had targeted us or been our current target.ThreatQuery.npcs(TargetSpec spec)