Hunger
0–100Drains every tick. Run it to zero and starvation starts taking health.
EndCore is the apocalypse framework for FiveM. Zombies, radiation, infection, scavenging and player-built bases, with survival built into the core instead of bolted on.
Other frameworks were built for roleplay and have survival added later. In EndCore, hunger, thirst, radiation, infection, immunity and body temperature are part of every player and tick on the server, so every resource reads the same numbers.
Drains every tick. Run it to zero and starvation starts taking health.
Falls faster than hunger. Dehydration hurts, and nobody sprints on an empty stomach or a dry throat.
Builds up inside hot zones and slowly fades outside them. Above 400, radiation sickness hurts you and eats your immunity.
Once you're infected, it spreads every tick, slowed by your immunity. At 100 it's lethal.
Your defence against infection. It recovers over time, and radiation sickness drains it.
Drifts back toward normal. Below 95°F is hypothermia, above 104°F is heatstroke. Weather and clothing push it around.
Radiation zones, antidotes, bites, fevers: the core exposes every stat as exports and events, and the EndCore library gives your resource inventory, callbacks and UI in the same style.
Survival system docs-- A radiation hot zone: 12 rads every survival tick
exports['en-core']:SetRadiationExposure(source, 12)
-- A bite from an infected zombie
exports['en-core']:AddInfection(source, 15, 'Bitten')
-- RadAway, as a usable inventory item
encore.inventory.registerUsable('radaway', function(source)
local player = exports['en-core']:GetPlayer(source)
if not player or player.Functions.GetRadiation() <= 0 then return end
player.Functions.RemoveRadiation(150, 'RadAway')
return true -- consume one
end)
EndCore isn't a core you have to finish yourself. It ships with the systems that make an apocalypse server playable, each as its own resource you can configure, extend or replace.
A zombie population with AI, hot zones that raise the danger, and corpses worth searching.
en-zombiesDayZ-style grid. Items have a footprint and rotate, bags add storage, and the server re-checks every move.
en-inventoryPlant a territory flag, build walls, doors and storage, pay upkeep in materials, and defend it from raids.
en-propertiesAbandoned vehicles to lockpick, hotwire and claim. Keys are items you can hand over, and fuel, damage and trunks persist.
en-garagesTraders buy and sell for cash, some goods only change hands in trade, and prices move with stock.
en-shopsSkills improve as you use them, and levels earn perk points to spend in skill trees.
en-skillsTeam up to share XP and loot and see each other on the map. Found a permanent group instead of a gang.
en-partyRecipes at workbenches, around campfires and by hand, turning scrap into things that keep you alive.
en-craftingSurvivors with stories, jobs and daily tasks, tracked and rewarded by the server.
en-questsClothes are items you find and wear. A winter jacket keeps you warm; a backpack adds room.
en-clothingPlace traders, garages, quest survivors, workbenches and zones from the admin menu while the server runs.
en-adminHold Alt, look at something and pick what to do. A radial menu covers everything else.
en-targetEvery EndCore interface is built on one design system, en-ui. It looks like scavenged military hardware: warm charcoal, hairline rules, stencil labels and amber readouts. The HUD, inventory, traders and menus all read as one game.
ESX and QBCore are great for city roleplay. If your server is about surviving the end of the world, you'll spend months working against them. EndCore starts where they stop.
Survival stats, zombies, looting, bases and barter are the foundation, not addons. Ambient traffic, pedestrians and police are switched off, leaving an empty world.
Callbacks, commands, keybinds, streaming and UI services, with no ox_lib, ox_inventory or ox_target to keep in sync. The only third-party dependency is oxmysql.
Compatibility bridges answer QB-Core, QBX and ESX exports, so many existing scripts run unchanged while you move over.
The server owns the numbers. It re-checks inventory moves, runs the survival simulation and rewards quests, so a modified client can't cheat past them.
Download EndCore and build your server yourself, add ready-made resources, or have the team behind EndCore build it with you.
$0 free forever
Ready-made resources for your EndCore server, so you can add features without writing them yourself.
The studio that develops EndCore. Tell Fxora what your server needs and they'll build it properly.
resources/[encore] on your FXServer.mysql_connection_string at an empty database. en-core creates its tables on first start.set mysql_connection_string "mysql://user:password@localhost/endcore?charset=utf8mb4"
sv_enforceGameBuild 3095
ensure oxmysql
# EndCore Framework
ensure en-ui
ensure en-core
ensure [encore]
# Staff
add_ace group.admin command allow
add_ace group.admin encore.bypassclosed allow
Yes. EndCore is free and open source, and the whole framework is on GitHub. You pay for nothing unless you want custom development or addon resources.
Many will. en-core ships compatibility bridges that answer exports['qb-core'], exports['qbx_core'] and exports['es_extended'] calls, so a lot of scripts run unchanged. There are limits: EndCore has no gangs, QB server events aren't fired, and ESX societies, billing and licences don't exist. See Compatibility bridges before you rely on a script.
No. EndCore has its own library (callbacks, commands, keybinds, UI services), its own spatial grid inventory and its own look-at targeting. The only third-party dependency is oxmysql.
It's a survival framework. Hunger, thirst, radiation, infection, immunity and body temperature live in the core and tick on the server. Jobs still exist, but gangs are replaced by player-founded groups and temporary parties, which suit survival servers better.
Yes. Every feature is its own en-* resource, and the library falls back gracefully when one isn't running: without en-party everyone is a party of one, and without en-skills every bonus is zero. You can also switch the survival simulation off in en-core's config.
An FXServer artifact of 7290 or newer with OneSync enabled, oxmysql, and a MySQL or MariaDB database. The reference server enforces game build 3095. The installation guide walks you through it.
Fxora, the studio that develops EndCore, takes on custom development: new systems, full server builds and ports of your existing scripts.
Upgrade Scripts has addon resources for EndCore servers.
Download EndCore free, or have Fxora build your server with you.