Skip to content

Compatibility

What BeamJoy runs on, and what to check when something that worked last month does not.

BeamNG.drive 0.40
BeamMP 4.23.1
BeamJoy 2.1.1, server build 2498, client build 2785

BeamJoy targets the current BeamNG release. It does not carry fallbacks for the previous one: when the game updates, BeamJoy follows it rather than supporting both.

BeamJoy carries more than one version, deliberately, and knowing which is which turns a confusing symptom into an obvious one.

Number Where it lives What it is
Server version and build Server/BeamJoyServer/ What your server is running.
Client version and build the client mod What players’ games are running.
UI build inside the interface code A copy of the client build, baked into the interface itself.

The server and client versions are independent and are not required to match. A server-side fix can be deployed without players updating anything, and the changelog says which kind each release is.

The game’s interface layer runs in a browser engine and caches its own copy of BeamJoy’s interface. That cache can survive an update, so the interface a player sees can be older than the BeamJoy their game actually loaded — and stale code cannot reliably detect that it is stale.

So a copy of the build number is baked into the interface source itself. BeamJoy compares it with the real one and shows the banner when they differ:

Your BeamJoy UI looks out of date. Close BeamNG completely, clear your cache, then relaunch.

That is why the fix is always close the game fully, clear the cache, relaunch — see troubleshooting.

Players do not download the client mod themselves and cannot install the wrong one: BeamMP hands them whatever the server is serving, each time they connect. A player’s own mods folder is not what runs on your server.

The practical consequence: when a player reports an old-looking interface, it is a cache question, not a download question.

The 2.1 release was largely about following the game to 0.40. The changes worth knowing, because they explain behaviour that looks odd otherwise:

  • Translations moved. The game changed which files it accepts as translations, so BeamJoy’s were silently ignored from 0.40 and every window fell back to English. Fixed in 2.1, with all thirteen translations filled in and Italian added.
  • Drift and drag scores moved. Since 0.40 the game draws them in container apps that BeamMP’s multiplayer layout does not have, so BeamJoy adds its own.
  • What a player may do in their car is now decided from their presence in it, which interacts with BeamMP setting the game state to multiplayer — the reason driving your own car needed fixing on 0.40.
  • Seat figures are local. The figures the game puts in seats are the viewer’s own players only, so BeamJoy disables them on other players’ cars.

Two features shell out rather than reimplementing network code:

Feature Needs
Discord webhooks curl — ships with Windows 10 version 1803 and later, and virtually every Linux distribution.
The self-updater curl, PowerShell on Windows, unzip and zip on Linux.

Each says plainly which tool is missing and how to install it, and neither failure touches anything already installed.

The mod’s own CHANGELOG.md is the authority on what changed in each release, down to individual fixes and the reasoning behind them. It is in the repository and in your install, and it is far more detailed than a release note. The GitHub releases carry the same per-version summaries.