- Home
- Skills
- Game Development
- Godot Party Game Workflow
Godot Party Game Workflow
A focused AI-agent workflow for Godot 4 party games: round contracts, bot-stall diagnosis, split-screen controls, and checks that distinguish working logic from playable results.
$9
Works with the AI Agents you already use
Godot Party Game Workflow
Example session with this skill installed
Review this simplified Godot 4 pickup eligibility function. Team 0 can stand at x=-0.25 and team 1 at x=0.25. Pickup radius is 0.6. The ball starts at x=0. Both teams report that the ball is in reach, but neither can collect it. Explain the cause and suggest a minimal change. Do not run Godot or change project files.
func can_pick_up(team: int, player_x: float, ball_x: float) -> bool:
var in_team_region: bool = (team == 0 and ball_x <= -0.1) or (team == 1 and ball_x >= 0.1)
return in_team_region and absf(player_x - ball_x) <= 0.6
- Read your context and instructions
- Compiled the godot party game
Finding
The neutral strip excludes the spawn point before reach is considered. At ball_x = 0, the team-0 condition 0 <= -0.1 is false and the team-1 condition 0 >= 0.1 is false. Both players are only 0.25 units from the ball, inside the 0.6 pickup radius, but the conjunction rejects both requests. Increasing reach alone cannot fix this case.
Minimal proposed change
If both teams should be allowed to collect a ball in the neutral strip, make that permission explicit:
func can_pick_up(team: int, player_x: float, ball_x: float) -> bool:
if team != 0 and team != 1:
return false
var in_neutral_strip: bool = absf(ball_x) <= 0.1
var in_team_region: bool = (team == 0 and ball_x <= -0.1) or (team == 1 and ball_x >= 0.1)
return (in_neutral_strip or in_team_region) and absf(player_x - ball_x) <= 0.6
This changes neutral-strip eligibility only and preserves reach and team-region checks. If the intended neutral-possession rule differs, encode that rule instead.
Ownership and checks
The round should resolve simultaneous valid attempts and assign possession once. Players must not each claim ownership independently.
| Case | Expected |
|---|---|
| Team 0, player -0.25, ball 0 | Eligible |
| Team 1, player 0.25, ball 0 | Eligible |
| Team 0, player -1, ball 0 | Rejected: out of reach |
| Team 0, player 0.25, ball 0.3 | Rejected: opponent region |
| Team 1, player 0.25, ball 0.3 | Eligible |
| Invalid team 2, player 0, ball 0 | Rejected |
Validation limits
This is a static review of a supplied example using the workflow. The original failure and eight proposed-predicate cases, including boundaries, were checked separately with arithmetic assertions. Godot was not run and project files were not edited. Actual bot movement and simultaneous pickup remain untested. A full implementation should exercise neutral pickup, boundaries and a completed bot match in the real project.
Connects securely to your tools. The creator never sees your data.
About this skill
Help your coding agent keep round rules, player input, progression and presentation from drifting into conflicting implementations.
Derived from the development of SOBE, an unfinished Godot party-game prototype that underwent Godot runtime testing and human playtesting, this skill covers bots unable to reach neutral objects, state leaking across rounds, aiming through the wrong viewport, optional models breaking startup, and fixes tested in a different checkout from the one you launch. Those tests belong to the source prototype; they are not a cross-project certification of this newly packaged skill.
Includes a focused SKILL.md plus five references: round contracts, player presentation, bot diagnostics, layered verification, and example requests.
For developers building Godot 4 GDScript local multiplayer or mini-game projects. Requires an agent with project access; runtime checks require Godot and execution permissions, while visual checks require a rendered session or user evidence.
This is a text-based engineering workflow, not the SOBE game, playable template, model pack, executable plugin or networking framework. Cross-project compatibility of the newly packaged skill has not yet been established.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Game Development.
SOBE, the source prototype, was tested in Godot and human play sessions but was not completed. This newly packaged skill has passed structural checks and a static example review; it has not been validated end-to-end across other projects. It provides guidance, not an executable game, networking framework or art pack.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 13 days ago
- Software
- Godot 4
The Godot 4 editor is used for runtime verification.
Permissions
Project file access only. Read-only requests remain read-only; writes and engine execution are used only for authorized implementation/testing tasks. Optional rule or API research may use a browser. No credentials, account access or environment-variable harvesting required.