How to update
From 1.05 to v1.1.0
Section titled “From 1.05 to v1.1.0”v1.1.0 is a big update: new resources, a new voice system and four database migrations. On a server you never edited, a clean reinstall with the recipe is the easiest path (new world, so export anything you want to keep first). On a server you changed, update by hand:
Download v1.1.0 · Changelog · How to update.txt
- Stop the server and back up its folder and the database.
- Download v1.1.0 into a separate folder. The release is split in 5 zip parts (
bs19-part1.ziptobs19-part5.zip) because txAdmin gives each download 150 seconds. Extract all five into the same folder. Do not run the fresh-install recipe against an existing server and do not extract the download over your files. - Copy the new resources into your server:
resources/[beyond]:bs_bodycam,bs_darkzone,bs_fighting,bs_fpdebug,bs_missions,bs_parkour,bs_pass,bs_survivor,bs_survivor_link,bs_voiceresources/[compat]:qbx_coreresources/[prototypes]:bs_attachment_factory_03,bs_attachment_prototypes,bs_attachment_set_02(weapon attachment models)
- Existing resources: for the ones you never edited, take the v1.1.0 copy. For the ones you edited, compare your copy with v1.1.0 and merge.
- server.cfg: compare yours with the v1.1.0 one and add the new
ensurelines in the same order. Two changes matter most:bs_voicereplaces pma-voice. Remove orstop pma-voice, then ensurebs_voice.bs_radiois now on. Ensure it right afterbs_voice.bs_esx_bridgeis no longer started by default. Keep it if you rely on it, see ESX and Qbox scripts.
- Database: keep it. Migrations 045 (Dark Zone), 046 (building v2), 047 (faction emblems) and 048 (backpack items) run on their own the first time
bs_corestarts. 048 renames the old backpack items and keeps their contents. Watch the console for the migration lines. - Restart the full server, join and check character select, inventory, voice and a zombie fight. If something goes wrong, stop the server and restore your backup.
Keep your credentials, F1 profiles and custom resources. New systems like the Dark Zone and Survivor Link are off until you switch them on in F1.
Older: v1.05 Hotfix
Section titled “Older: v1.05 Hotfix”This release fixes the existing public framework. It does not include the new systems planned for v1.1, and it adds no database migrations.
Download v1.05. The download includes How to update.txt and update-v1.05.json, with the exact changed paths and file hashes. You can also read the file list on GitHub or compare the code.
Keep your changes
Section titled “Keep your changes”Stop the server and back up its folder and database first. Extract v1.05 somewhere separate. Do not run the install recipe on your existing server or extract the new files straight over it.
For each file in the update list:
- You never changed it: copy the v1.05 version.
- You changed it: compare the original release you installed, your current file and the v1.05 file. Keep your edits and merge the fix. A three-way comparison shows what each side changed.
- You want to skip it: check its dependencies first. Keep the old related files together rather than mixing half of an update.
For example, if you changed bs_chat, review its Lua client and HTML page together. If you changed bs_zombies, review the client and server files as one update. Copying just one side can leave the old problem in place.
The hashes in the manifest help identify an untouched file. A mismatch does not mean your changes are wrong; it means the file needs review. There is no automatic update tool included in v1.05.
What changes
Section titled “What changes”| Resource | Fixes |
|---|---|
bs_admin | Staff teleports wait for world collision. |
bs_atlas | Map teleports use the same collision-safe helper. |
bs_chat | Recover lost focus, hidden chat and a stalled browser page. |
bs_core | Shared safe teleport and streaming-focus recovery. |
bs_faction_bases | Seat flag poles after nearby collision loads. |
bs_factions | Faction admin teleports use safe placement. |
bs_interactions | Avoid NPC outline crashes, require line of sight and clear completed progress bars. |
bs_inventory | Restore refused moves, retry character captures and explain overload sprint restrictions. |
bs_medical | Keep hold-X give-up progress through brief input drops. |
bs_multichar | Prevent selector fade/camera races and release streaming focus after spawn. |
bs_operations | Existing admin teleports use safe placement. |
bs_pause | Expose texture recovery in existing troubleshooting settings. |
bs_recycler | Place players safely after recycler travel. |
bs_traders | Skip unavailable clothing, keep checkout reachable and fix debug teleports. |
bs_tutorial | Do not repeat the picker/tutorial bucket for established characters. |
bs_ui | Avoid duplicate HUD/audio messages. |
bs_world | Keep service NPCs out of ambient cleanup and reduce repeated population work. |
bs_zombies | Validate hits against live positions, retry death reports, protect recycled NPC handles and correct takedown/get-up timing. |
Take bs_core together with the changed teleport callers and bs_pause. Update the inventory capture client and browser script together. The full per-file list is in How to update.txt.
Keep your own server.cfg, connection details, license key, database, F1 profiles and extra resources. The changed interaction and zombie config files need a comparison if you edited them. Do not replace your settings just to pick up a new default.
Start the server
Section titled “Start the server”Use a full server restart after applying the files. Watch the console, join, and check character selection, chat, inventory moves, clothing and zombie damage. Keep the backup until you are happy with the result.
If you need to undo the update, stop the server and restore the changed files. This hotfix does not change the database schema. A database restore is separate from restoring scripts.
For a new server, use Installation. For database background, see Updating & database.
bs19.org · Privacy · Terms · Cookie settings
Cookies and outside content
The site only needs two essential cookies to keep you logged in and protect forms. Videos and streams from YouTube and Twitch load from their servers, which can set their own cookies, so they stay off until you say yes. Nothing is pre-ticked and you can change your mind any time with "Cookie settings" at the bottom of every page. Details.
Questions about the server, the framework or the site? A real person reads this, usually within a day.