Was IComponentData (singleton), [Obsolete] — uint Value (not Seed) — the deprecation’s one-release grace window closed; the type and its propagation system (SeededRandomSystem, below) no longer exist in source. Use DOTSCore.GameFlow.RunScopeSingleton.RunSeed directly — this was already the recommended migration target while RunSeed existed
Was [UpdateInGroup(typeof(CoreSystemGroup), OrderFirst = true)], copying RunScopeSingleton.RunSeed into the legacy RunSeed singleton for consumers not yet migrated. Deleted alongside RunSeed — there is nothing to propagate to anymore. Read RunScopeSingleton.RunSeed directly; Random.CreateFromIndex still lives in ProceduralMapSystem below, unaffected by this removal
Two passes, not one. A single loop that creates room i and immediately appends a
connection to rooms[i+1] forward-references an entity that does not exist yet — rooms[i+1]
is still the array’s default Entity (all-zero) at that point, so the connection silently
points at nothing. Create every room first, THEN wire connections in a second pass once the
whole rooms array is populated.
Linear chain only — current impl creates a straight dungeon (no branching). Code comment flags “optional branches” as future work. For branching graphs, the consumer must extend ProceduralMapSystem or post-process connections.
Boss hardcoded to last room — RoomType.Boss is assigned unconditionally at index == RoomCount - 1. To override boss placement, modify FloorConfig struct or post-process connections after generation.
NativeArray must be disposed after ECB loop — room entities exist in the ECB; the NativeArray<Entity> holding their IDs is temp-allocated and MUST be disposed before OnUpdate returns.
ProceduralMapSystem has no OnCreate and no RequireForUpdate — and does not need one.
It is guarded by [RequireMatchingQueriesForUpdate] plus a SystemAPI.Query<RefRW<FloorConfig>>()
foreach, which simply iterates zero times before the singleton bakes. There is no frame-1 crash.
(An earlier version of this skill asserted the opposite; corrected 2026-08-12 against source.)
FloorConfig is read as a QUERY, not a singleton. The system iterates everyFloorConfig
entity, so two of them means two floors generated in the same frame. The GetSingletonRW<FloorConfig>()
call in the re-trigger snippet above is fine for the normal one-config case, but the system itself
imposes no singleton constraint — do not assume one.
Seed + FloorNumber uniqueness — if two floors have the same Seed + FloorNumber value, they generate identically. Use the per-run base seed from DOTSCore.GameFlow.RunScopeSingleton.RunSeed + floor offset for variety — the standalone RunSeed component and its SeededRandomSystem propagator are gone as of 2026-08-21 (ff45564a), so RunScopeSingleton.RunSeed is now the ONLY source, not merely the recommended one.