godot-game-loop-collection

Name: godot-game-loop-collection
Author: thedivergentai

136installs26forks

How to install godot-game-loop-collection?

thedivergentai/gd-agentic-skills/godot-game-loop-collection

$npx -y skills add thedivergentai/GD-Agentic-Skills --skill godot-game-loop-collection

Installs into the current project.

Summary

Use when implementing collection quests, scavenger hunts, or "find all X" objectives.

Files · 1

View on GitHub

SKILL.md

1	## Godot 4.7 Baseline
2
3	- Expert patterns in this skill target Godot 4.7+ (stable, 2026-06-18).
4	- Consult the [Godot 4.7 migration guide](https://docs.godotengine.org/en/4.7/tutorials/migrating/upgrading_to_godot_4.7.html) when upgrading projects from 4.6.
5	- NEVER assume 4.6 defaults (stretch mode, audio area_mask, RichTextLabel percent flags) without checking 4.7 migration notes.
6
7	# Collection Game Loops
8
9	## Overview
10	This skill provides a standardized framework for "Collection Loops" – gameplay objectives where the player must find and gather a specific set of items (e.g., hidden eggs, data logs, coins).
11
12	## NEVER Do
13
14	- NEVER use free() to destroy an active state node or level — This can cause crashes if the node is still processing. Always use `queue_free()` to safely dispose of it at the end of the frame.
15	- NEVER calculate physics-dependent game state in _process() — Movement and precise collisions must happen in `_physics_process()` to stay synced with the engine's fixed timestep.
16	- NEVER execute heavy state transitions (like loading massive levels) synchronously — Calling `load()` on a huge scene stalls the main thread. Use `ResourceLoader.load_threaded_request()`.
17	- NEVER use exact floating-point equality (==) for time-based states — Floating-point errors will eventually cause missed triggers. Use `is_equal_approx()` or relative comparisons.
18	- NEVER manipulate the active SceneTree from a background thread — The SceneTree is not thread-safe. Use `call_deferred()` to push results back to the main thread.
19	- NEVER rely on a monolithic "GameManager" with hardcoded absolute paths — This creates tight coupling. Use groups, signals, and exported references for a modular architecture.
20	- NEVER assume child nodes are ready before their parent — `_ready()` executes from bottom-to-top. If you need child references, use `@onready` or `await ready`.
21	- NEVER use string-based signals for critical state transitions — Avoid `connect("signal", _on_func)`. Use the Signal object syntax (`signal.connect(_on_func)`) for compile-time validation.
22	- NEVER poll for input state every frame for discrete menu events — Use the `_unhandled_input()` callback to cleanly intercept events without wasting CPU cycles in `_process()`.
23	- NEVER crash the engine intentionally via CRASH_NOW_MSG — Regular state handling should always recover gracefully. Crashing is for unrecoverable internal engine failures.
24	- NEVER hardcode spawn positions in code — Always use `Marker3D` or `CollisionShape3D` nodes in the scene so designers can adjust layout without touching code.
25	- NEVER neglect "juice" before an item disappears — Immediate `queue_free()` feels dry. Always spawn particles or play a sound before removal.
26	- NEVER use global variables for local collection progress — Keep counts encapsulated within the `CollectionManager` and emit signals to update the UI.
27	- NEVER leave orphaned nodes in the tree during state swaps — Always ensure the previous level/state is properly queued for deletion before instantiating the new one.
28	- NEVER scale collision shapes non-uniformly for collectibles — This breaks collision detection math. Adjust the internal shape resource properties instead.
29
30	---
31
32	## Available Scripts
33
34	> MANDATORY: Read the appropriate script before implementing the corresponding pattern.
35
36	### [collection_loop_patterns.gd](scripts/collection_loop_patterns.gd)
37	Collection of 10 expert patterns: Custom MainLoop extensions, deferred scene switching, threaded loading, and frame throttling.
38
39	### [collection_manager.gd](scripts/collection_manager.gd)
40	The central brain of the hunt. Tracks progress and manages completion signals.
41
42	### [collection_compass.gd](scripts/collection_compass.gd)
43	Spatial radar for pointing towards the nearest collectible using vector math.
44
45	---
46
47	## Expert Collection Patterns
48
49	### 1. Persistent Collection (Save/Load)
50	To ensure progress survives restarts, use `FileAccess` to store data in `user://`.
51
52	```gdscript
53	func save_progress(data: Dictionary):
54	var file = FileAccess.open("user://save.dat", FileAccess.WRITE)
55	file.store_var(data) # Binary serialization for performance
56
57	func load_progress() -> Dictionary:
58	if not FileAccess.file_exists("user://save.dat"): return {}
59	var file = FileAccess.open("user://save.dat", FileAccess.READ)
60	return file.get_var()
61	```
62
63	### 2. Collection Archive UI (Silhouettes)
64	Display uncollected items as silhouettes without extra textures by using `modulate`.
65
66	- Technique: Use an `ItemList` or `TextureRect` grid.
67	- Silhouette: Set `modulate = Color(0, 0, 0, 0.5)` for locked items.
68	- Reveal: Set `modulate = Color(1, 1, 1, 1)` once collected.
69
70	## Reference
71	- Master Skill: [godot-master](../godot-master/SKILL.md)

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

godot-game-loop-collection

136installs26forks

View on GitHub

How to install godot-game-loop-collection?

thedivergentai/gd-agentic-skills/godot-game-loop-collection

$npx -y skills add thedivergentai/GD-Agentic-Skills --skill godot-game-loop-collection

Installs into the current project.

Summary

Use when implementing collection quests, scavenger hunts, or "find all X" objectives.

Files · 1

View on GitHub

SKILL.md

1	## Godot 4.7 Baseline
2
3	- Expert patterns in this skill target Godot 4.7+ (stable, 2026-06-18).
4	- Consult the [Godot 4.7 migration guide](https://docs.godotengine.org/en/4.7/tutorials/migrating/upgrading_to_godot_4.7.html) when upgrading projects from 4.6.
5	- NEVER assume 4.6 defaults (stretch mode, audio area_mask, RichTextLabel percent flags) without checking 4.7 migration notes.
6
7	# Collection Game Loops
8
9	## Overview
10	This skill provides a standardized framework for "Collection Loops" – gameplay objectives where the player must find and gather a specific set of items (e.g., hidden eggs, data logs, coins).
11
12	## NEVER Do
13
14	- NEVER use free() to destroy an active state node or level — This can cause crashes if the node is still processing. Always use `queue_free()` to safely dispose of it at the end of the frame.
15	- NEVER calculate physics-dependent game state in _process() — Movement and precise collisions must happen in `_physics_process()` to stay synced with the engine's fixed timestep.
16	- NEVER execute heavy state transitions (like loading massive levels) synchronously — Calling `load()` on a huge scene stalls the main thread. Use `ResourceLoader.load_threaded_request()`.
17	- NEVER use exact floating-point equality (==) for time-based states — Floating-point errors will eventually cause missed triggers. Use `is_equal_approx()` or relative comparisons.
18	- NEVER manipulate the active SceneTree from a background thread — The SceneTree is not thread-safe. Use `call_deferred()` to push results back to the main thread.
19	- NEVER rely on a monolithic "GameManager" with hardcoded absolute paths — This creates tight coupling. Use groups, signals, and exported references for a modular architecture.
20	- NEVER assume child nodes are ready before their parent — `_ready()` executes from bottom-to-top. If you need child references, use `@onready` or `await ready`.
21	- NEVER use string-based signals for critical state transitions — Avoid `connect("signal", _on_func)`. Use the Signal object syntax (`signal.connect(_on_func)`) for compile-time validation.
22	- NEVER poll for input state every frame for discrete menu events — Use the `_unhandled_input()` callback to cleanly intercept events without wasting CPU cycles in `_process()`.
23	- NEVER crash the engine intentionally via CRASH_NOW_MSG — Regular state handling should always recover gracefully. Crashing is for unrecoverable internal engine failures.
24	- NEVER hardcode spawn positions in code — Always use `Marker3D` or `CollisionShape3D` nodes in the scene so designers can adjust layout without touching code.
25	- NEVER neglect "juice" before an item disappears — Immediate `queue_free()` feels dry. Always spawn particles or play a sound before removal.
26	- NEVER use global variables for local collection progress — Keep counts encapsulated within the `CollectionManager` and emit signals to update the UI.
27	- NEVER leave orphaned nodes in the tree during state swaps — Always ensure the previous level/state is properly queued for deletion before instantiating the new one.
28	- NEVER scale collision shapes non-uniformly for collectibles — This breaks collision detection math. Adjust the internal shape resource properties instead.
29
30	---
31
32	## Available Scripts
33
34	> MANDATORY: Read the appropriate script before implementing the corresponding pattern.
35
36	### [collection_loop_patterns.gd](scripts/collection_loop_patterns.gd)
37	Collection of 10 expert patterns: Custom MainLoop extensions, deferred scene switching, threaded loading, and frame throttling.
38
39	### [collection_manager.gd](scripts/collection_manager.gd)
40	The central brain of the hunt. Tracks progress and manages completion signals.
41
42	### [collection_compass.gd](scripts/collection_compass.gd)
43	Spatial radar for pointing towards the nearest collectible using vector math.
44
45	---
46
47	## Expert Collection Patterns
48
49	### 1. Persistent Collection (Save/Load)
50	To ensure progress survives restarts, use `FileAccess` to store data in `user://`.
51
52	```gdscript
53	func save_progress(data: Dictionary):
54	var file = FileAccess.open("user://save.dat", FileAccess.WRITE)
55	file.store_var(data) # Binary serialization for performance
56
57	func load_progress() -> Dictionary:
58	if not FileAccess.file_exists("user://save.dat"): return {}
59	var file = FileAccess.open("user://save.dat", FileAccess.READ)
60	return file.get_var()
61	```
62
63	### 2. Collection Archive UI (Silhouettes)
64	Display uncollected items as silhouettes without extra textures by using `modulate`.
65
66	- Technique: Use an `ItemList` or `TextureRect` grid.
67	- Silhouette: Set `modulate = Color(0, 0, 0, 0.5)` for locked items.
68	- Reveal: Set `modulate = Color(1, 1, 1, 1)` once collected.
69
70	## Reference
71	- Master Skill: [godot-master](../godot-master/SKILL.md)

People who liked this also viewed

6 picks

Type