chore: backpack README + own-art test gaps (#103) #124
No reviewers
Labels
No labels
alpha:wave-0
alpha:wave-1
alpha:wave-2
alpha:wave-3
area:assets
area:combat
area:ecology
area:infra
area:render
area:scripting
area:ui
area:world
enhancement
epic
migration
post-alpha
roadmap
tech-debt
type:bug
type:chore
type:design
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
marco/IsoMmo!124
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/backpack-followups"
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?
Summary
Closes #103 — polish follow-ups from the #100 backpack review.
art/gump/container_backpack.README.mdstill told the artist the client draws Weapon/Armor equip slots + a visible 4×4 grid. #100 removed the slots and uses an invisible, free-placement, weight-bounded interior. Rewrote the composition section to the current panel (no slots, no grid; icons scatter/overlap; equip is a double-click).OwnArtTestsonly assertedPixels.Length. Added: RGBA channel-order lock (catches a BGRA swap / dropped channel), semi-transparent alpha (128) survives the bake (the backpack interior is transparent — the property that matters), and thestatic/treebottom-centre anchor branch.The issue's hit-test boundary/gap item is already covered:
BackpackLayoutTestswas reworked to the free-placement API and assertsContains' inclusive-left / exclusive-right boundary — noted in the closing rather than duplicated.Screenshots / recording
No visible change (docs + tests only).
How it was tested
dotnet testgreen —IsoMmo.AssetExtractor.Tests11 → 14 (the 3 new own-art asserts); whole solution builds 0 warnings;just lintclean.Checklist
just lintpasses (CSharpier + analyzers, zero warnings)just testis greenOwnArtTests)