I        This condition is triggered when a client requests to set or change their client name.

The client will be auto-selected for you at the start of the event, and channel selection will be set to none.

This condition can be disabled for efficiency

To change the mode in Blue Server, use the Enable/disable conditions > On name set request action. You should do this before you start hosting, to avoid a fast client managing to outrace your server.

Changing the mode while a server is live is safe to do.


In Relay Server, this condition cannot be disabled.

Possible responses

The responses can be set to happen automatically in Blue via the Enable/disable conditions > On name set request action.

In Relay, the name set request events are always run and must finish before a response is sent.


Events can choose one of three actions:

  1. Use On interactive condition > Deny (on [..] request), causing the name set/change to be denied.
  2. Use On interactive condition > Change name (for name set/change request), causing the client to set their name to a different name than was requested.
    Note the name restrictions below apply to the changed name, as does the client name Unicode allowlist.
  3. If no interactive action is run, the request is approved with the name expected.

In Blue, if you use multiple of these actions, an error will be created for the second and later ones.

Name restrictions

Client names may have any characters, and clients may request a name set/change with a name at any length, but once approved by the server, the name must be 1-255 characters long.

By default, servers do not change the names before trying to approve them, so if you request a name too long, you will get your name set denied.

In Relay, this limit is 1-255 ANSI characters, and there is no way to use Unicode names. In Blue, it is 1-255 UTF-8 bytes.

ANSI and UTF-8 are described under Unicode notes.

You can get the byte count of a potential name with the Convert to UTF-8 and count bytes expression.


Some servers may allow newlines, tab characters and the like in a client/channel name, but due to difficulty referring to or displaying these in one-line controls, this is usually not allowed.

In Blue Server, there is a default client name Unicode allowlist preventing use of strange characters, which you can view under Unicode notes.