For the complete documentation index, see llms.txt. This page is also available as Markdown.

Switch From Multiplay

Take advantage of free integration support for Unity and Unreal projects and migrate to our reliable hosting easily. If you're relying on Multiplay hosting services, the time to switch is now.

🚨 Multiplay End of Life

πŸš€ Getting Started

With Multiplay end of life closing in, evaluating replacements is an urgent need to keep your business running and prevent negative impact on your player base. Edgegap engineers and our amazing dev community are available for integration support and navigating this stressful situation.

Try one of our quick start guides supported with game engine plugins:

If you need help, please reach out to us over Discord. For live games support see our ticketing system.

πŸ’‘ Case Studies

πŸ—ΊοΈ Replace Features

Review and identify Multiplay and Unity services and features which you need to replace:

Multiplay Feature
Edgegap Features

Hosting SDK

No SDK required! ServerConfig replaced by Apps and Versions.

Create a Build

Try our quickstart tools - Unity / Unreal Engine.

Build Configuration

Fully Automated. Optionally expose additional ports or variables.

Server Query Protocol

Fleet

Private Fleets with Persistence and Cloud Overflow. Optionally add later on, or default to Match-Bound cloud.

Test Allocation

AB testing

⭐ Start Deployments from UGS Matchmaker

If you prefer not to migrate to Edgegap's Matchmaking and keep your UGS Matchmaker, see our UGS hosting provider cloud script integration.

Deployment Placement

Choosing the right location for your deployment can help reduce latency by up to 58% on average!

To take advantage of low-latency edge deployments you will need to:

  1. include our EdgegapAllocator cloud script module in your UGS matchmaker,

    1. add your EDGEGAP_API_TOKEN to UGS Secrets,

    2. paste your Edgegap App name and Version in the cloud script code,

  2. include player's public IP address when creating matchmaker tickets:

    1. when creating ticket with POST- https://matchmaker.services.api.unity.com/v2/tickets ,

    2. include public IP in custom data:

Storing Deployment Details for Player Connections

Last updated

Was this helpful?