Skip to content
  • Our Product
    • Namazu Elements
      • What is Elements?
      • Why open source?
      • Docs
        • Elements in Five Minutes or Less
        • RESTful APIs Library
        • Security Model
        • Accessing the Web UI (CMS)

    Our Product

    A logomark with three layered rhombuses adorning the lettermark that says Elements in bold all-caps sans-serif letters.
    • What is Namazu Elements? Discover our easy-to-use backend network solution built for online games. Rapidly enables full-scale multiplayer games or online solo adventures.
    • Why open source? Is there a truly open source server backend for connected games? There is now. Download and run a local copy of Namazu Elements and try it for yourself.
    Download Namazu Elements

    Get started

    • Quick start Read our Elements 5-minute quick start guide
    • Documentation Read our developer docs for learning more about Elements
    • RESTful APIs A full list of core API specs for working with the Elements framework
    • Security An overview of the server-authoritative security model of Elements
    • Accessing the CMS Manage your game with ease via the Namazu Elements CMS.

    Co-development Reimagined

    • Reduce your costs Would you rather outsource your backend development? Hire Namazu Studios to build your server backend with the power of Namazu Elements.
      Co-dev

    Recent Posts

    • Namazu Studios Featured in San Diego Business Journal
      22 Sep 2025 Press
    • Namazu Elements 3.1 Released – Service Layer Fixes, Secure APIs, and Steam Bug Fix
      22 Apr 2025 Release Notes
  • Case Studies
  • About Us
  • News
  • Services
  • Book a call
namazu-studios-logo
Book a call

Getting Started

  • Elements in Five Minutes or Less
  • 🐧Ubuntu Linux Setup
  • 🍎 Mac OS Setup
  • πŸ–₯️ Setup for Windows
  • Accessing the Web UI (CMS)
  • General Concepts
  • N-Tier Architecture
  • Security Model

Namazu Elements Core

  • User Authentication / Sign In
    • What is a User?
    • User Authentication in Elements
    • Auth Schemes
      • Auth Schemes
      • OAuth2
      • OIDC
  • Features
    • Applications
    • Sessions
    • Users and Profiles
    • Digital Goods
    • Progress and Missions
    • Progress and Missions (3.4+)
    • Leaderboards
    • Matchmaking – Comprehensive Guide
    • Followers
    • Friends
    • Reward Issuance
    • Save Data
    • Metadata
    • Metadata (3.4+)
    • Queries
    • Web3
      • Wallets
      • Vaults
      • Omni Chain Support
      • Smart Contracts
        • Smart Contracts
  • Queries
    • Advanced Operators
    • Object Graph Navigation
    • Boolean Queries
    • Base Query Syntax
  • Advanced Operators
    • .name
    • .ref

Custom Code

  • Custom Code Overview
  • Introduction to Guice and Jakarta in Elements
  • Structuring your Element
  • Packaging an Element with Maven
  • Deploying an Element
  • Preparing for Code Generation
  • Properties
  • Websockets
  • RESTful APIs
  • Direct MongoDB Access (3.5+)

Releases

  • 3.4 Release Notes
  • 3.3 Release Notes
  • 3.2 Release Notes
  • 3.1 Release Notes

Configuration

  • Matchmaking – Comprehensive Guide
  • Direct Database Access and Batch Configuration
  • Batch Samples
    • Mission Upload Bash Script Sample
    • Item Upload Bash Script Sample

RESTful APIs

  • RESTful APIs Library
  • Swagger and Swagger UI

Crossplay

  • Namazu Crossfire
  • Deploying Namazu Crossfire in Your Game
View Categories
  • Home
  • Docs
  • Crossplay
  • Deploying Namazu Crossfire in Your Game

Deploying Namazu Crossfire in Your Game

Est. read time: 4 min read

Namazu Crossfire is currently distributed as separate Element, which means you must install it separately. We publish stable releases to Maven Central and therefore you can simply include Crossfire as a dependency in your game’s Custom Code. Namazu Crossfire implements a single WebSocket endpoint which will handle the real time matchmaking process.

Prerequisites #

πŸ“ Note

Starting with Namazu Crossfire 1.0.4 and later, the element artifact has been renamed to server with the Classifier element

<dependency>
<groupId>dev.getelements.elements.crossfire</groupId>
<artifactId>server</artifactId>
<version>${crossfire.version}</version>
<classifier>element</classifier>
<scope>provided</scope>
</dependency>
  • This guide assumes you have already completed the steps required to establish an application configuration for Matchmaking. If you haven’t already done so, please work through the process of Creating a Matchmaking Application Configuration
  • You have sufficient access to publish Custom Code to your instance of Namazu Elements.
  • You have reviewed or are familiar with making a Custom Element. Reviewing the Example Code is a great place to start.
  • You have completed the steps necessary to setup your local environment and have git installed.
    • πŸ–₯️ – Windows
    • 🍎 – Mac
    • 🐧 – Linux

