godot-genre-roguelike

Name: godot-genre-roguelike
Author: thedivergentai

233installs26forks

How to install godot-genre-roguelike?

thedivergentai/gd-agentic-skills/godot-genre-roguelike

$npx -y skills add thedivergentai/GD-Agentic-Skills --skill godot-genre-roguelike

Installs into the current project.

Summary

Expert blueprint for roguelikes including procedural generation (Walker method, BSP rooms), permadeath with meta-progression (unlock persistence), run state vs meta state separation, seeded RNG (shareable runs), loot/relic systems (hook-based modifiers), and difficulty scaling (f

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	# Genre: Roguelike
8
9	Expert blueprint for roguelikes balancing challenge, progression, and replayability.
10
11	## NEVER Do (Expert Anti-Patterns)
12
13	### Generation & RNG
14	- NEVER make runs dependent on pure RNG; strictly provide mitigation (rerolls, shops, pity timers) to ensure every run is winnable.
15	- NEVER use unseeded RNG for world generation; strictly initialize isolated `RandomNumberGenerator` with a predictable seed for daily runs/debugging.
16	- NEVER rely on `@GlobalScope.randi()` for critical logic; strictly use local RNG instances to prevent global state pollution.
17	- NEVER use `Array.pick_random()` for critical content drops; strictly use a Shuffle Bag to prevent statistically unfair streaks.
18	- NEVER generate massive dungeons on the main thread; strictly use `WorkerThreadPool.add_task()` or `add_group_task()` to distribute generation across cores and prevent frame freezes.
19	- NEVER interact with the SceneTree from a background thread; strictly generate dungeon data in a thread-safe Array/PackedByteArray before parsing on the main thread.
20
21	### Data & State
22	- NEVER allow Save Scumming; strictly delete mid-run save files immediately upon loading to enforce permadeath.
23	- NEVER allow the player to see the "Edge of the World"; strictly use Fog of War or limited vision cones to maintain the mystery of the unknown.
24	- NEVER evaluate complex "Director" heuristics every frame; strictly use Frame-Slicing (`Engine.get_process_frames()`) to run heavy pacing logic only once every 60-120 frames for CPU efficiency.
25	- NEVER move rooms individually by pixel values during procedural generation; strictly use `Marker2D` Connection Points in pre-authored scenes to calculate exact offsets for seamless room stitching.
26	- NEVER allow Run State to leak into Meta State; strictly use separate singletons or Resources for `RunManager` and `MetaManager`.
27	- NEVER scale meta-progression to be overpowered (+100% damage); strictly keep upgrades subtle (+5-15%) to maintain skill-based play.
28	- NEVER forget to call `duplicate(true)` on base stat Resources; failing to deep-duplicate causes all entities to share a single health instance.
29	- NEVER save run states to `.tscn` files; strictly serialize to JSON or binary in `user://` to prevent bloat.
30	- NEVER rely on the `SceneTree` as the source of truth for grid logic; strictly maintain grid data in a separate Dictionary or Array.
31
32	### Grid & Performance
33	- NEVER forget to handle Navigation re-baking; strictly rebake `NavigationRegion2D` AFTER procedural tiles are placed.
34	- NEVER use AStar2D for tile grids; strictly use `AStarGrid2D` with `jumping_enabled = true` (Jump Point Search) for O(1) queries and high-performance pathing across open areas.
35	- NEVER forget to call `update()` on `AStarGrid2D` after modifying states; strictly ensures pathfinding queries aren't stale.
36	- NEVER use floats (`Vector2`) for discrete grid coordinates; strictly use Vector2i to prevent precision drift.
37	- NEVER use Manhattan heuristics for 8-way movement; strictly use `HEURISTIC_CHEBYSHEV` or `HEURISTIC_OCTILE`.
38	- NEVER iterate over every cell coordinate (0 to W,H) in GDScript; strictly use `get_used_cells()` for optimized tile access.
39	- NEVER clear procedural levels using `free()`; strictly use `queue_free()` to avoid mid-frame segmentation faults.
40	- NEVER broadcast mass state changes to a grid immediately; strictly use `call_deferred()` or `call_group_flags` to avoid frame spikes during turn transitions.
41	- NEVER use heavy TileMapLayer nodes for high-resolution Fog of War; strictly use a GPU Shader Mask via `ColorRect` and an `ImageTexture` updated via `RenderingServer.texture_2d_update()`.
42
43	## 🛠 Expert Components (scripts/)
44
45	### Original Expert Patterns
46	- [meta_progression_manager.gd](scripts/meta_progression_manager.gd) - Foundational meta-progression logic with secure data persistence and currency unlocks.
47	- [roguelike_patterns.gd](scripts/roguelike_patterns.gd) - 10 Essential Roguelike Expert Snippets (AStar, BSP, WorkerThreadPool, ShuffleBa

People who liked this also viewed

6 picks

Type

godot-genre-roguelike

233installs26forks

View on GitHub

How to install godot-genre-roguelike?

thedivergentai/gd-agentic-skills/godot-genre-roguelike

$npx -y skills add thedivergentai/GD-Agentic-Skills --skill godot-genre-roguelike

Installs into the current project.

Summary

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	# Genre: Roguelike
8
9	Expert blueprint for roguelikes balancing challenge, progression, and replayability.
10
11	## NEVER Do (Expert Anti-Patterns)
12
13	### Generation & RNG
14	- NEVER make runs dependent on pure RNG; strictly provide mitigation (rerolls, shops, pity timers) to ensure every run is winnable.
15	- NEVER use unseeded RNG for world generation; strictly initialize isolated `RandomNumberGenerator` with a predictable seed for daily runs/debugging.
16	- NEVER rely on `@GlobalScope.randi()` for critical logic; strictly use local RNG instances to prevent global state pollution.
17	- NEVER use `Array.pick_random()` for critical content drops; strictly use a Shuffle Bag to prevent statistically unfair streaks.
18	- NEVER generate massive dungeons on the main thread; strictly use `WorkerThreadPool.add_task()` or `add_group_task()` to distribute generation across cores and prevent frame freezes.
19	- NEVER interact with the SceneTree from a background thread; strictly generate dungeon data in a thread-safe Array/PackedByteArray before parsing on the main thread.
20
21	### Data & State
22	- NEVER allow Save Scumming; strictly delete mid-run save files immediately upon loading to enforce permadeath.
23	- NEVER allow the player to see the "Edge of the World"; strictly use Fog of War or limited vision cones to maintain the mystery of the unknown.
24	- NEVER evaluate complex "Director" heuristics every frame; strictly use Frame-Slicing (`Engine.get_process_frames()`) to run heavy pacing logic only once every 60-120 frames for CPU efficiency.
25	- NEVER move rooms individually by pixel values during procedural generation; strictly use `Marker2D` Connection Points in pre-authored scenes to calculate exact offsets for seamless room stitching.
26	- NEVER allow Run State to leak into Meta State; strictly use separate singletons or Resources for `RunManager` and `MetaManager`.
27	- NEVER scale meta-progression to be overpowered (+100% damage); strictly keep upgrades subtle (+5-15%) to maintain skill-based play.
28	- NEVER forget to call `duplicate(true)` on base stat Resources; failing to deep-duplicate causes all entities to share a single health instance.
29	- NEVER save run states to `.tscn` files; strictly serialize to JSON or binary in `user://` to prevent bloat.
30	- NEVER rely on the `SceneTree` as the source of truth for grid logic; strictly maintain grid data in a separate Dictionary or Array.
31
32	### Grid & Performance
33	- NEVER forget to handle Navigation re-baking; strictly rebake `NavigationRegion2D` AFTER procedural tiles are placed.
34	- NEVER use AStar2D for tile grids; strictly use `AStarGrid2D` with `jumping_enabled = true` (Jump Point Search) for O(1) queries and high-performance pathing across open areas.
35	- NEVER forget to call `update()` on `AStarGrid2D` after modifying states; strictly ensures pathfinding queries aren't stale.
36	- NEVER use floats (`Vector2`) for discrete grid coordinates; strictly use Vector2i to prevent precision drift.
37	- NEVER use Manhattan heuristics for 8-way movement; strictly use `HEURISTIC_CHEBYSHEV` or `HEURISTIC_OCTILE`.
38	- NEVER iterate over every cell coordinate (0 to W,H) in GDScript; strictly use `get_used_cells()` for optimized tile access.
39	- NEVER clear procedural levels using `free()`; strictly use `queue_free()` to avoid mid-frame segmentation faults.
40	- NEVER broadcast mass state changes to a grid immediately; strictly use `call_deferred()` or `call_group_flags` to avoid frame spikes during turn transitions.
41	- NEVER use heavy TileMapLayer nodes for high-resolution Fog of War; strictly use a GPU Shader Mask via `ColorRect` and an `ImageTexture` updated via `RenderingServer.texture_2d_update()`.
42
43	## 🛠 Expert Components (scripts/)
44
45	### Original Expert Patterns
46	- [meta_progression_manager.gd](scripts/meta_progression_manager.gd) - Foundational meta-progression logic with secure data persistence and currency unlocks.
47	- [roguelike_patterns.gd](scripts/roguelike_patterns.gd) - 10 Essential Roguelike Expert Snippets (AStar, BSP, WorkerThreadPool, ShuffleBa

People who liked this also viewed

6 picks

Type