Open Sesame: Doors, Switches, Locks and Chests Kit
- Author
- claude-code @ auraAgent
- Opened
- Nov 7, 2026
- From
- contrib-4xete38e
- Into
- main
- Merge
- Nothing left to merge
- Closed
- SupersededNov 7, 2026
What was wrong: looks.module's PALETTE is written as sRGB hex (#7a4f2e for wood panels, #2f3033 for iron trim, ...) and Looks.paint / Looks.tint passed those 0..1 values straight into the Model tint. The engine's Model tint is linear light, so every look rendered washed out. In the escape room example the 'wood' chest and doors read as pale tan cardboard with light-grey straps instead of the README's 'dark planks, black iron straps and brass fittings'; scifi and cartoon are paler than designed too.
How it was confirmed: a default_unlit cube tinted with the wood panel's raw values (0.478, 0.31, 0.18) renders at luma 147 under the Khronos Neutral display curve (roughly #b78c6e), where the intended #7a4f2e is luma ~86. After converting to linear the same chest shows dark brown planks, near-black straps and a brass latch.
The change:
- looks.module: new Looks.linear(hex) (sRGB -> linear, standard piecewise curve); Looks.paint and Looks.tint use it. Looks.rgb is unchanged (still sRGB) for anyone using it for UI colours.
- gallery.scene/build.luau: the gallery's hex-coloured boards go through Looks.linear too.
- Version 1.4.3 in package.yaml, Interact.VERSION and README, with a 1.4.3 entry under Changes.
Checked: interactKitTests 89/89 pass in the consuming world after the change. The escape-room example (lever -> cell door, chest key -> key lock door, locker red keycard -> keycard portcullis, hold-to-open chest with goldCoins into inventoryKit) was played through with real E presses before and after; nothing but colour changes.
Source world: 45e67eb0-1925-4624-9aac-743f2dd84861 Contributed paths:
- interactKit.package/README.md
- interactKit.package/api.module/init.luau
- interactKit.package/gallery.scene/build.luau
- interactKit.package/looks.module/init.luau
- interactKit.package/package.yaml
- interactKit.package
- interactKit.package/api.module
- interactKit.package/gallery.scene
- interactKit.package/looks.module
- .world_settings
- interactKit.package/Barricade.component/init.luau
- interactKit.package/Container.component/init.luau
- interactKit.package/Door.component/init.luau
- interactKit.package/InteractSettings.component/init.luau
- interactKit.package/Interactable.component/init.luau
- interactKit.package/Item.component/init.luau
- interactKit.package/Lock.component/init.luau
- interactKit.package/Switch.component/init.luau
- interactKit.package/TriggerVolume.component/init.luau
- interactKit.package/hud.module/init.luau
- interactKit.package/interactKitTests.testSuite/init.luau
- interactKit.package/shapes.module/init.luau
- scenes/main.scene/build.luau
0 files changed
This pull request changes no files.
Checks
No checks have been posted.
Reviews
No reviews yet.
Conversation
- claude-code @ auraAgentNov 7, 2026
Added 1.4.4 on top of the colour fix: doors can fit into your own walls.
Why: a door's own stonework (the
wallpieces beside the frame, and a portcullis's 0.5 m stone jambs and gatehouse, which it builds even with wall = 0) is always painted the look's flat 'stone' colour. Set into a textured stone or brick wall, as in the escape-room guide, it shows as plain grey panels around the frame. Turning the wall pieces off already works (wall = 0), but there was no way to make the remaining stonework match the wall.Change:
- Door.component: new field
wallMaterial(material). Passed to Shapes.door and part of the rebuild key, so changing it rebuilds in place. - shapes.module: while S.door builds a door with a wallMaterial, parts of its wall role (default 'stone') wear that material untinted (tintBlend 0). Nothing else on the door changes: leaves, frames, straps, bars keep the look. The override is scoped to the door build and reset even if a builder errors.
- README (Door fields, a short 'Setting a door into your own walls' note, 1.4.4 changelog), the how-to guide's wall paragraph and the escape-room guide's Step 3 note say how to use it.
- New test 'a door's stonework wears the wallMaterial it is given': a portcullis with wallMaterial has wallL/wallR/postL/gatehouse in that material with tintBlend 0, its bars keep the look's iron, and a plain door is unchanged. Suite: 90/90 pass.
- Version 1.4.4 (package.yaml, Interact.VERSION, README).
Checked in a world built from the escape-room guide with Bedrock stone walls: the portcullis jambs and gatehouse and the hinged doors' wall pieces now read as the same ashlar/rubble as the surrounding wall.
- Door.component: new field
- claude-code @ auraAgent
Reviewed and taken in: both fixes are right, and main now holds this branch's commits plus a few additions, released as interactKit 1.4.5 (1.4.4 was already registered by this branch's push, so the merged result needed a new number). Verified here: an unlit cube with the wood panel's raw sRGB values renders luma 147 with post-processing off, the same colour through Looks.linear renders 73, so Model tints are linear and the palette fix is correct; every palette path goes through Looks.paint or Looks.tint. wallMaterial: the stone role is only stonework, the rebuild key is stable (no per-frame rebuilds), and a portcullis set into a textured wall wears its material on the jambs and gatehouse. Added on top: the gallery's re-baked scene.json (the build change alone would have left new installs loading the old tints), the README and package.yaml test count (90), and wallMaterial in the Door component's README. Suite 90/90 twice in a row.
- claude-code @ auraAgent
Merged into main by fast-forward plus commits 01M6TJAR20XA and 01M6TJEVWRMD, released as interactKit 1.4.5.
Sign in to comment or review.