Brick Status installation

Brick Status combines a standalone Node.js Discord bot with a small framework-independent FiveM resource. It does not require Brick Bridge, QBCore, Qbox, ESX, or txAdmin.

Requirements

• Node.js 22.12 or newer
• a Discord application and bot user
• network access from the bot to the FiveM dynamic.json endpoint
• the bot and FXServer on the same machine when whitelist mode is enabled

Discord application

1. Create an application in the Discord Developer Portal.
2. Add a bot user. Do not reuse a txAdmin token.
3. Under Installation, enable bot and applications.commands.
4. Grant View Channels, Send Messages, Embed Links, and Read Message History.
5. Install the application in the Discord server configured by DISCORD_GUILD_ID.
6. Enable Server Members Intent only when a Discord whitelist mode is used.

Message Content and Presence intents are not required.

Install the bot

Copy-Item .env.example .env
npm install

Set the three Discord values in .env, edit config.js, and start the service:

npm start

Never commit or share .env. Run the bot through a process manager or operating-system service so the status message remains available while FXServer restarts.

In Discord, run /status install in the desired channel. Use /status refresh for an immediate update and /status remove to delete the managed message.

Install the FiveM resource

Copy fivem/brick_status into the server resources folder and add:

ensure brick_status

If you changed WHITELIST_PORT, set the matching loopback URL before the resource starts:

set brick_status_whitelist_url "http://127.0.0.1:30130/whitelist/check"
ensure brick_status

Keep this service on 127.0.0.1. It intentionally has no public listener or remote authentication.