Independent founder-led studio
Systems that make roleplay matter.
Riftvane builds gameplay systems for FiveM roleplay servers that are configurable enough to fit your economy, integrate cleanly with the framework you already run, and stay supportable once they are live.
Store link coming soon
Explore TrapNexusFlagship product
TrapNexus
A deep, configurable drug-gameplay system for FiveM roleplay servers.
TrapNexus covers the whole loop through one economy engine and one administration surface: players gather ingredients from world zones, craft them into product, and move that product on the street, from a vehicle, or through timed bulk contracts. Prices, random outcomes, inventory changes and progression are all decided on the server, and every value is editable in game without a restart.
- Price
- $49.99one-time
- Status
- Alpha
- Version
- 0.3.0-alpha
- Updated
- 5 September 2026
- Licence
- Up to 3 servers
Why Riftvane
How these systems are built
Operating principles rather than performance claims. Everything below describes how the work is done, and can be checked against the documentation and the changelog.
Deep configuration
Prices, yields, durations, recipes, zones and ranks are data, not hard-coded values. Most of it is editable in game and takes effect without a restart, because tuning an economy is something you do repeatedly against your own server rather than once at install.
Verified rather than assumed compatibility
A framework is listed as tested only when the whole loop has been run against it. Combinations that share a code path but have not been run are labelled as such, and the difference is never collapsed into a single tick.
Documentation-first deployment
Installation, configuration and integration are written down before they are asked about. If a question can only be answered in a support ticket, the documentation has a gap worth fixing.
Server-authoritative design
The client is treated as untrusted input. Values that decide money, items or progression are computed on the server, and a request that cannot be validated is rejected rather than trusted.
Transparent changelogs and limitations
Known limitations are published on the product page rather than discovered after purchase, and every release records what changed, what broke, and what still does not work.
Evidence
What can be checked before you buy
Screenshots, a demonstration and performance measurements are published as they are produced. Nothing stands in for them in the meantime.
What exists today, and what does not
There is no demonstration video, screenshot gallery or published performance measurement yet, so none is shown. What can be read right now is the full documentation, the changelog for every release, and the known limitations on the product page — which is the same material that would otherwise be summarised into a claim.
Support
How support actually works here
Riftvane is run by one person. That shapes what support can honestly promise: direct answers from whoever wrote the code, within published hours, rather than a queue staffed around the clock.
01
Check the documentation
Installation, configuration and troubleshooting are written up in full. Most problems are a dependency version or a configuration value, and both are covered there.
02
Have your purchase details ready
Support covers licensed installations, so a ticket needs to be matched to a purchase before it can be worked on.
03
Open a private ticket in Discord
Tickets are private. Include the checklist from the support page — version, framework, dependency versions, logs and reproduction steps — and the first reply can be about the actual problem.
04
Get a reply from the person who wrote it
Riftvane is an independent founder-led studio, so the reply comes from the person who built the resource. That means context is never lost in a handoff, and it means replies arrive within published hours rather than instantly.
Discord is where support and community happen, and it is optional. TrapNexus neither requires nor contacts Discord: nothing about installing, configuring or running the resource depends on it.
Latest release
TrapNexus 0.3.0-alpha
Makes the cost of a failed street deal a server decision, and tightens buyer verification now that it can be relied on.
- Security
- Sales that cannot be matched to a verified buyer entity are rejected rather than accepted as unverified. Servers that see legitimate failures can restore the previous behaviour with a single configuration change.
- Added
- A configuration option decides whether a robbery takes the product being offered. It defaults to the previous behaviour, where the seller keeps their stock and the hostile buyer is the penalty.
- An economy settings row written by an earlier version is backfilled on load with any option added since, so new settings arrive at their documented default and appear in the administration console instead of staying invisible. Values already set by an administrator are never overwritten.
TrapNexus is $49.99, once, for up to three servers.
It is alpha software: the loop is complete and has been tested end to end on live QBCore and ESX Legacy servers, and it is priced for buying in early rather than for a finished suite. The known limitations are published in full before you decide.
Store link coming soon
Product details