NB Trains
Own the rails. Player-owned locomotives for RedM — RSGCore and VORP Core, one resource.
Most train scripts give players a locomotive and stop there. NB Trains gives them a business: buy an engine, name it, fuel it, keep it running, haul freight and passengers across two circuits, and sink the profits back into upgrades that actually change how the thing drives.
Runs on RSGCore or VORP Core. The framework is detected at runtime — same folder, same config, no separate builds to keep in sync.
What players get
21 purchasable locomotives From a hand cart up to heavy engines topping 30 speed. Every unit has its own top speed, coal consumption rate and coal capacity, so the cheap engines stay useful and the expensive ones feel earned.
Name your locomotive Trains are named at purchase and renameable afterwards. The name follows the engine through the UI, the garage list and the cargo stash.
Coal, not magic Engines burn coal at their own rate and stop when the tender runs dry. Refuelling is an inventory item, so coal has a real economy attached to it.
Maintenance that bites Condition decays as the train runs. Let it slide and performance degrades. Repairs consume iron bars and a hammer on a tiered material cost — the worse the condition, the more it costs to bring back.
Upgrades Five speed tiers and five engine tiers per locomotive. Speed upgrades raise top speed; engine upgrades cut coal consumption. Both are material-gated and applied through a timed workbench animation, not an instant menu click.
50-slot cargo stash per train Every locomotive gets its own persistent 500 kg stash, keyed to the train and saved through your inventory's own pipeline. It's how freight actually moves.
Freight contracts Eight delivery missions across two circuits — New Hanover and New Austin. Load the required cargo into the train stash, run it to the drop point, unload on a timed sequence. The server verifies the cargo is genuinely aboard before it pays. A configurable cooldown stops back-to-back farming.
19 passenger runs Named NPC passengers with their own dialogue on boarding and arrival. Pick up at one station, drop at another, get paid on delivery. Missions are filtered to the circuit the train is actually on, so runs stay geographically sane.
28 track junctions Switch the points from the cab and choose your route. Both circuits are wired.
9 stations Valentine, Rhodes, Emerald, Annesburg, Riggs, Saint Denis and three Armadillo approaches, each with map blips and a station menu.
Built for server owners
Dual framework, one codebase RSGCore and VORP Core both supported through a bridge layer. Identity, jobs, money, items and stashes are all abstracted — set Config.Framework = 'auto' and forget about it, or force 'rsg' / 'vorp' if you run non-standard resource names.
Multi-currency purchasing Define your own currencies. Each one is either a money account (cash, bank, or a VORP currency id — dollars, gold, rol) or an inventory item. Price trains in gold bars, missions in cash, keys in something else entirely. Per-train currency overrides are supported, so a premium locomotive can cost something different from the rest of the roster.
Server-authoritative economy Prices, currency, cargo contents and mission cooldowns are all re-validated server-side. The client never decides what a player can afford or whether the freight is really loaded. Inventory capacity is checked before payment is deducted or cargo destroyed, so a full backpack can't eat a purchase or a payout.
Automatic VORP job registration Railroad jobs register themselves with VORP Core on start via RegisterJobs, including grades and labels. Admin commands (/trainjob, /trainjobmulti, /trainjobclear, /trainjobs) let you staff the railroad without touching the database. Permission is group-based or ACE-gated.
Job gating throughout Station access, maintenance, upgrades and passenger contracts each take their own job list. Leave a list empty to open that feature to everyone, or run the railroad as a proper whitelisted company.
Fully configurable Stations, trains, prices, currencies, junctions, missions, passengers, upgrade tiers, material costs, decay rates and every UI string live in config.lua. The config is commented throughout.
Custom NUI Purpose-built interface for the station menu, purchase flow, repair screen, upgrade screen and both mission boards. No dependency on a menu resource for the core loop.
Requirements
Resource
Notes
ox_lib
shared library and notifications
oxmysql
database (v2 or v3)
rsg-core + rsg-inventory
RSGCore servers
vorp_core + vorp_inventory
VORP Core servers
Item definitions ship for both frameworks — a items.txt for rsg-inventory and a ready-to-run vorp_items.sql. One SQL import for the trains table and you're live.
Support
Documentation is included in the package. Support is available in Discord.