Script Restrictions

To promote a more level playing field during organized PvP encounters, specific restrictions are applied to automation tools like Razor scripts and macros, as well as certain UI elements. These restrictions aim to limit overly complex automation and reliance on out-of-game information gathering during events.

Important Note: These restrictions are subject to review, reassessment, and potential changes based on ongoing evaluation and player feedback.

Scope of Restrictions

These PvP Feature Restrictions apply during participation in the following activities:

• Arena Matches (Duels and Tournaments)
• Corpse Creek Contest
• Dungeon Flashpoints
• Factions activities (including Wayposts, Flag actions, Caravans, VIPs, etc.)
• Stygian Rifts
• Town Struggles

These restrictions do not apply to non-consensual PvP activities (i.e., standard Player Killing outside of structured events).

A new script expression, `pvp`, has been added. This expression allows scripts to check if the PvP script restrictions are currently active for the player (`if pvp`).

Script Restrictions

Disabled Commands and Expressions

While restrictions are active, the following Razor script commands and expressions are disabled or function differently:

Commands

• `setvar` (when targeting players)
• `droprelloc`
• `waitforsysmsg`
• `settimer`
• `removetimer`
• `getlabel`
• `rename`
• `cooldown`
• `wait`/`pause`

Expressions

• `bandaging`
• `findbuff`/`finddebuff`
• `mana`, `maxmana`, `diffmana`
• `hits`, `maxhits`, `diffhits`
• `stam`, `maxstam`, `diffstam`
• `poisoned`
• `paralyzed`
• `hidden`
• `str`, `dex`, `int`
• `position`
• `timer`
• `followers`
• `hue`
• `blessed`
• `notoriety`
• `dead` (when checking mobs other than the player themselves)
• `maxweight`, `diffweight`
• `gumpexists`, `ingump`
• `cooldown`
• `casting`

Serial Handling

Player serials (unique identifiers) will resolve as `0x0` (effectively null/disabled) within scripts and macros when restrictions are active.

• Example: If a script stores another player's serial in the variable `player`, attempting to use that variable in commands like `attack player` or `setlasttarget player` will fail as `player` will evaluate to `0x0`.

Item Find Handling

Commands and expressions that search for items (`find`, `findtype`, `findtypelist`, `dclicktype`, `lifttype`, `counttype`) will only locate items that are currently worn by the player or are within the player's main backpack inventory. Items in containers within the backpack, on the ground, or elsewhere will not be found by these commands while restrictions are active.

Message Handling

Party and Guild chat messages will not be intercepted or recognized by Razor scripts or the client's macro/journal system while restrictions are active.

UI Restrictions (Experimental)

The following UI changes are currently experimental and subject to adjustment based on feedback.

Last Target Expiration

If the player's currently held `Last Target` corresponds to a player who has been off-screen for more than 60 seconds, the `Last Target` will automatically reset (clear). The player will receive an overhead system message notifying them when this occurs.

Macro Restrictions

The following built-in client macro actions and types are disabled or will not function correctly while PvP script restrictions are active:

• Conditionals (`If`, `While`, `DoWhile`) that rely on checking player stats (e.g., `hits`, `poisoned`) or system messages.
• `DropRelLoc` (Drop Relative Location)
• Wait actions (`WaitForTarget`, `WaitForGump`, `WaitForMenu`, `Pause`)
• `TargetRelLoc` (Target Relative Location)
• `SetLastTarget`
• `SetMacroVariableTarget`