Introduction
BeyondSurvival is a FiveM framework for zombie survival servers with RPG progression. I wrote it from zero. It’s not ESX, not QBCore, not vRP. The only external thing it needs is oxmysql, and that’s a database driver, not a framework.
If you have ESX scripts you can’t live without there is bs_esx_bridge, a shim that answers getSharedObject() against BeyondSurvival. It covers the common stuff, not everything. Test your script before you promise it to players.
What you get
Section titled “What you get”Everything lives in resources/[beyond]/. One folder per system, all prefixed bs_:
- bs_core - players, characters, money, XP, needs, database migrations. Everything else sits on top of this.
- bs_zombies - the walkers. Server registry, sectors, a simulation of individual zombies, hordes, and since October a networked mode where every walker is a real OneSync ped.
- bs_inventory - grid inventory, containers, crafting, hotbar, loadouts.
- bs_medical - going down instead of dying, bleed out, revive, carry, corpses you can loot.
- bs_weapons / bs_skills - attachments as items, magazines, recoil, skill trees and perks.
- bs_factions / bs_faction_bases - factions, squads, treasury, ranks, sanctions, jail, flags and bases, faction levels.
- bs_boosters / bs_gadgets - personal buffs and deployables (drone, turret, medic beacon, decoy).
- bs_drugs - drugs, cigarettes, addiction and withdrawal.
- bs_events - airdrops, supply stashes, military convoys, horde waves on a schedule.
- bs_vip - cosmetic VIP tiers. No gameplay advantage, on purpose.
- bs_config - the F1 console. Tune about 300 values live, save profiles, see who changed what.
- bs_guard - anti-cheat detection. It logs and tells staff, it never kicks or bans by itself.
- bs_admin - the F10 staff menu.
Plus the smaller ones: traders, vehicles, building, stashes, recycler, mining, extraction zones, emotes, chat, radial menu, scoreboard, loading screen, character select. The API reference has one page for each.
Who these docs are for
Section titled “Who these docs are for”- Owners (this section) - you want to install it, configure it and keep it running. No Lua needed for most of it, the F1 console covers a lot.
- Developers - you want to write your own resource on top of bs_core or change ours. Start with Architecture.
Things to know before you start
Section titled “Things to know before you start”- It’s built for OneSync and game build 3095. Don’t run it without OneSync.
- Ambient population is off at the server (
onesync_population false). The world is empty on purpose, the zombies are the population. - The map is a whole-map post-apocalypse conversion (
[the_apocalypse_project]). It’s heavy, see Performance. - Most config files have long comments explaining why a value is what it is. Read them before you change things, a lot of them were learned the hard way.
bs19.org · Privacy · Terms · Cookie settings