Pure data filter that reconciles a PlacementCatalog and TerrainPalette into a single view of "which terrains are actually available for this session". Extracted from TerrainPaletteUI so the catalog-first filtering contract is testable without UI scene-tree assumptions (no Node instantiation, no _ready/_validate asserts, no parent/child wiring). Catalog-first means: if the session's catalog has tile_entries, those are the canonical entries and the palette is treated as a display theme (icons + colors) rather than the source of truth. The palette's own entries are still available for visual continuity, but the catalog owns what the user can actually select. When no catalog is provided, falls back to the legacy palette-only resolution so scenes that pre-date the catalog contract keep working.
Source: addons/grid_placement/placement/terrain/terrain_catalog_filter.gd
Syntax
class TerrainCatalogFilter extends RefCountedMembers
| Name | Kind | Summary |
|---|---|---|
catalog_from_session | Method | |
get_available_terrain_names | Method | |
resolve_entry_for_terrain | Method |
Guides that use this class
Tutorials built on Grid Placement
- Godot multiplayer grid placement: one host, four sessions
- Godot 2D grid building system: paint, place, save
- Godot 3D grid building system: the runtime loop
- Godot 4 grid-building plugins: build mode vs editor tools
- 3D room placement in Godot: build rooms and stack storeys
- 3D grid placement in Godot 4: full setup tutorial
- Snap to a TileMap in Godot: 2D grid placement
- How to make a farming system in Godot
- How to snap objects to a 3D grid in Godot