Skip to content

Raid event {user} uses displayName instead of login ID, causing /shoutout {user} to fail for users with non-ASCII names (e.g., Chinese display names) #51

@k2210000

Description

@k2210000

Hello StreamElements team,

I would like to report an issue related to how the {user} variable is handled in Raid events.

Currently, the {user} field in raid events appears to use displayName, and not the user's Twitch login (account ID).
When using {user} to perform /shoutout {user}, this works fine for users with English or ASCII usernames.
However, for users with non-ASCII displayName (such as Chinese names), the generated /shoutout {user} command fails to execute properly in Twitch chat.

This is because:

displayName can contain non-ASCII characters.

Twitch's /shoutout command requires the login ID, not the display name.

Applying .toLowerCase() on displayName has no effect on Chinese or other non-Latin characters, causing the command to fail.

When a user raids the channel:

displayName: 你有感覺嗎

login: cute_phantom

What is currently generated:

/shoutout 你有感覺嗎

→ Twitch chat does not recognize this command correctly.

What should be generated:

/shoutout cute_phantom

→ This works properly because Twitch identifies users by login ID.

Suggested Solution
Please update the {user} field in raid event handling to use the user's login (account ID) instead of displayName.
This would ensure that /shoutout {user} works reliably for all users, including those with non-English or non-ASCII names.

If maintaining backward compatibility is a concern, you might consider introducing a new variable, such as {user_login}, specifically for commands that require a safe, ASCII-compatible ID.

Thank you very much for your hard work on StreamElements!
I hope this feedback helps improve the platform for global users.
Looking forward to your response!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions