This action allows you to change the name of a client from their requested name during an On name set request event.

Its only parameter is the new changed name you want to give the client.


You can view the original name using the Requested name (for name set/change request) expression, but note once you use this action, the expression will return the name you changed it to.


If you want to allow the name without changes, don't run any deny or name-change action, and the client will be given their requested name once Lacewing finishes running all the On name set request events.

Relay notes

If you pass blank "" as the new name, the client will receive a name set success message with a blank name. This is a bug.

Both Blue and Relay Client will see a blank name as an unset name during the Join channel action, and they will not allow you to join a new channel. But if you already set a name and joined a channel, you will have a blank name to all peers.


If a client requests a name or server modifies the request to a name that is longer than 256 characters, Relay Server will approve the name set with the last 256 characters stripped – causing a blank name to be approved. 257 characters will result in a name of only the first character of the requested name, 258 characters the first two characters, etc. This is a bug.

If you set it as 257 characters, the too-long name will result in corrupting any channel that you're on. Relay Client will start to not process messages silently, whereas Blue Client will start to create errors about malformed messages.

Blue notes

If a client requests an invalid name and you do not change it, e.g. blank or too long, then before approval it will fail checks and be rejected.

A deny reason will be sent back to the client. This denial does not create a server-side error.


If you change the name with Blue Server to an invalid name, you will get an error, and the name change request will be denied. The reasoning is that if the original name was approvable, you would not have run the change name action in the first place.

The only error that will not cause the request to be denied is if you set the name to what it already was.


The Blue Server's Unicode allowlist for client names still applies to client names the server has modified. You can set the allowlist using the (Advanced) Set Unicode allowlist action.

If a changed client name fails the allowlist, you will get a server error similar to:

Cannot change new client name: Code point at index 6 does not match allowed list. Code point U+0031, decimal 49; valid = yes, Unicode category = Nd.

For a breakdown on what parts of the error message means, see the Convert string to UTF-8 and check against Unicode allowlist expression.