Install & load order

The Apocalypse Project is a map pack, not a script. It works on any FiveM server, with BS19, ESX, QBCore, Qbox or nothing at all.

Note

The Apocalypse Project is a separate, manual download. The BS19 txAdmin recipe doesn’t include it, and txAdmin can’t run a second recipe on the same server, so there’s no recipe for the map: download the zip and install it by hand.

What you need

• A FiveM server with OneSync on. apocalypse-world-core (the movable wrecks) refuses to start without it, the rest of the map doesn’t care.
• About 1.1 GB of disk for the files. Players download what’s streamed the first time they join, after that it’s cached.
• An up-to-date server artifact. The IPL loader turns some fixes on only when the game build is new enough, so older builds just get fewer of them.

1. Download

Get the zip from bs19.org/map (latest GitHub release, or the newest files from the main branch while there’s no release) or straight from GitHub.

Inside the zip is one folder, [the_apocalypse_project]. The square brackets matter: FiveM treats a folder in brackets as a group and starts everything inside with one line.

2. Copy

resources/
├── [map]/
│   └── [the_apocalypse_project]/
│       ├── apocalypse-core/
│       ├── apocalypse-ipl/
│       ├── apocalypse-los-santos/
│       └── ... (17 resources)
└── ...your other resources

3. server.cfg

# framework and your own scripts first
ensure oxmysql
# ensure [your framework]

# the map
ensure [the_apocalypse_project]

Load order inside the folder sorts itself out: apocalypse-core and apocalypse-ipl are declared as dependencies, so FiveM starts them before the parts that need them. What matters is the order between the map and your other map resources:

• Your own MLOs and ymaps that should win over the map go after ensure [the_apocalypse_project].
• Another IPL loader (like bob74_ipl) goes before it, and you switch ours off. See Custom IPLs.

4. Streaming and pools

A map this size puts pressure on the client pools. If players get crashes or Pool full errors near big areas, raise the pools in server.cfg:

increase_pool_size "Building" 500
increase_pool_size "StaticBounds" 2000
increase_pool_size "EntityDescPool" 5000
increase_pool_size "TxdStore" 8000
increase_pool_size "FragmentStore" 4000
increase_pool_size "fragInstGta" 800
increase_pool_size "Object" 800

Keep them modest. Maxing everything costs memory on every client. Also keep ambient population off if you can (set onesync_population false), it fills the same pools.

5. Start and check

Restart the server (or refresh then ensure [the_apocalypse_project] in the console) and reconnect. In the client console (F8):

• /tapiplstatus prints the interiors the IPL loader found and whether they’re ready.
• /worldprofile low, balanced or high sets how much world dressing and how many wrecks you stream. Balanced is the default. /worldstatus shows the active profile.

After an update, tell players to clear their FiveM cache if something looks half old and half new.

Turning parts off

Every subfolder is its own resource. To skip one, stop starting the whole group and list what you want:

ensure apocalypse-core
ensure apocalypse-ipl
ensure apocalypse-los-santos
ensure apocalypse-blaine
# ensure apocalypse-world-core   # no movable wrecks

Keep apocalypse-buildings and apocalypse-los-santos on the same version, they share far-distance models.