How to Write Godot 4.3 GDScript from a Gameplay Brief

Godot scripts fail when they Find in _process and invent a jump action. Cache paths in _ready. Lock 4.3 vs 4.2.

The matching generator is the Godot 4.3 GDScript Node from a Gameplay Brief (Input Map, No get_node in _process; 4.3 vs 4.2 LTS Fork) (Godot 4 3 Gdscript Node From Gameplay Brief Input Map No Get Node In Process) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Cache child paths in _ready not in _process

Write a Godot 4.3 GDScript node from a gameplay brief. Use the Input Map. Do not call get_node in _process. Fork Unity-style Find and 4.2 yield. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

Gameplay brief (what the node does, scene tree names I allow): [Brief]
Godot version I lock (4.3 / 4.2 LTS / UNKNOWN): [Version]
Input Map actions I allow: [Actions]
Node type I allow (CharacterBody2D or other named type): [Type]
Child node paths I may cache in _ready: [Paths]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language for comments: [Lang]
Fork notes I require (4.3 vs 4.2): [Fork]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

Use only Input Map actions from Inputs

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

1. Honesty ledger: Brief, Version, Actions, Type, Paths, Fork, Lang. Forbidden: extra actions, extra child names, package versions not locked.
2. Version fork: if Version is 4.3, use await and typed arrays as 4.3. If 4.2 LTS, do not use 4.3-only APIs; mark yield as 4.2-only if Brief needs a coroutine. If UNKNOWN, write VERSION UNKNOWN and do not pick 4.3 by default in code comments.
3. Script: one file. class_name only if Brief names it. extends Type. @onready or _ready cache for Paths only. No get_node in _process or _physics_process.
4. Input: Input.is_action_pressed / just_pressed only for Actions. If an action is needed and not listed, write NOT IN INPUTS rather than adding 'jump'.
5. Refuse: Unity Input.GetAxis, GameObject.Find, FindObjectOfType, GetComponent in Update, C# MonoBehaviour.
6. Comments: Lang. Each cached path quoted from Paths.
7. Never: invent a singleton Autoload name, an addon, or a Godot 4.4 API if Version is 4.3 or 4.2.
8. Compliance pass: cut Banned and Never. Print that Version is quoted or UNKNOWN. Format as Format.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

Honor the 4.3 await vs 4.2 yield fork

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

• Godot GDScript node from Brief. Not a Unity MonoBehaviour and not a full project.
• No get_node in _process or _physics_process.
• Only Actions and Paths named in Inputs.
• Honor the 4.3 vs 4.2 LTS fork.
• No emojis.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

Refuse Unity MonoBehaviour APIs

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (godot 4.3 gdscript node, godot input map no get_node, godot 4.3 vs 4.2 lts fork) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.