Many venues start with one Spawnpoint Controller PC per arena. While this works perfectly well, it means managing multiple PCs, downloading content multiple times, and moving between different operator stations throughout the day.

This guide covers setting up your network to support centralised management of multiple arenas in Spawnpoint. While you still need a Game Server for each arena, Spawnpoint's multi-arena support allows you to centrally monitor, configure and update your headsets from a single Spawnpoint Controller instead of needing one for each arena.

By connecting your arenas together, Spawnpoint can manage them from a single Controller PC while still keeping a dedicated Game Server in each arena.

Benefits include:

• Manage all arenas from a single Operator UI
• Download games once and deploy them across all arenas
• Centralised venue management
• Support for multi-arena experiences such as Nanoclash, which is designed around Arena vs Arena gameplay. Find out more about this feature [HERE]
• Access arena controls from any device on your network, including other PCs, laptops and tablets

Note: Each arena still requires its own Game Server PC. Spawnpoint only combines arena management into a single Controller PC.

If your venue uses enterprise networking equipment such as Ubiquiti UniFi or TP-Link Omada, your network will most likely already be configured in a way that supports a single Spawnpoint Controller. In most cases, no additional changes are required.

For venues using separate consumer-grade routers for each arena such as ASUS, TP-Link (excluding Omada) or Netgear , there are two main ways to setup your network to support this feature

Before You Start

Every router manufacturer uses different menus and terminology.

Whether you're using ASUS, TP-Link, Netgear, Linksys, MikroTik, GL.iNet, or another brand, the settings described in this guide may be located in different places.

If you're unsure where to find a particular setting, consult your router manufacturer's documentation.

Check for Fixed IP Addresses

Before making any network changes, check whether any systems in your venue are reliant on pre-existing fixed IP addresses. This guide assumes that you are only using your Arena routers for your PCs and headsets and no other business-critical hardware such as payment systems, security cameras, etc.

If you change your network layout or IP address ranges, some systems may need to be updated with their new IP addresses before they can communicate correctly. If in doubt, please consult your IT provider as we would not advise messing with any non-VR critical infrastructure.

Backup your Router Configurations

Before changing anything, we recommend backing up the settings from each of your routers to ensure you can reverse the changes if needed. This is usually found in an Administration/Maintenance section in your router's control panel.

Warning: Do this early in the week if you're already open

This is a disruptive process, and may leave your arenas non-operational. We can always help you get back up and running, but we would not recommend doing this later in the week when there may not be time to do so before the weekend.

Option 1: One Shared Network

This is the recommended approach for most venues.

The goal is to create a single network for all arenas while still allowing each arena to have its own WiFi coverage and network name.

One device acts as the primary router and manages internet access and IP address assignment for the entire venue. The remaining arena routers are converted to Access Point Mode (AP Mode).

Choosing Your Primary Router

In a shared network setup, one device must be responsible for managing the network and assigning IP addresses. This is typically referred to as the primary router.

However, you do not necessarily need to purchase additional networking equipment: Many venues simply choose one of their existing arena routers to become the primary router and convert the remaining routers to Access Point Mode.

For example:

Alternatively, if your venue already has a dedicated internet router, firewall, or networking appliance, that device may already be acting as the primary router. The correct approach depends on your existing network design.

If you are unsure which device should act as the primary router, contact Spawnpoint support. If you already work with an IT provider, we can also provide a separate networking recommendations guide intended for IT professionals.

Configure Access Point Mode

Most routers provide an operating mode called:

• Access Point Mode
• AP Mode
• Bridge Mode
• Wireless Access Point Mode

The exact name varies by manufacturer.

You can usually find this option within:

• Network Settings
• Advanced Settings
• Operating Mode Settings
• Administration Settings

Consult your router manufacturer's documentation if you cannot locate it.

Different WiFi Names Are Still Supported

Putting your arena routers into Access Point Mode does not mean all arenas must share the same WiFi network name. Most venues continue to use a separate WiFi name (SSID) for each arena, and this is the recommend way to avoid your headsets roaming to a different router and ending up with a poor signal.

For example:

• "Arena-A"
• "Arena-B"
• "Arena-C"

This helps ensure headsets remain connected to the correct arena while still allowing all devices to exist on the same underlying network.

Assign an IP Address to Each Access Point

When converting a router to Access Point Mode, we strongly recommend assigning it a permanent IP address.

This makes it easy to access the router's administration page later if you need to:

• Change WiFi settings
• Update firmware
• Change passwords
• Troubleshoot connectivity issues

For example:

Create DHCP Reservations

Most routers provide a feature called:

• DHCP Reservation
• Address Reservation
• Static DHCP
• DHCP Binding

The exact name varies by manufacturer.

We recommend creating DHCP reservations on the primary router for each Access Point. This ensures each Access Point always receives the same IP address, making future maintenance much easier.

Keep a record of these addresses for future reference.

Things to Consider

