# How to Change Max Players on Your Stormworks Server (/docs/stormworks/max-players)



import { Step, Steps } from 'fumadocs-ui/components/steps';

The max players setting controls how many players can be connected to your Stormworks server at the same time. Adjusting this value lets you balance between a lively multiplayer experience and optimal server performance, especially when players are operating complex custom vehicles.

Changing Max Players [#changing-max-players]

<div className="fd-steps">
  <div className="fd-step">
    Open the XGamingServer panel [#1-open-the-xgamingserver-panel]

    Log in to the [XGamingServer panel](https://panel.xgamingserver.com) and select your Stormworks server.
  </div>

  <div className="fd-step">
    Stop your server [#2-stop-your-server]

    Stop your server before editing the config file.
  </div>

  <div className="fd-step">
    Navigate to Files [#3-navigate-to-files]

    In the sidebar, go to `Files`.
  </div>

  <div className="fd-step">
    Open server_config.xml [#4-open-server_configxml]

    Find and open `server_config.xml` in the server root directory.
  </div>

  <div className="fd-step">
    Edit the max_players tag [#5-edit-the-max_players-tag]

    Find the `<max_players>` tag and change the value to your desired player limit:

    ```xml
    <max_players>16</max_players>
    ```
  </div>

  <div className="fd-step">
    Save and start [#6-save-and-start]

    Click **Save** and start your server.

    The new player limit will take effect when the server starts. Players already connected will not be kicked — the limit only prevents new players from joining once the server is full.
  </div>
</div>

Changing Max Players via Startup Tab [#changing-max-players-via-startup-tab]

You may also be able to change max players through the Startup tab:

<div className="fd-steps">
  <div className="fd-step">
    Go to Startup [#1-go-to-startup]

    In the sidebar, click `Startup`.
  </div>

  <div className="fd-step">
    Find the Max Players field [#2-find-the-max-players-field]

    Look for a **Max Players** field.
  </div>

  <div className="fd-step">
    Set the value [#3-set-the-value]

    Enter your desired player count.
  </div>

  <div className="fd-step">
    Save and restart [#4-save-and-restart]

    Save your changes and restart the server.

    > 📝 **Note:** If the max players value is set in both the Startup tab and `server_config.xml`, check which one takes priority by reviewing the server browser listing after restarting.
  </div>
</div>

Recommended Player Counts [#recommended-player-counts]

The ideal player count depends on your server's purpose and the complexity of the vehicles being used:

| Player Count | Experience                                                   | Best For                                         |
| ------------ | ------------------------------------------------------------ | ------------------------------------------------ |
| **2–4**      | Intimate coop sessions with close coordination               | Small friend groups, complex multi-crew vehicles |
| **4–8**      | Active multiplayer with room for multiple vehicle operations | Coop rescue missions, small community servers    |
| **8–16**     | Busy server with multiple concurrent operations              | General multiplayer, community events            |
| **16+**      | Large-scale sessions with many active vehicles               | Big events, large communities                    |

> 💡 **Tip:** Stormworks performance is heavily affected by vehicle complexity. A server with 4 players operating massive, detailed vehicles can use more resources than a server with 16 players using simple boats. Factor in your community's building style when choosing the player limit.

Performance Considerations [#performance-considerations]

Stormworks is unique in that performance depends not just on player count, but on what players are building and spawning:

| Factor                         | Impact                                                                        |
| ------------------------------ | ----------------------------------------------------------------------------- |
| **Vehicle complexity**         | More logic components, sensors, and moving parts = more CPU usage per vehicle |
| **Number of spawned vehicles** | Each active vehicle on the map adds to the physics simulation load            |
| **Player count**               | More players = more network traffic and more potential vehicles               |
| **World state**                | Fires, weather events, and NPC rescues add to the simulation load             |

Tips for Better Performance with More Players [#tips-for-better-performance-with-more-players]

* **Set vehicle limits** — Encourage or enforce limits on how many vehicles each player can spawn
* **Clean up unused vehicles** — Enable the `<cleanup_vehicle>` setting in `server_config.xml` so players can despawn vehicles they're no longer using (see the [configuration guide](/docs/stormworks/configure-your-server))
* **Monitor the console** — Check `Console` on the XGamingServer panel for performance warnings
* **Start conservative** — Begin with a lower player count and increase it as you test performance

How Player Slots Work [#how-player-slots-work]

* **Full server** — When the server reaches the max player limit, new players will see it as full in the server browser and cannot join until a slot opens
* **No slot reservation** — Stormworks does not have a built-in slot reservation system. If you need to guarantee slots for certain players, set the max players slightly above your expected count
* **Rejoining** — If a player disconnects, their slot opens immediately for someone else. There is no reserved reconnect window

> 📝 **Note:** Your XGamingServer plan determines the maximum resources available to your server. If you're experiencing performance issues at high player counts, consider upgrading your plan or optimizing vehicle complexity on your server.

If you get stuck at any time, you can join our [Discord](https://discord.xgamingserver.com/).