Parse and use MazeMap's marker colours #20
Labels
No labels
animation
audio
blocked
bug report
controversial
documentation
easy
feature request
hard
medium
multiplayer
physics
ui
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
elsie/liuverse#20
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Every feature in the MazeMap
markerslayer carries acolorproperty --stairs arrive as
rgba(0,255,230,1.00), rooms asrgba(239,239,239,1.00)-- andthe bake throws it away.
interiors.rs:299readstextand nothing else:property_coloralready exists in the same file for thearea-filllayer anddoes the
rgba(...)parse. So MazeMap already tells us what colour a room signand a stair sign are supposed to be, and
MARKER_ALBEDOSinliuverse/src/config.rsis instead a hand-picked five-slot palette indexed byMARKER_*kind.Bake the colour through
BakedMarkerand let it drive the marker albedo, withthe palette as the fallback for the POI-dump markers (which carry no colour --
the dump has no
colorfield).This also means a new
MARKER_*kind needs no new palette entry, which is thereal argument for it.
Related
Closed by the merged batch: #142 (tier1-features) landed this, rebased onto main at
609dcb8.