FiveM logs you can search, with alerts on Discord.

Why Discord channels are a poor place to keep logs

Most FiveM servers start logging the same way: every resource posts an embed to a Discord webhook, one channel per category. It works on day one. By month three the channels hold hundreds of thousands of messages, Discord search cannot filter on an amount or a license, webhook rate limits drop events during busy hours, and screenshots attached to those messages turn into links that expire.

BasiX keeps the part that works — a notification in Discord when something needs a human — and moves the record itself somewhere it can be queried. Your staff still gets pinged; they just click through to a search instead of scrolling.

Sending events from FiveM

Install the basix resource, set your key in server.cfg, and call exports.basix:info, warn, error or debug from any resource. Events are buffered and sent every two seconds in one request, and up to 400 are kept in memory if the API cannot be reached, so a short outage does not lose a ban record. The calling resource is filled in for you.

Anything that can make an HTTP request can log too: POST https://basix.media/api/v1/logs with a dataset and up to 500 events per request. The endpoint accepts 240 requests per minute per key, which is plenty once events are batched.

exports.basix:log('info', 'Player bought a car', {
    player = GetPlayerIdentifierByType(source, 'license'),
    metadata = { model = 'sultan', price = 25000 },
})

Player logs: one profile per player

Every event sent with a player field builds a profile: first and last seen, event counts per category, and identifiers found in the metadata — license, license2, discord, steam, fivem, xbl, live, rockstar and citizenid. Your team can add a display name, internal notes and custom fields, so the history of a player who keeps getting reported is one page rather than a search across ten channels.

Categories, columns and saved views

Each dataset can become a category with a label, colour, icon and group, and with columns read from the metadata: an economy log can show amount and source as real columns, a vehicle log the plate. Saved views store a set of filters — categories, levels, player, resource, text and a time range — and are shared with your team by default, so the moderator on shift opens the same view the head admin built.

Discord alerts when it matters

An alert rule fires when a number of matching events arrive within a window — for example three warn or error events in the economy category within five minutes, with metadata source equal to admin. It then stays quiet for a cooldown you choose, so a burst does not flood the channel. Alerts post to a Discord webhook, to your own webhook endpoints, or both.

Alert rules come with a plan: 5 on Starter, up to 100 on Ultra.

Retention and price

Logs are included in every plan, not sold as a separate subscription. They count toward the same storage as your files and are kept for the retention of your plan: Free 3 days, Starter 30 days, Pro 90 days, Business 90 days, Ultra 180 days. A full quota answers with an explicit error instead of silently dropping events.