Most refused or interrupted interactions can be handled safely by reading the complete response, restoring the required context, and checking the documented player-visible state before retrying. Do not use repeated commands, reconnects, or unrelated interactions as a general way to force progress.

Start with the complete response

  1. Read the whole refusal or result, including any prerequisite it names.
  2. Use /help to review the current registered command, category, syntax, and action descriptions.
  3. Use the refusal and owning guide to confirm the required role, duty state, location, interior, world, vehicle, or proximity.
  4. Review required money, items, ownership, keys, employment, or organization membership through the owning feature’s visible state.
  5. Retry only after correcting the stated condition.

An unknown command can offer a conservative suggestion, but the game does not run it automatically. Check the suggestion before entering it.

Refresh numbered references

A displayed number or # reference belongs to the list and context that produced it. References can expire, be replaced by a new search, or clear when the character or connection changes.

Reopen the exact owning list and choose from the current entries. Do not guess a hidden identifier, reuse a number from another list, or rely on a reference remembered from an earlier session.

Wait for the final result

A prompt, preview, started action, or accepted offer is not necessarily completion. Wait for the feature’s final success result and use only its documented player-visible checks.

If the final result is missing:

  • do not immediately repeat or reverse the action;
  • for money, both participants can check /balance;
  • inventory and key views can show a completed visible change, but absence there does not reconcile an ambiguous save;
  • for a job, vehicle, property, or record action, follow that owning guide’s specific recovery path rather than assuming a universal status view; and
  • preserve an unresolved item, key, or other durable mutation for support without retrying.

See Offers and incomplete transactions for consent prompts and multi-part exchanges.

Recover after a real interruption

Reconnect only after a genuine connection or client interruption. Do not reconnect to bypass a scene, refusal, waiting period, custody, or consequence.

After returning:

  1. complete login and character selection normally;
  2. read any recovery or reminder message;
  3. use the owning feature’s documented visible checks once;
  4. reopen temporary lists, prompts, checkpoints, or interfaces only through their normal entry point; and
  5. restart an action only after an explicit result makes clear that no mutation was attempted.

Durable state such as balances, owned items, employment, access, and property records can survive even when a temporary offer, route, prompt, or list does not.

Preserve useful evidence

If the state still does not make sense, record:

  • the task and command or interaction;
  • the exact message and visible result;
  • affected characters or visible entities;
  • the location and approximate time; and
  • which player-visible balance, list, label, or status result you checked afterward.

Do not reproduce a harmful action, flood several support routes, post login codes, or include unrelated private information. Avoid unsupported fixes such as deleting client files, reinstalling, manipulating local state, or repeatedly reconnecting.

For command discovery, see Commands, prompts, and getting help. For unclear balances and payments, see Money, banking, and paying players; for item custody, see Inventory, giving, dropping, and picking up items.