This is for Blue Server. Relay Server always runs name set request events.

This sets the handling mode for name set/change requests. It takes three parameters:

  1. Inform Fusion parameter. 1 to triggers the Fusion condition Client > On name set request when a name set request happens, or 0 to disable (quiet mode).
  2. Immediately respond with; one of 0 (approve immediately), 1 (deny immediately), or 2 (wait for fusion).
  3. The deny reason, if denying immediately.


There are five valid handling modes.

Trying to use the invalid mode (parameters 0, 2) will result in an error and the handling mode not being changed.

Using something outside of 0 or 1 for first parameter, or outside of 0 through 2 for second parameter, will result in an error and the handling mode not being changed.

If the deny reason is non-blank when the immediate response is not set to deny, the reason will be ignored without error.

Mode 1. Auto-approve and don't tell Fusion

You can enable this mode by passing parameters 0, 0, "".

This is one of the two fastest options performance-wise.


This mode instantly approves the name set request when processing the request message, and doesn't queue a Client > On name set request event.

Mode 2. Auto-deny and don't tell Fusion

You can enable this mode by passing parameters 0, 1, and the deny reason.

This is one of the two fastest options performance-wise.


This mode instantly denies the name set request when processing the request message, and doesn't queue a Client > On name set request event.

The third parameter of this action is used for the deny reason.

Mode 3. Auto-approve and tell Fusion

You can enable this mode by passing parameters 1, 0, "".

This is a slower option performance-wise, and is useful for logging.


This is the default mode Blue Server uses, to match Relay Server's defaults.


This mode instantly approves the name set request when processing the request message, and queues a Client > On name set request event.

The triggered event is an after-the-fact notification, and due to the request already being approved, you cannot deny or change the name during the event.

Mode 4. Auto-deny and tell Fusion

You can enable this mode by passing parameters 1, 1, and the deny reason.

This is a slower option performance-wise, and is useful for logging.


This mode instantly denies the name set request when processing the request message, and queues a Client > On name set request event, with the deny reason already set during the event.

The triggered event is an after-the-fact notification, and due to the request already being denied, you cannot deny or change the client name during the event.

The third parameter of this action is used for the deny reason.

Mode 5. Wait for Fusion events to approve/deny

You can enable this mode by passing parameters 1, 2, "".

This is the slowest option performance-wise, and is useful when Fusion events must dictate whether to approve or deny the name, or you want to modify the names, and after-the-fact renaming isn't sufficient.


This mode does not respond to the name set request message when processing it, but queues a Client > On name set request event.

When the event is triggered, you can choose to deny via the On interactive condition > Deny (for on […] request) action, or change the requested client name before approval via the On interactive condition > Change name (for name set/change request) action.

If you do not deny, the name will be approved once the event finishes.