Skip to content
ND

ND_Core

Framework Supported

ND_Core admin panel and staff tools

ND_Core keeps a character’s job among their groups, and FiveStaff reads it there

Cash and bank are kept on the character, items are ox_inventory’s, and a job is whichever of the character’s groups is marked as one. FiveStaff reads and changes each of those where ND_Core keeps it, through ND_Core while the character is loaded and through the database when they are not.

panel.fivestaff.gg
The FiveStaff panel, as staff on an ND_Core server use it

Shown on our demo server, which runs QBCore

ND What FiveStaff sees on ND_Core

  • Characters name and groups
  • Money cash and bank
  • Jobs the group marked as a job
  • Items ox_inventory
  • Vehicles by plate

Framework data

What FiveStaff reads and changes on ND_Core

What FiveStaff reads

  • The character and the names on it
  • Every group the character holds, and the one marked as their job
  • Cash and bank, from the character itself
  • Items out of ox_inventory
  • Owned vehicles, by plate

What staff can change

  • Set cash or bank
  • Set an item count, or remove an item
  • Set the job
  • Give or take an owned vehicle
  • Move a vehicle to another character, or change its plate

Every one of these goes through the same pipeline as a ban: permission-checked and written to the audit log with what it was before. Item, money, job and vehicle edits can be put back in one press from the player’s profile.

In the panel

The screens your staff will use

Real screens from the panel, taken on our demo server, which runs QBCore. On yours, the accounts and jobs are ND_Core’s own.

One character: a screen from the FiveStaff panel
One character Each money account along the top, their vehicles, inventory and log in tabs, and who they are beside it, with a card to change something.
Every owned vehicle: a screen from the FiveStaff panel
Every owned vehicle Every owned vehicle and where it is. Move one to another character, change its plate or delete it, and each goes on the audit log.
The player log: a screen from the FiveStaff panel
The player log Money, items, vehicles and deaths, searchable by player, item, amount and time, with what is collected beside it.
Every character: a screen from the FiveStaff panel
Every character Search by name, citizen id, licence or phone number, and filter by job. Read from your game database, so characters who are offline are here too.
One page per player: a screen from the FiveStaff panel
One page per player Their history newest first, their characters, reports, bans and trust in tabs, and a card to act on them.

Player log

What the player log picks up on ND_Core

ND_Core announces every money change, every new job and every character loaded, and ox_inventory says where every item went. FiveStaff listens to both, with no changes to your scripts.

From ND_Core

  • Cash and bank changes, with the reason where the script gave one
  • A new job, with its rank
  • Characters loaded

With ox_inventory

  • Items dropped, picked up, given, and taken from another player
  • Moves into and out of stashes, boots and gloveboxes, with the plate
  • Shop purchases with the price, and crafts with what went into them
  • Items created from nothing, with the script that made them
  • Items used, and one player searching another

On every server

  • Joins and leaves
  • Deaths and kills, from the game itself: how, by whom and with what
  • txAdmin’s scheduled restarts and shutdowns, and resources stopped or started by hand
  • Every line your scripts already send to qb-log, kept word for word
  • Your own events, with one line of Lua: exports.fivestaff:logEvent
Your own script, server side
-- one line, and it is searchable by item and amount
exports.fivestaff:logEvent(source, 'drugs.weed.sold', {
    item = 'weed_brick', amount = 5, price = 2500
})

The log is off until you switch it on, and a category you leave off costs your server nothing. The player log and alerts

Your resources

The scripts it works with on ND_Core

A server picks its inventory, its ambulance job and its clothing separately from its framework. FiveStaff looks for what is actually running and works through it.

Inventory

ND_Core runs with ox_inventory and keeps no items of its own, so items are read and changed through ox_inventory. Cash and bank stay on the character.

  • ox_inventory

Revive

Revive uses ND_Core’s own revive, the one ND_Ambulance listens for, so its knocked-down and dead states are cleared too.

  • ND_Ambulance

The small print

Where ND_Core is different

The details a tool gets wrong when it treats every framework as the same one, and what FiveStaff does instead.

A job is a group marked as one

ND_Core keeps a character’s jobs and other groups in one list, and marks which of them is the job. FiveStaff reads that list as it is and sets the job in it, rather than treating the first group it finds as somebody’s job.

Items are ox_inventory’s

ND_Core runs with ox_inventory and keeps no items of its own. Item edits go to ox_inventory, which is where the player will see them, while cash and bank stay on the character where ND_Core keeps them.

