modules: raptors — the options as a module, and a seat on the game axis - #8687
Draft
keithharvey wants to merge 1 commit into
Draft
modules: raptors — the options as a module, and a seat on the game axis#8687keithharvey wants to merge 1 commit into
keithharvey wants to merge 1 commit into
Conversation
This was referenced Aug 7, 2026
Contributor
Integration Test Results21 tests 8 ✅ 16s ⏱️ For more details on these failures, see this check. Results for commit 9c777ab. ♻️ This comment has been updated with latest results. |
The raptor_* options move from the root modoptions.lua into modules/raptors, byte-identical — they are wire values, and the move does not get to rename them. The section hands itself to the game axis (mode_category = "game", mode_key = "raptors"), and the Raptors preset takes the seat beside standard, ffa and scavengers: the shared PvE grammar bound to the raptor_* keys, the queen standing where the boss does, RaptorsAI fielded by the lobby the way ScavengersAI already is. This is deliberately only the lobby face of the flavor. The spawner stays in luarules and reads its options exactly as it always has; activation stays AI-presence, so every existing lobby, coop room and startscript keeps working with the selector unset. The day raptors migrates onto the wave director, the roster and mechanics land beside these files — the same path scavengers took — and the Swarm noun the preset already dials becomes the pack it has been naming all along. The Bot chain verb moves to the shared PvE grammar on the way: every flavor needs its AI on the field, and no modoption can say so. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #8577 (scavengers); #8494 (CM8 Ashfall) continues above this.
The
raptor_*options move from the rootmodoptions.luaintomodules/raptors, byte-identical — they are wire values, and the move does not get to rename them. The section hands itself to the game axis (mode_category = "game",mode_key = "raptors"), and the Raptors preset takes its seat ongame_modebeside standard, ffa and scavengers: the shared PvE grammar bound to theraptor_*keys, the queen standing where the boss does, RaptorsAI fielded by the lobby the way ScavengersAI already is.This is deliberately only the lobby face of the flavor. The spawner stays in
luarulesand reads its options exactly as it always has; activation stays AI-presence, so every existing lobby, coop room and startscript keeps working with the selector unset. The day raptors migrates onto the wave director, the roster and mechanics land beside these files — the same path scavengers took — and theSwarmnoun the preset already dials (raptors.swarm) becomes the pack it has been naming all along.The
Botchain verb moves to the shared PvE grammar on the way: every flavor needs its AI on the field, and no modoption can say so.🤖 Generated with Claude Code