← ExekiteCONTENT HISTORY

Update to Exekite

Snapshot Nov 17, 2026 · 12:11 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Exekite and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "For Exekite-hosted Godot games only. Title gates, menus, and pause/resume handlers. Use when writing or debugging the specific handler that starts, pauses, or resumes play — keycode and click-only gates strand the playability probe; covers the probe-reachable ui_accept form and clean scene handoff.",
  "included_files": [],
  "name": "startability-and-input-gates",
  "skill_md_contents": "---\nname: startability-and-input-gates\ndescription: \"For Exekite-hosted Godot games only. Title gates, menus, and pause/resume handlers. Use when writing or debugging the specific handler that starts, pauses, or resumes play — keycode and click-only gates strand the playability probe; covers the probe-reachable ui_accept form and clean scene handoff.\"\n---\n\n# Getting past the title screen\n\nExposed by a real birth (Race-C): the title gate read `event.keycode`, so\nsynthetic input could never start the game and **every playability probe was\nblind** — they all reported on a title screen they could not leave. Detection\ntoday: none — this agent has no raw-input lint. The playtest tier presses\n`ui_accept` and, when a gate does not answer, its findings (no player, no\nmovement) are advisory warnings under `EXEKITE_PLAYTEST_STRICT=warn`, so a\nstranded probe reports on a menu rather than failing the turn.\n\nThis is also the single highest-leverage rule in the platform contract: the\nprobes press `ui_accept`. A gate that does not answer to it makes every oracle\ndownstream vacuous.\n\n## The rule\n\n```gdscript\n# WRONG — unreachable by the probe, and wrong on non-US layouts\nfunc _input(event: InputEvent) -> void:\n    if event is InputEventKey and event.pressed and event.keycode == KEY_SPACE:\n        _start()\n```\n\n```gdscript\n# RIGHT — the probe supplies both action state and parsed action events.\n# This polling form handles the action state; an event handler also works.\nfunc _process(_delta: float) -> void:\n    if Input.is_action_just_pressed(\"ui_accept\"):\n        _start()\n```\n\nAn event-handler gate (`if event.is_action_pressed(\"ui_accept\")` in `_input`)\nworks too. The probe delivers its press BOTH ways — an `InputEventAction`\nthrough `Input.parse_input_event` and the polled state through\n`Input.action_press` — so a handler and a poll are each sufficient on their own.\n\nThis paragraph used to say an event gate was \"invisible to the probe\". It was\ntrue when the probe called `action_press` alone: measured against real Godot\n4.6.1, that gives `is_action_pressed` = true and `_input` = 0 calls, so an\nevent-only title never advanced and the run reported a game that would not\nstart. The probe sends both forms now, and re-sends until a player exists.\n\n`ui_accept` is bound to **Space, Enter and the keypad Enter** by the\nharness-written `project.godot` — you cannot add actions, so use the ones that\nexist.\n\n## Why `keycode` specifically fails\n\n- `keycode` is the layout-mapped symbol. On AZERTY or Dvorak it is not the key\n  under the player's finger; `physical_keycode` is. Actions handle this for you.\n- The probe synthesizes ACTION presses, not scancodes. A keycode comparison\n  never matches, so an automated run sits on the title forever and every later\n  measurement — movement, camera, world — reports on a menu.\n\n## Never gate on a mouse click alone\n\nA click-only title is unreachable by the probe as well. If you want a clickable\nbutton, keep the action as a parallel path:\n\n```gdscript\nfunc _ready() -> void:\n    $StartButton.pressed.connect(_start)\n\nfunc _process(_delta: float) -> void:\n    if Input.is_action_just_pressed(\"ui_accept\"):\n        _start()                 # the probe's path, and the keyboard player's\n```\n\n## Make the transition actually happen\n\nTwo ways a correct gate still fails to start the game:\n\n```gdscript\nfunc _start() -> void:\n    if _started:                 # the poll and a button press can both fire\n        return\n    _started = true\n    get_tree().change_scene_to_file(\"res://scenes/Game.tscn\")\n```\n\n- **No re-entry guard.** The poll, a button, and any extra `_input` path can\n  each call `_start`, and two `change_scene_to_file` calls in one frame is\n  undefined behaviour.\n- **The same press leaking into gameplay.** `set_input_as_handled()` only\n  consumes the EVENT path; it does not clear polled action state. A handoff\n  within the same input frame can still see `is_action_just_pressed` as true.\n  If title/resume and gameplay share an action, wait for its release before\n  arming gameplay, or use a separate gameplay action. Reset this latch when\n  entering or resuming gameplay:\n\n```gdscript\nvar _accept_armed := false\n\nfunc _gameplay_accept() -> bool:\n    if not _accept_armed:\n        _accept_armed = not Input.is_action_pressed(\"ui_accept\")\n        return false\n    return Input.is_action_just_pressed(\"ui_accept\")\n```\n\nWhen an overlay takes over, move keyboard focus from covered or disabled HUD\ncontrols to an available overlay action. A focused HUD button can still consume\n`ui_accept` behind the overlay: Retry must not also toggle a previously focused\nmute button. Use one guarded transition owner for button and polling paths so\nthey cannot both start or restart the run. Arm shared gameplay actions only\nafter release, including after retry and resume.\n\n## Keep gameplay frozen while menus stay active\n\nProcess modes inherit down the tree. An `ALWAYS` main node also keeps every\n`INHERIT` player, enemy, hazard and game timer active while the tree is paused.\nKeep the menu/resume handler separate, or explicitly make each gameplay branch\n`PAUSABLE`. In this example, every gameplay node belongs under `Gameplay`;\ntitle/pause UI belongs outside it and calls `_start_or_resume()` / `_pause()`:\n\n```gdscript\n# Main.gd — Gameplay contains all live gameplay, including its timers.\nextends Node\n\nfunc _ready() -> void:\n    process_mode = Node.PROCESS_MODE_ALWAYS\n    $Gameplay.process_mode = Node.PROCESS_MODE_PAUSABLE\n    get_tree().paused = true # Pre-spawned gameplay waits behind the title.\n\nfunc _start_or_resume() -> void:\n    get_tree().paused = false\n\nfunc _pause() -> void:\n    get_tree().paused = true\n```\n\nHiding a title or disabling only the player's input does not freeze enemies,\nhazards or timers. If the title does not pause the tree, defer gameplay creation\nuntil Start or disable the entire gameplay branch until then. Signals and\ndirect method calls still run on paused nodes; guard gameplay-changing callbacks\nthat can be reached from active UI. See Godot's [process-mode semantics](https://docs.godotengine.org/en/4.6/tutorials/scripting/pausing_games.html).\n\n## Verify it without a human\n\n```gdscript\n# In the title scene, temporarily:\nfunc _ready() -> void:\n    if not InputMap.has_action(\"ui_accept\"):\n        push_error(\"ui_accept is not bound — the probe can never start this game\")\n```\n\nThen run the playtest gate and observe the title-to-play transition: the title\nmust accept input, gameplay must start, and the starting press must not also\ntrigger a gameplay action. Also hold movement on the title and while paused:\nplayer, enemies, hazards and game timers must stay fixed while menu/resume input\nstill works. Resume must restore gameplay. A bound action alone does not prove\nthe handoff or the freeze.\n"
}

SHA-256 of public snapshot: 0af287e328d16a8670bc578f8d2b2f4337a3423e09c1e08e3af58aff760f6f93