Revive uses ND_Core’s own

ND_Core has a revive of its own, and ND_Ambulance listens for it. FiveStaff uses it, so the knocked-down or dead state ND_Ambulance keeps is cleared too, rather than a player being stood up while the script still thinks they are down.

No Food and drink with ND_Status

ND_Status keeps hunger and thirst on the player’s own game, and the only way your server can fill them heals the player as well. FiveStaff does not offer Food and drink there rather than do something you did not press. ND_Core keeps no stress, so there is no Calm stress either.

Install

Put it on your ND_Core server

One resource, a few lines in server.cfg, and no changes to your framework or your scripts.

  1. 1

    Add your server

    Sign in to the panel with Discord, press Add server, give it a name and choose a plan.

  2. 2

    Download the resource

    On your server’s dashboard, press Download the resource. The fivestaff folder inside already holds your server key, so there is nothing to fill in.

  3. 3

    Add it to server.cfg

    Upload the folder to your resources, keeping its name exactly fivestaff, and add the lines opposite anywhere after ND_Core and ox_inventory start.

  4. 4

    Restart and check

    Restart, or type ensure fivestaff in the server console. Within seconds the dashboard says Online. FiveStaff finds ND_Core from its own resource, and uses ox_inventory for items.

  5. 5

    Connect your game database

    Under Settings, Database, connect a read-only database user and choose Other as the table layout. Pick ND_Core’s tables yourself on any plan, or let FiveStaff work them out on Pro, and confirm before anything is read.

server.cfg
ensure fivestaff

# lets FiveStaff update itself, and staff start and stop resources
add_ace resource.fivestaff command.restart allow
add_ace resource.fivestaff command.start allow
add_ace resource.fivestaff command.stop allow

Only if it guessed wrong

Most servers never need these. They go above ensure fivestaff.

set fivestaff_framework "nd"

When FiveStaff starts, the server console says which framework and inventory it is using. Try one edit on a test character before your staff use it on a player.

Why staff use it

Built for the people who keep an ND_Core server fair

A record of every player, a log of every action, and powers handed out one at a time.

One record for every player

Whichever character somebody is on, their warnings, bans, reports and notes sit on one profile, and a ban checks every identifier they connect with — so a new account is not a fresh start on your ND_Core server.

Nobody needs in-game admin

Your team is a list in the panel. Staff act from the panel, from Discord or in game with /staff, and you hand out no ace permissions to make that work.

Each power is its own permission

Edit money, Edit inventories, Edit vehicles and Edit jobs are separate permissions, so a trial moderator can read the player log without being able to set a balance.

Every change has a before

The audit log records who did what and what it was before, and item, money, job and vehicle edits can be put back in one press.

Questions people ask first

Does FiveStaff read ND_Core’s cash and bank?

Yes. ND_Core keeps both on the character, and FiveStaff reads and sets them there: through ND_Core while the character is loaded, and in your database when they are not.

Do item edits go through ox_inventory?

Yes. ND_Core runs with ox_inventory and keeps no items of its own, so a character’s items are read and changed there, which is where the player will see them.

How is a job set on ND_Core?

ND_Core keeps a character’s jobs and other groups in one list and marks which of them is the job. FiveStaff reads that list as it is, and sets the job in it.

Does Revive work on ND_Core?

Yes. It uses ND_Core’s own revive, which ND_Ambulance listens for, so the knocked-down or dead state ND_Ambulance keeps is cleared too.

Why is there no Food and drink?

ND_Status keeps hunger and thirst on the player’s own game rather than on your server, and the only way your server can fill them heals the player too. Rather than heal somebody when you pressed Food and drink, FiveStaff does not offer it there. ND_Core keeps no stress, so there is no Calm stress either.

Can staff edit a character who is offline?

Yes. A character who is not on the server is edited in your database, through your game server, so your game server has to be online for any edit.

What does the player log pick up without any changes?

Every cash and bank change ND_Core reports; a new job and its rank; characters loaded; where every item went in ox_inventory; and joins, leaves and deaths.

Can an edit be undone?

Item, money, job and vehicle edits are written to the audit log with what they were before, and can be put back from the player’s profile under Framework, Edits.

Point it at your ND_Core server

Sign in with Discord, add your server, and drop one resource into it. Free for 3 staff, and nothing to cancel if it is not for you.