EndCore Framework
Open-source framework for FiveM

Build the server that outlives the end

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.

v1.2.0 Free & open source OneSync No ox dependencies
24Resources included
6Survival stats in the core
3Bridges: QB, QBX, ESX
$0Free & open source
Lua 5.4JavaScript NUIoxmysqlOneSyncFiveM
Survival lives in the core

Six ways to die, simulated on the server

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.

Hunger

0–100

Drains every tick. Run it to zero and starvation starts taking health.

Thirst

0–100

Falls faster than hunger. Dehydration hurts, and nobody sprints on an empty stomach or a dry throat.

Radiation

0–1000

Builds up inside hot zones and slowly fades outside them. Above 400, radiation sickness hurts you and eats your immunity.

Infection

0–100

Once you're infected, it spreads every tick, slowed by your immunity. At 100 it's lethal.

Immunity

0–100

Your defence against infection. It recovers over time, and radiation sickness drains it.

Temperature

98.6°F

Drifts back toward normal. Below 95°F is hypothermia, above 104°F is heatstroke. Weather and clothing push it around.

One API for every resource

Write survival features in a few lines

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
lua
-- 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)
Features

Everything a survival server needs, from day one

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.

Zombies & hot zones

A zombie population with AI, hot zones that raise the danger, and corpses worth searching.

en-zombies

Spatial grid inventory

DayZ-style grid. Items have a footprint and rotate, bags add storage, and the server re-checks every move.

en-inventory

Player-built bases

Plant a territory flag, build walls, doors and storage, pay upkeep in materials, and defend it from raids.

en-properties

Scavenged vehicles

Abandoned vehicles to lockpick, hotwire and claim. Keys are items you can hand over, and fuel, damage and trunks persist.

en-garages

Barter economy

Traders buy and sell for cash, some goods only change hands in trade, and prices move with stock.

en-shops

Skills & perks

Skills improve as you use them, and levels earn perk points to spend in skill trees.

en-skills

Parties & groups

Team up to share XP and loot and see each other on the map. Found a permanent group instead of a gang.

en-party

Crafting

Recipes at workbenches, around campfires and by hand, turning scrap into things that keep you alive.

en-crafting

Quests

Survivors with stories, jobs and daily tasks, tracked and rewarded by the server.

en-quests

Clothes that matter

Clothes are items you find and wear. A winter jacket keeps you warm; a backpack adds room.

en-clothing

In-game world builder

Place traders, garages, quest survivors, workbenches and zones from the admin menu while the server runs.

en-admin

Look-at interaction

Hold Alt, look at something and pick what to do. A radial menu covers everything else.

en-target
One visual identity

Every screen looks like it belongs to the same world

Every 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.

  • Grid inventory. Items take real space, rotate, and stack into backpacks, stashes and vehicle trunks.
  • Shared services. Notifications, progress bars, dialogs and prompts come from one place, so they always match.
  • Safe by default. Player-written text is always rendered as text, never as markup.
Design system docs
Pockets & rig 18.4 / 30.0 kg
Assault rifle
First aid kit
Water2
Canned beans3
Rad pills4
Bandage5
Rifle ammo60
Jerrycan
Winter jacket
Pistol
Lockpick2
Cash1,240
Antibiotics
Repair kit
Radio
MRE
Dirty water
Breach charge
Duct tape2
Cloth6
GPS
First aid kit · 2 × 2 Drag · Rotate · Split
Why EndCore

Why this and not another framework?

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.

Built for the apocalypse

Survival stats, zombies, looting, bases and barter are the foundation, not addons. Ambient traffic, pedestrians and police are switched off, leaving an empty world.

Its own library

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.

Brings your scripts along

Compatibility bridges answer QB-Core, QBX and ESX exports, so many existing scripts run unchanged while you move over.

Server-authoritative

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.

How to get it

Free framework. Expert help when you want it.

Download EndCore and build your server yourself, add ready-made resources, or have the team behind EndCore build it with you.

Addon resources

Upgrade Scripts

Ready-made resources for your EndCore server, so you can add features without writing them yourself.

  • Built for EndCore servers
  • Drop in and configure
  • Spend your time on your world, not boilerplate
Browse addons
Custom development

Fxora

The studio that develops EndCore. Tell Fxora what your server needs and they'll build it properly.

  • Custom systems and resources
  • Full server builds on EndCore
  • Ports of your existing scripts
Talk to Fxora
Quick start

From empty server to first zombie in minutes

  1. Download EndCorePut the resources in resources/[encore] on your FXServer.
  2. Add oxmysqlPoint mysql_connection_string at an empty database. en-core creates its tables on first start.
  3. Ensure the resourcesStart en-ui, then en-core, then the rest of the category.
  4. Join and surviveCreate a character, then open the zombie server guide to shape your world.
cfg
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
Full installation guide
FAQ

Questions before you commit

Is EndCore really free?

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.

Will my QB-Core, QBX or ESX scripts work?

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.

Do I need ox_lib, ox_inventory or ox_target?

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.

Is EndCore a roleplay framework?

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.

Can I leave out the parts I don't want?

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.

What do I need to run it?

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.

Can someone build a custom feature or a whole server for me?

Fxora, the studio that develops EndCore, takes on custom development: new systems, full server builds and ports of your existing scripts.

Where can I get more resources for my server?

Upgrade Scripts has addon resources for EndCore servers.

The world ended. Your server doesn't have to.

Download EndCore free, or have Fxora build your server with you.