While Spawnpoint fully supports this setup, some VR platforms expect you to use a separate network for each arena and do not provide an option to bind your headsets to a specific game server. This can cause issues when moving to a fully shared network as your headsets may connect to the wrong game server.

If you rely on software that behaves this way, Option 2 may be easier to implement - or hassle your other providers to add a Fixed IP option, we're not picky.

Option 2: Separate Networks with a Shared Controller

If your venue already operates each arena as its own separate network, you may prefer to keep that configuration.

In this setup, each arena continues to use its own router, IP range and network configuration while still allowing all arenas to communicate with a single Spawnpoint Controller.

This provides many of the benefits of a shared Controller without requiring you to redesign your existing network architecture.

Network Layout

Choose one arena to become the primary arena. This arena will host the Spawnpoint Controller PC (the one you installed Spawnpoint on).

For example:

• Arena A = Primary Arena
• Arena B = Secondary Arena
• Arena C = Secondary Arena

Connect each secondary arena router directly to the Arena A router, and the Controller PC should remain connected to Arena A.

Each arena remains a separate network, but devices can still route traffic back to the Controller PC through Arena A.

Configure Different IP Ranges

Each arena router must use a different IP range to ensure your headsets can connect to Arena A's PC.

Example:

This allows devices in each arena to correctly find their way back to the Controller PC.

Important: If you change an arena's IP range, any devices or applications configured to use fixed IP addresses may need to be updated.

Reserve the Controller PC's IP Address

The Controller PC must always keep the same IP address.

Most routers provide a feature called:

• DHCP Reservation
• Address Reservation
• Static DHCP
• DHCP Binding

The exact name varies by manufacturer.

Create a reservation for the Controller PC within the Arena A router.

For example:

If the Controller PC's IP address changes, headsets may no longer be able to automatically find it.

A Note When Using Multi-Arena Linking

When using Spawnpoint's new Multi-Arena Linking functionality in this setup (e.g. to run NanoClash), Arena A must be the primary arena that you link your other arenas as Arena A's game server is the only one that all the headsets can connect to.

Reconfiguring Spawnpoint

Once your network has been configured, the final step is to add your additional arenas to Spawnpoint.

The process differs slightly depending on whether:

• You are adding a brand new arena to an existing Controller.
• You are migrating existing standalone arenas to a shared Controller.

Please follow this guide: Managing Multiple Arenas in Spawnpoint

Accessing Spawnpoint from Other Devices

One of the biggest advantages of a central Controller is that the Operator UI can be accessed from anywhere on your local network.

Simply open a web browser and navigate to:

http://<controller IP>:4376

For example:

http://192.168.1.10:4376

The Operator UI is fully tablet-friendly, allowing staff to manage games, players and arenas from tablets, laptops and other devices connected to the network.

This means that even though there is only one Controller PC, operators are not restricted to sitting in front of it.

Tip: Pico and VIVE Focus customers should set Spawnpoint as their Device Admin (Owner/MDM). This allows Spawnpoint to deploy application updates wirelessly across all arenas, making updates significantly faster and eliminating the need to connect headsets via USB in most situations. For more information, see: Using Spawnpoint's Advanced "Device Admin" Features

Quick Reference for Advanced Users

Option 1: One Shared Network

• One device acts as the primary router and DHCP server.
• All arena routers are converted to Access Point Mode.
• Each arena may continue using its own SSID and password.
• All devices exist on the same IP network.
• Create DHCP reservations for all Access Points.
• Record the management IP of each Access Point.

Option 2: Separate Networks with a Shared Controller

• Arena A hosts the Spawnpoint Controller.
• Arena B, C, etc. connect directly back to Arena A.
• Each arena retains its own router and DHCP server.
• Each arena uses a unique IP range.
• Create a DHCP reservation for the Controller PC.
• Arena A acts as the primary arena for Multi-Arena Linking.

Spawnpoint Configuration

After network changes:

1. Uninstall the Controller from any secondary Controller PCs.
2. Right-click the Spawnpoint Agent in the Windows system tray.
3. Select Clear Agent Pairing.
4. Open Spawnpoint on the primary Controller.
5. Select Add Arena.
6. Complete Arena Setup for each arena.
7. Re-pair Game Servers and headsets.

Operator UI

The Operator UI is available from any device on the network:

http://<controller IP>:4376

Notes

• One Game Server is still required per arena.
• Pico and VIVE Focus customers should set Spawnpoint as their Device Admin (Owner/MDM) to enable wireless application updates.
• If changing IP ranges, update any systems using fixed IP addresses.
• Enterprise networking platforms such as UniFi and Omada typically already operate as a single network, so you just need to setup your arenas in your controller.

Need Help?

Networking equipment varies significantly between manufacturers, and the exact steps required will depend on your existing setup.

If you are unsure which option is right for your venue, contact Spawnpoint support.

If you already work with an IT provider, ask us for our technical networking guide, which contains additional information intended for IT professionals.