> For the complete documentation index, see [llms.txt](https://docs.linuxgsm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxgsm.com/game-servers/battlefront-eternal.md).

# Battlefront Eternal

## Requirements

* A Steam account that owns STAR WARS Battlefront (Classic, 2004). Set `steamuser` and `steampass` in your LinuxGSM instance config. Anonymous SteamCMD download does not work.
* At least 2 GB of RAM. The retail game download is about 2.8 GB, and prepared data uses about 2.2 GB more.
* glibc 2.28 or newer.

LinuxGSM downloads the native Battlefront Eternal server and Node.js 24, then prepares server data from your owned retail game files. Battlefront Eternal is still in development preview.

## First Start

1. Set the Steam account in `lgsm/config-lgsm/bfeserver/bfeserver.cfg`, then install the server. LinuxGSM downloads and prepares the game data.
2. Edit `serverfiles/bfe-state/config.json` to set the server name, ports, player limit and map rotation.
3. To list the server publicly, read the project's online notice and set `"onlineNoticeAccepted": true` in `config.json`. The default is `false`, so the server is limited to LAN or direct connection until you accept it.

## Server Settings

Stop the server before editing:

```
serverfiles/bfe-state/config.json
```

| Setting                | Default      | Description                                                       |
| ---------------------- | ------------ | ----------------------------------------------------------------- |
| `name`                 | `SERVERNAME` | Name shown to players.                                            |
| `gamePort`             | `18451`      | Game UDP port and HTTP server information port.                   |
| `discoveryPort`        | `18452`      | LAN discovery port.                                               |
| `maxPlayers`           | `64`         | Player limit.                                                     |
| `rotation`             | Six maps     | Maps and modes played in order.                                   |
| `onlineNoticeAccepted` | `false`      | Set to `true` after accepting the online notice to list publicly. |

The LinuxGSM instance setting `healthport="18450"` controls the local health and admin endpoint. Each instance on the same host needs a different health port as well as different game and discovery ports. Additional start parameters can go in `extraparams`. See [start parameters](https://docs.linuxgsm.com/configuration/start-parameters.md#extra-parameters).

## Ports

| Description                           | Port    | Protocol        |
| ------------------------------------- | ------- | --------------- |
| Local health and admin                | `18450` | TCP, local only |
| Game                                  | `18451` | UDP             |
| Server information and LinuxGSM query | `18451` | TCP             |
| LAN discovery                         | `18452` | UDP             |

Change `gamePort` and `discoveryPort` in `config.json`, and `healthport` in the LinuxGSM instance config. Open or publish the game and server information ports for remote players. LinuxGSM checks the TCP server information port when monitoring.

## Updates

`update` and `check-update` check Battlefront Eternal releases and Node.js 24. A Node-only update also restarts the server. `validate` checks the owned retail game files; it does not replace the Battlefront Eternal server, prepared data or Node.js. LinuxGSM prepares game data again when the server release changes the preparation tools.

## Stopping

LinuxGSM uses [stop mode](https://docs.linuxgsm.com/features/stop-mode.md) 2, which sends CTRL+c.

## Files

| Path                                | Contents                                           |
| ----------------------------------- | -------------------------------------------------- |
| `serverfiles/GameData/`             | Retail game files downloaded through SteamCMD.     |
| `serverfiles/bfe/`                  | Battlefront Eternal server and preparation tools.  |
| `serverfiles/bfe-data/`             | Prepared game data.                                |
| `serverfiles/bfe-state/`            | Server config, identity, operator token and state. |
| `serverfiles/node/`                 | Node.js runtime.                                   |
| `log/script/<instance>-prepare.log` | Game data preparation log.                         |

{% hint style="warning" %}
`bfe-state/` contains identity and operator credentials. Keep backups private.
{% endhint %}

## Server Resources

* [Battlefront Eternal server guide](https://battlefronteternal.com/servers/)
* [Battlefront Eternal releases](https://get.battlefronteternal.com/downloads/latest)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.linuxgsm.com/game-servers/battlefront-eternal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
