Interface & appearance · Interface & services
Macroing
A macro repeats a fixed sequence of inputs; it does not understand the map, danger, rules, or whether the sequence still makes sense.
Practical guide
3 steps for this topic- Read the current service rules before using any repeated-input feature, even in a training area.
- Prefer built-in or supported controls and remain able to respond to staff, hazards, map changes, and other players.
- Do not run unknown executables or tools that read client memory merely because an old guide named them.
Key details
Keep these with the route- Policy first
- Historical community practice is not permission under current rules.
- Security
- Unsigned automation software can expose accounts, credentials, or the whole computer.
Check the living world.
The underlying system is stable, but exact prices, schedules, laws, event rewards, availability, policies, or community rules can change. Current in-game dialogue and official notices win.
Detailed reference
3 concrete notes- A simple macro repeats fixed key presses without understanding the map, target, danger, or game state. That distinction does not make unattended use automatically permitted.
- Historical uses include executing PvP combos, repeating training inputs, or cycling a stationary hunt role. Each use still needs current service-policy and host-rule approval.
- Avoid tools that inject into the client, read credentials, or arrive as unsigned binaries. Supported in-game training and ordinary keybinds are safer than an archived executable.