Local Development in IDE #

It is possible to run Namazu Crossfire directly in your local IDE along side your game’s custom Element. This enables you to rapidly iterate on development cycles without needing to push to the cloud. Additionally, you can step through and debug any additional endpoint code.

Automatic Method #

The latest Element Example project incorporates Namazu Crossfire right out of the box as of the 3.4 release. However, it must be enabled by activating the profile to include it as a dependency.

    <profiles>
        <profile>
            <id>namazu-crossfire</id>
            <activation>
-               <activeByDefault>false</activeByDefault>
+               <activeByDefault>true</activeByDefault>
            </activation>
            <dependencies>
                <dependency>
                    <groupId>dev.getelements.elements.crossfire</groupId>
                    <artifactId>element</artifactId>
                    <version>${crossfire.version}</version>
                </dependency>
            </dependencies>
        </profile>
    </profiles>

By changing <activeByDefault> to true and rebuilding the project, you have enabled Namazu Crossfire in your local environment.

πŸ“ Note

It is sometimes necessary to clean the build before running as re-running local does not always immediately clean up the classpath. Cleaning the build guarantees a complete rebuild of the element path.

mvn clean

Manual Method #

This guide is here to incorporate Crossfire into an existing game.

1. Changes to <dependencies> in pom.xml #

Crossfire has a single dependency that needs to be added to your Element.

        <dependency>
            <groupId>dev.getelements.elements.crossfire</groupId>
            <artifactId>element</artifactId>
            <version>${crossfire.version}</version>
        </dependency>

2. Update <properties> in pom.xml #

    <properties>
        <! -- Existing Properties -->
        <crossfire.version>1.0.4</crossfire.version>
    </properties>

πŸ“ Note

Do not replace the entire properties section. only add <crossfire.version>1.0.4</crossfire.version> to the existing properties

<crossfire.version>1.0.2</crossfire.version>

3. Make the SDK Aware of Namazu Crossfire #

In order to make the SDK aware of the Crossfire Element, you must update the loader to include it in the application.

        // Create the local instance of the Elements server
        final var local = ElementsLocalBuilder.getDefault()
                .withElementNamed(
                        "example",
                        "com.mystudio.mygame",
                        PropertiesAttributes.wrap(elementProperties))
+               .withElementNamed(
+                       "example",
+                       "dev.getelements.elements.crossfire",
+                       PropertiesAttributes.wrap(crossfireProperties))
                .build();

πŸ“ Note

Be sure to replace the name “example” with the application you are using in your particular case.

Verify Successful Deployment #

After enabling in your local IDE, perform the following steps to ensure that Namazu Crossfire was successfully added to the project.

  • Launch the Namazu Elements in your IDE.
  • Visit your local instance’s browser at http://localhost:8080/admin/
  • Login using the default credentials or credentials you know to work for a SUPERUSER
    • Default Username: root
    • Default Password: example
  • Check the left-hand side of the Namazu Elements Admin Panel
  • Near the bottom you should see your game’s Element along side Namazu Crossfire
  • Ensure that “CLEAN” appears under the application, in this case the application is named “example”
  • Click on “crossfire” to see the deployment status.

πŸ“ Note

If you use advanced configuration parameters, such as overriding Namazu Crossfire’s default URL these settings may appear slightly differently. The most important things to observe are the deployment status (CLEAN) and the URI from where Namazu Crossfire is hosted.

What are your Feelings
Still stuck? How can we help?

How can we help?

Updated on November 5, 2025
Namazu Crossfire
Table of Contents
  • Prerequisites
  • Local Development in IDE
    • Automatic Method
    • Manual Method
      • 1. Changes to in pom.xml
      • 2. Update in pom.xml
      • 3. Make the SDK Aware of Namazu Crossfire
    • Verify Successful Deployment
  • Documentation
  • Terms of Service
  • Privacy Policy
  • Contact us
  • Linkedin
  • Join our Discord

Namazu Studios LLC is powered by Namazu Elements, an Elemental Computing Inc. product.

Elements
  • Download
  • About Elements
  • Open source
  • Documentation
  • Support
About Namazu
  • Case Studies
  • About Us
  • News
Get in Touch
  • info@namazustudios.com
  • Book a call
  • (619) 862-2890
  • Linkedin
  • Discord

Β©2008-2025Β Namazu Studios. All Rights Reserved.