PurrNet
  • 🐈Introduction
    • ‼️Unique to PurrNet
    • 💲Pricing
    • 💻Compatibility
    • 📚Addon library
    • 🗺️Roadmap
    • 🏎️Performance
      • RPC Benchmarks
      • Network Transform benchmarks
    • 🥰Support PurrNet
  • 📚Guides
    • Installation/Setup
    • Getting Started
    • Converting to PurrNet
      • Converting from Mirror
      • Converting from FishNet
    • Lobby System
    • Networking custom classes, structs & types
    • Chat system with broadcasts
    • Easy Multiplayer Physics (input Sync)
  • 🎮Full game guides
    • 🔫First Person Shooter
    • 🪓Survival Game
  • 🖥️Systems and modules
    • Network Manager
      • Network Rules
      • Network Prefabs
      • Network Visibility
        • Distance condition
      • Transports
        • Composite Transport
        • UDP Transport
        • Web Transport
        • Local Transport
        • Steam Transport
        • Purr Transport
      • Authentication
    • PlayerID (Client connection)
    • Network Identity
      • NetworkBehaviour
      • Ownership
      • Sync Types
        • SyncVar
        • SyncList
        • SyncArray
        • SyncQueue
        • SyncDictionary
        • SyncEvent
        • SyncHashset
        • SyncTimer
      • Don't destroy on load
    • Network Modules
    • Collider Rollback
    • Client Side Prediction
      • Overview
      • Predicted Identities
      • Predicted Hierarchy
      • Best Practices
      • Input Handling
      • State Handling
    • Plug n' play components
      • Network Transform
      • Network Animator
      • Network Reflection (Auto Sync)
      • State Machine (Auto Networked)
    • Spawning & Despawning
    • Remote Procedure Call (RPC)
      • Generic RPC
      • Static RPC
      • Awaitable RPC
      • Direct Local Execution of RPCs
    • Instance Handler
    • Scene Management
    • Broadcast
  • 🤓Terminology
    • Early Access
    • Channels
    • Client Auth/Everyone (Unsafe)
    • Host
    • Server Auth (Safe)
  • 💡Integrations
    • Dissonance
    • Cozy Weather
Powered by GitBook
On this page
  1. Systems and modules
  2. Network Manager
  3. Transports

Purr Transport

The Purr Transport is a relay provided by us to you. We wanted to allow the best developer experience and not having to setup servers or do port forwarding to test your game in an online scenario is a big pain point we are trying to take away from you.

The transport is in very early stages and will undergo multiple changes and you might experience server restarts once in a while. That being said it should be more than fine for testing purposes.

It works through a room system, you just need to specify a unique room and anyone can connect to it through the relay. There is still the notion of server and client and only one client can act as the host. Once the host disconnects everyone else is also kicked out similar to the other transports.

There are multiple regions available to you, right now when you create a room it will ping and get the one closest to you. We have 2 servers in the US, one in EU, one in AP, one in Brazil and one in South-Africa. This should be enough coverage and if needed we might expand on these regions in the future.

To use this transport simply add the PurrTransport component and assign it to your NetworkManager. Region only matters when creating a server/room. When joining an existing session, region is not taken into account. This means that rooms are global and their names are shared across all regions.

The default relay address found in the transport is meant for development only, any production use is prohibited. You can use the transport layer for production if you setup your own relay server for it.

PreviousSteam TransportNextAuthentication

Last updated 4 months ago

🖥️