Oftentimes, channel naming and management associate your in-game social entities, such as guilds or parties, which are then matched with a channel identifier of your choice.Īll secured actions such as logging in, joining channels, and performing certain moderated actions, require authorization in the form of a VAT. You can choose channel names based on your own naming conventions. The echo channel is useful for both internal development and testing, and for providing an audio test environment for user devices. Note: This channel type does not allow communication between users. Refer to the following table when choosing your channel types: They have no persistent state, nor are they managed by any form of access control from within the Vivox network.Īccess to the channel (joining) as well as secured third-party actions (for example, kick or moderator mute) must be authorized by the game server with a VAT before a user may perform the action. They are ephemeral and persist only as long as there is at least one occupant. Continue reading to learn more about channel properties, types, and names. They have a short lifespan (being valid for 90 seconds from generation).Ī token is required for logging into the Vivox network and your game server should securely vend this token to your client (for example, with a secure web service).ĭetails regarding the generation and distribution of tokens can be found in Vivox's Access Token Developer Guide, which can be found at the end of this guide.Ī channel supplies voice chat to two or more participants, and joining a channel (or several channels) is accomplished by properly generating a VAT. They limit a client to a single server operation, such as logging in or joining a voice channel. Since there may be persistent data within the Vivox network associated with your users, the assigned Vivox user ID should be persisted with the game account even if the user's in-game account ID or character ID changes.Īccess to Vivox services requires a VAT because these tokens provide the following security measures: The typical approach for logging into the Vivox service is to associate your user's in-game account, character ID, or other unique data to a non-identifying, unique Vivox user ID, which is generated per user. The following subsections contain brief overviews of major integration elements. Tip: Although we realize that having a game server is optional, it is considered a best practice to have one. During initial development, game server actions can be performed on the client, but eventually, you should move these tasks to a secure game server before final launch. This phase has game server and game client tasks. Optionally, determining what users can mute, ban, or kick channel participants.
Unreal engine 4 portal how to#
The last phase is a reminder to secure your feature-complete implementation.ĭuring the planning phase, organizational decisions must be made about:ĭeciding on a naming scheme for user IDs and channels.ĭetermining how to perform Vivox login and channel management services as part of your game's back-end. The third phase is considered optional because it means that you intend to integrate advanced services, such as 3D positional audio or moderator features, often requiring additional development time and future maintenance cost. Phase 3: Advanced Implementation (Optional)Īfter completing the first two phases of the integration plan, your project should be able to login and logout, as well as join and leave a single channel with locally generated Vivox Access Tokens (VATs). Integrating Vivox into a game typically involves the following phases: The following integration guide is intended to be a basic overview, helping you evaluate the Unreal Vivox Plugin for your own project. After signing up to access the Vivox Developer Portal, adding and enabling the Vivox Plugin, and agreeing to all of the licensing terms and conditions, you're ready to start working on an integration plan. Now, from the Built-In side menu, open Online Platform, and enable the Vivox Plugin.įinally, restart the editor to complete this process.Īfter restarting Unreal Editor, the built-in Vivox Plugin is enabled for your project so keep reading to learn more about planning for your Vivox integration. In the Settings drop-down menu of the Level Editor toolbar, select Plugins to open the Plugins Browser. To enable the Vivox Plugin for your project, follow this process:
Unreal engine 4 portal license#
Note: To access Unreal Engine 4 (UE4), either enter a custom licensing agreement with Epic Games or agree with the Unreal Engine End User License Agreement (EULA).
0 kommentar(er)
