Phase 1: Planning and organization
Understand and plan how you'll manage voice and text chat within your code and game.
읽는 시간 1분최근 업데이트: 8달 전
In phase one, you make determinations about the general structure and organization of in-game voice-related data and identify code paths for handling necessary actions such as signing in and joining or leaving channels.
During the planning phase, you must make decisions about the following topics:
- Login and channel management: Decide on an authoritative naming scheme for user logins and channels. Identify game client code paths for account and channel-based operations.
- Game server interaction: Determine which game server APIs return Vivox login data or channel joining information. Configure the general structure and relationships between channels, user logins, and user privileges in a particular channel type, or if users are blocking audio from other users.
- Authorization: Control the flow for authorizing users to perform secure client-side voice operations.
- UI Integration: Designate the UI elements for voice operation control.
The tasks that make up this phase of the integration are split between the game server, for authorization and server-enacted operations, and the game client, for user activity and UI integration.
Topic | Description |
|---|---|
| Login management | Basic information on how logins work in Vivox Core SDK. |
| Channel management | Basic information on how channels work in Vivox Core SDK. |
| Game server integration | Information management on the game server. |
| Authorization | Information on how to grant authorization. |
| Voice-related logging | Best practice recommendations for client logging. |
| User settings | Recommended settings to expose to users. |
| UI integration | Suggested UI integrations for a better user experience. |