Maps won't load: 'Builtin 601: not implemented' (engine older than bundled QuakeC since late Sep)

surfnterd commented

2026-10-23 08:07:41 -03:00

(Migrated from github.com)

@surfnterd on GitHub wrote:

Every map fails to load on the recent weekly builds: "game starts" then it drops straight back to the main menu. The menu itself runs fine (Vulkan, 60fps).

Device: AYN Thor (Snapdragon 8 Gen 2, Adreno 740), arm64.

Log (build-20261019-30):

NZ:PDroid: unknown-file : Json_ParseFile
NZ:PDroid: unknown-file : Modifiers_LoadFile
NZ:PDroid: unknown-file : Modifiers_LoadGameVariables
NZ:PDroid: unknown-file : worldspawn
NZ:PDroid: unknown-file : CheckSpawn
NZ:PDroid: SV_Error: Builtin 601: not implemented.
NZ:PDroid: Mod is not compatible.

build-20260914-24 also fails the same way, but on a different builtin:

NZ:PDroid: SV_Error: Builtin 120: not implemented.
NZ:PDroid: Mod is not compatible.

What I think is happening: the weekly workflow bundles the latest NZ:P nightly QuakeC (progs.dat), but the bundled engine (libftedroid.so) has been byte-identical in every build since at least 31 Aug. Upstream QuakeC has since started calling builtins the fork doesn't implement. From what I checked:

The Json_* / Modifiers_* functions are in progs.dat from build-20260928-27 onwards. They're absent in build-20260914-24 and build-20260831-22.
The libftedroid.so md5 is the same across 0831, 0914, 0928, 1005, 1012 and 1019.

The CI check only catches the QuakeC patch failing to apply. A runtime builtin mismatch still builds and ships, so every weekly release since late September is unplayable.

Possible fixes:

Rebase the fteqw fork onto nzp-team/fteqw so it picks up the builtins upstream QuakeC now expects (601 / the JSON ones, and whatever 120 maps to).
Or pin the bundled game data to the NZ:P nightly that matches the engine, and only bump the two together.
Add a CI smoke test: run the dedicated server headless on one map for a few seconds and fail the release on SV_Error.

Thanks for doing the port, the touch and controller work looks great.

*@surfnterd on GitHub wrote:* Every map fails to load on the recent weekly builds: "game starts" then it drops straight back to the main menu. The menu itself runs fine (Vulkan, 60fps). **Device:** AYN Thor (Snapdragon 8 Gen 2, Adreno 740), arm64. **Log (build-20261019-30):** ``` NZ:PDroid: unknown-file : Json_ParseFile NZ:PDroid: unknown-file : Modifiers_LoadFile NZ:PDroid: unknown-file : Modifiers_LoadGameVariables NZ:PDroid: unknown-file : worldspawn NZ:PDroid: unknown-file : CheckSpawn NZ:PDroid: SV_Error: Builtin 601: not implemented. NZ:PDroid: Mod is not compatible. ``` **build-20260914-24** also fails the same way, but on a different builtin: ``` NZ:PDroid: SV_Error: Builtin 120: not implemented. NZ:PDroid: Mod is not compatible. ``` **What I think is happening:** the weekly workflow bundles the latest NZ:P nightly QuakeC (`progs.dat`), but the bundled engine (`libftedroid.so`) has been byte-identical in every build since at least 31 Aug. Upstream QuakeC has since started calling builtins the fork doesn't implement. From what I checked: - The Json_* / Modifiers_* functions are in `progs.dat` from build-20260928-27 onwards. They're absent in build-20260914-24 and build-20260831-22. - The `libftedroid.so` md5 is the same across 0831, 0914, 0928, 1005, 1012 and 1019. The CI check only catches the QuakeC patch failing to *apply*. A runtime builtin mismatch still builds and ships, so every weekly release since late September is unplayable. **Possible fixes:** 1. Rebase the `fteqw` fork onto nzp-team/fteqw so it picks up the builtins upstream QuakeC now expects (601 / the JSON ones, and whatever 120 maps to). 2. Or pin the bundled game data to the NZ:P nightly that matches the engine, and only bump the two together. 3. Add a CI smoke test: run the dedicated server headless on one map for a few seconds and fail the release on `SV_Error`. Thanks for doing the port, the touch and controller work looks great.

zqpvr commented

2026-10-23 08:11:01 -03:00

(Migrated from github.com)

I will look into this in a bit; thanks for letting me know. Also, I do seem to be able to produce it.

zqpvr commented

2026-10-24 17:32:24 -03:00

(Migrated from github.com)

working on it now

zqpvr commented

2026-10-27 14:53:51 -03:00

(Migrated from github.com)

It's gonna take a little bit longer than expected, keep to the old build for now