AI Agent Playbook

​

Why This Exists

• conforms to the Summer SDK runtime contract,
• passes static analysis + submission checks,
• stays server-authoritative,
• does not assume 3D template-only architecture.

​

Platform-First Rule

• Build Summer game logic in Summer Engine.
• Integrate SummerGame lifecycle + player synced state.
• Use templates only when they fit the genre.

​

Required Output (Minimum Valid Pack)

• manifest.json
• main.gd (extends SummerGame)
• main.tscn (entry_scene)
• player.tscn (player root script)

​

Player Model Decision (Required)

1. 3D template path: player root script is SummerCharacter3D
2. Custom path: player root script extends SummerPlayer and defines custom synced game model

​

Required manifest.json Keys

• id (string)
• name (string)
• version (string)
• summer_sdk (string, for now "1.0")
• entry_scene (string, for example "main.tscn")
• min_players (number)
• max_players (number)

• player_scene (string, for example "player.tscn")

​

Scene + Script Contract

• extend SummerGame
• implement:
  • _game_init()
  • _game_start()
  • _game_end()
  • _player_joined(player)
  • _player_left(player)
• run authority logic server-side (if not Summer.is_server(): return in _process when needed)

• a SpawnPoints node with at least 2 child spawn nodes for multiplayer testing
• a Players node (recommended)

• use either:
  • res://sdk/summer_character_3d.gd, or
  • your own script that extends SummerPlayer
• include collision + visible mesh so test runs are obvious

​

Allowed vs Blocked APIs

​

Allowed (use these)

• Summer SDK systems (Summer, SummerGame, SummerPlayer, score/teams/data/economy APIs)
• normal gameplay node logic (Node, Node3D, movement, physics, animation, signals)

​

Blocked (never generate these in game scripts)

• OS.execute
• OS.shell_open
• OS.create_process
• FileAccess
• DirAccess
• HTTPRequest
• HTTPClient
• JavaScriptBridge
• ClassDB.instantiate
• Thread.new

• Banned APIs Reference

​

Definition Of Done (AI Output)

1. manifest.json has all required fields and valid types.
2. entry_scene exists and loads.
3. player_scene exists (if present) and loads.
4. Main script extends SummerGame.
5. Player path chosen explicitly (3D template or custom SummerPlayer subclass).
6. No blocked APIs appear in any .gd file.
7. Server-authoritative gameplay logic is on server paths.
8. Game can be exported to .pck and submitted through the release API (release reaches pending_review).

​

Safe Starter Prompt (for AI systems)

https://docs.summerengine.com/agent-setup/prompt.md

Create a minimal multiplayer Summer game with these files only:
manifest.json, main.gd, main.tscn, player.tscn.

Rules:
- main.gd must extend SummerGame and implement all lifecycle hooks.
- Include at least 4 spawn points in main.tscn.
- Keep authoritative gameplay state on server paths only.
- Multiplayer-native defaults: min_players 1, max_players 8.
- Include player_scene in manifest.json and make sure it matches player.tscn.
- Choose one player model:
  - 3D template: use SummerCharacter3D in player.tscn
  - custom model: extend SummerPlayer and sync game-specific state with set_synced/get_synced
- DO NOT use blocked APIs: OS.execute, OS.shell_open, OS.create_process, FileAccess, DirAccess, HTTPRequest, HTTPClient, JavaScriptBridge, ClassDB.instantiate, Thread.new.
- Target summer_sdk "1.0".