Alexa 79a2b9844e fix: room-level DataBlob must be the blob sub-room 0 actually loads ...

Regression from adding the room-level DataBlob key: it was filled from the
per-ROOM name while sub-room 0 resolves its own, override included. A dorm's
data is per-PLAYER (dorm_p{id}_v*.dat) and reaches the builder as that
override, so the room level advertised a room_{id}_* file that was never
written. The client fetched it and rejected the whole room with "the data in
the room you are trying to load is corrupt" — which reads like a broken save
rather than a payload that disagrees with itself.

Both now come from one resolved value, so whichever key the client reads
first it gets the same file. The no-scenes fallback sub-room honours the
override too, instead of falling back to the per-room name.

Adds the invariant as a test: room-level DataBlob == SubRooms[0].DataBlob.
The DTO parity tests could not have caught this — the key was present and
correctly named, it just pointed somewhere else.

2026-07-28 11:09:58 +03:00

..

RoomsController.cs

fix: room-level DataBlob must be the blob sub-room 0 actually loads

2026-07-28 11:09:58 +03:00

RoomsModerationController.cs

feat: cloned rooms get their own copy of the source's save data

2026-07-28 10:28:50 +03:00