The autopilot engine is game-agnostic — scenarios, overlay rules, and the DSL aren’t tied to any specific game. Adding Kingshot is essentially authoring its scenario set under games/kingshot/; no engine changes required.
Status
Section titled “Status”In-game automation: not started. No daily-loop scenarios, no labeled regions, no analyzer rules for Kingshot’s in-game UI yet. (Gift codes above are a separate, complete feature — they don’t depend on in-game automation.)
We’ll start the in-game scenario implementation as soon as volunteers show up. This isn’t a planned-but-delayed project — it’s a “if there’s interest, we’ll do it” project. If even one person commits to authoring the daily-loop scenarios, we’ll pair up and ship a working version.
Want to help?
Section titled “Want to help?”Drop into the #install channel on Discord and ping us. You don’t need prior contribution experience — if you can describe Kingshot’s daily loop in plain English, you can describe it in the DSL.
We have public docs for the full authoring flow already:
- Authoring flow — capture → label → write DSL → test
- Labeling regions — using the editor
- DSL primer —
match,click,while_match,cond,push_scenariowith a worked example
We’ll pair on the labeling pass and review your first scenarios.
The Whiteout Survival coverage is a good template for what “fully covered” looks like — that’s roughly what we’d aim for with Kingshot, ideally driven by someone who actually plays the game.