A placement issue pairing an internal service tag with a player-facing message. Upstream callers set service to the component that emitted the issue (e.g. &"SmoothPlacementService") and message to the player-facing text (e.g. "That spot is already taken."). The presentation layer shows only message; service is for logs and telemetry. Keeping them apart means players never see internal names.
Source: addons/grid_placement/placement/manager/placement_issue.gd
Syntax
class PlacementIssue extends RefCountedMembers
| Name | Kind | Summary |
|---|---|---|
service | Property | Internal service that emitted the issue (e.g. &"SmoothPlacementService"). |
attempt_id | Property | The plugin attempt id of the operation that produced this issue. Stamped when the report is published, so a free-text issue can be joined to the typed PlacementLifecycleResult that carries the same id. |
message | Property | Player-facing message. This is what the UI shows. |
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