Where plugins live
Each plugin is a folder in Resources/Server, loaded when the server starts. Some plugins come with a client mod too (an in-game interface), which goes in Resources/Client like any other mod.
Two popular ones
- CobaltEssentials (GPL-3.0): permission levels, admin chat commands, per-rank car limits and a whitelist. It logs chat itself, so turn LogChat off to avoid every message twice.
- Nickel (GPL-3.0): roles, in-game commands, temporary bans and mutes, with its own database; its optional interface is a client mod from its page.
Both loaded on BeamMP-Server 3.9.3 in our tests. On Flux the Plugins tab installs either in one click from its GitHub release.
Installing any plugin on Flux
- Upload the plugin's .zip as its author ships it in the Plugins tab. A Resources folder, Server and Client folders, a plugin folder or loose .lua files are all understood.
- While the server runs, the change waits: press Apply and restart (about ten seconds). BeamMP cannot take a plugin folder changing under it: in our tests it stopped.
- An update keeps the files the plugin wrote (its settings, its data); turning a plugin off keeps everything.
Tip:Plugins and their data are in every backup. Every Flux server also runs FluxAdmin, our small plugin for the panel's player list, kicks and bans; it is put back on every start.
Frequently asked questions
Do players need to install plugins?
No. Plugins run on the server. A plugin with a client interface ships a client mod, which the server sends like any mod.
Why did my plugin not load?
Plugins load when the server starts: restart after adding one. The Console tab shows what each plugin printed as it loaded.