Conversation
CHANGELOG gains v4.09: the six shipped builds of 2026-09-05, each with its mechanism and its ladder. Navigation seats past a ledge lip, the co-op fetch rest, door contact as an overlap, co-op friendly fire, the unstick, and the AI tick livelock. It also records the corrections, because three of the day's results were reported wrongly first and the record should carry that: #248's headline ladder was invalidated by a stationary puppet acting as a second co-op client, the dm2 door result did not reproduce past one pair, and the "latent perception bug" in co-op does not exist because Argus_Perceive returns before its player scan whenever coop is on. README gains the two instruments and their limits. tools/ argus_pointfile.py draws nav data into the running game through the engine's own pointfile channel, and tools/argus_edicts.py reads an edicts dump for live bot state. Both note what they cannot do: pointfile colour cycles every 16 points and needs a listen game, and the edict dump is lossy under load. The MCP operator guide documents the dump on the tune whitelist (edicts, edict <n>, edictcount, all read only) and the reader that goes with it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b1cb54cd7c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| particles can. | ||
|
|
||
| ```bash | ||
| python tools/argus_pointfile.py e1m2 --what swim # then type: pointfile |
There was a problem hiding this comment.
For installations following the documented quick start, argus is copied into an arbitrary Quake installation, but this command uses the script's default output of <repo>/engine/argus/maps. The running engine therefore cannot find the generated .pts file unless the repository's engine directory happens to be its basedir. Pass and document --out <actual-game-dir>/maps, or derive the destination from the configured installation.
Useful? React with 👍 / 👎.
| and `--make-cfg` arms a delayed dump for `+exec` when there is no | ||
| injection channel. |
There was a problem hiding this comment.
When the lab uses a configured ARGUS_BASEDIR outside <repo>/engine—including the repository's Linux setup, which uses tools/quake—--make-cfg still hard-codes <repo>/engine/argus/edump.cfg. Consequently +exec edump.cfg cannot load the generated file, so this documented fallback produces no dump. The command needs an output/configured-basedir option, or the documentation must instruct operators to copy the file into the active game directory.
Useful? React with 👍 / 👎.
| injection channel. | ||
|
|
||
| ```bash | ||
| python tools/argus_edicts.py --make-cfg 45 --repeat 4 # dumps at 45, 90, 135, 180s |
There was a problem hiding this comment.
These advertised timestamps only hold on the approximately 10 Hz dedicated lab server: --make-cfg implements each second as ten wait commands, and each wait delays one frame. In a listen session running near the documented 72 Hz, the four dumps occur roughly at 6, 12, 19, and 25 seconds instead of 45–180 seconds, potentially missing the freeze the operator intended to capture. Either calculate against the actual frame rate or state that this schedule is dedicated-lab-only.
Useful? React with 👍 / 👎.
1 participant
CHANGELOG
A
v4.09entry for the six builds shipped on 2026-09-05, each with its mechanism and its ladder: navigation seats past a ledge lip (#250), the co-op fetch rest (#251), door contact as an overlap (#253), co-op friendly fire (#260), the unstick (#262), and the AI tick livelock (#263).It also records the day's corrections, because three results were reported wrongly first and the record should carry that:
Argus_Perceivereturns before its player scan whenevercoop > 0.README
The two instruments, with their limits stated rather than implied.
tools/argus_pointfile.pydraws nav data into the running game through the engine's own pointfile channel;tools/argus_edicts.pyreads anedictsdump for live bot state. Colour cycles every 16 points and needs a listen game; the edict dump is lossy under load.MCP operator guide
The dump on the tune whitelist (
edicts,edict <n>,edictcount, all read only) and the reader that goes with it, including the lossy-header caveat and how the reader tells a genuinely free slot from a header that never arrived.The machine-local project brief is updated in the same shape and is not part of this PR.
🤖 Generated with Claude Code