文档

​
​

Development

User Acquisition

Monetization

工业

Vivox Core SDK

Vivox Core SDK

此页面不支持所选语言。
Vivox
​
​
Vivox Core SDK
  • Overview
  • Before you begin
  • Get started
  • Release notes
  • Developer Guide
  • Reference
    • Access Token Developer Guide
      • Access token terminology
      • Requests that require access tokens
      • Access token identifiers
        • Usernames
        • Channel names
        • Access token issuers & signing keys
      • Access token format
      • Access token examples
      • Generate a token on the client
      • Generate a token on a secure server
      • Key update API
      • Override development key generation
      • Access token error codes
    • Server to Server Web API Reference Guide
    • Core API Reference Manual
    • Third-party license information
  • Privacy overview
  1. Vivox Core SDK documentation

Usernames

Understand the naming criteria and format required for Vivox usernames.
阅读时间1 分钟
最后更新于 8 个月前

When you create a username, the following criteria apply:
  • Maximum of 127 bytes
  • Start and end with a period '.'
  • Use only the following characters:
  • Alphanumerics

    0-9, A-Z, a-z

    0x30-0x39, 0x41-0x5A, 0x61-0x7A

    Exclamation mark
    ' ! '
    0x21
    Open parenthesis
    ' ( '
    0x28
    Close parenthesis
    ' ) '
    0x29
    Plus
    ' + '
    0x2B
    Minus
    ' - '
    0x2D
    Period
    ' . '
    0x2E
    Equals
    ' = '
    0x3D
    Underscore
    ' _ '
    0x5F
    Tilde
    ' ~ '
    0x7E
    Percent
    ' % '
    0x7F
    注意
    You can only use the percent sign for URL encoding. Follow the percent sign by two uppercase hex characters.
The recommended best practice is to URL-encode the username by using only uppercase hex digit characters. Lowercase characters are allowed in the username, but not when used as the hex digit characters.
For example, if your issuer name is "crux", then a valid username is
.crux.0verl0rd
.
You should also:
  • Create a one-to-one mapping between an Account and a player.
  • Use the same Account for the same player every time they play the game.
It’s recommended that you re-use player account names and create one-to-one mapping between and account and a player to facilitate the use of Vivox features such as cross-mute and blocking. It will also become a requirement for using future safety features designed for reducing toxicity and fostering more positive communities.
注意
For the Vivox Unity SDK and the Vivox Unreal SDK, the naming displayed in this example only applies during access token generation. When you construct an AccountId, you are expected to use only the
"0verl0rd"
part of the username and not
".crux.0verl0rd."
for the name argument. The AccountId function
ToString()
returns a full user URI that is suitable for token generation, which includes the dots, issuer, and other URI components.
If you do not want to use a unique account name per player, or if you do not want to expose the username to the network, then use one of the following options:
  • A hash of the unique username.
  • A universally unique identifier (UUID).

Copyright © 2026 Unity Technologies
法律信息隐私政策CookiesDocumentation Terms of Use请勿出售或分享我的个人信息您的隐私选择(Cookie 设置)

“Unity”、Unity 徽标及其他 Unity 商标是 Unity Technologies 或其附属公司在美国和其他地方的商标或注册商标(此处查看更多信息)。其他名称或品牌是其各自所有者的商标。

为方便起见,一些页面是机器翻译的,可能包含不准确的内容。如有信息不一致的情况,以英文版本为准。


    报告此页面的问题