Aaron Kimbrell 36cefc1ede feat(ugc): brick data through the client's assets; colours from Materials.xml everywhere ...

The UGC server reads brickdb.zip and brickprimitives through DLU's
AssetManager (loose files first, then the client's packs, as the game
does), so packed clients and bricks added to a client work. It falls
back to loose files under res/ as before.

In the LU Toolbox palette (the default), a colour LU Toolbox doesn't
know but the client's Materials.xml has, such as one added to the brick
database, is drawn in its Materials.xml colour instead of black. Ids
neither knows stay LU Toolbox's black.

The dashboard's 3D viewers get the brick colours from the client's
Materials.xml (/api/bricks/materials.js) instead of a hardcoded copy, so
added colours show there too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-28 22:31:13 -05:00

..

CMakeLists.txt

feat(dashboard): assembled mesh route, icon parameter groups and preset samples, pose math in JS

2026-09-28 22:31:12 -05:00

ugc-pose-fixture.json

feat(dashboard): assembled mesh route, icon parameter groups and preset samples, pose math in JS

2026-09-28 22:31:12 -05:00

ugc-pose-math.test.mjs

feat(dashboard): assembled mesh route, icon parameter groups and preset samples, pose math in JS

2026-09-28 22:31:12 -05:00

UgcTests.cpp

feat(ugc): brick data through the client's assets; colours from Materials.xml everywhere

2026-09-28 22:31:13 -05:00