feat: add gear and weapon renders
Validate and deploy production / validate (push) Successful in 21s
Validate and deploy staging / validate (push) Successful in 25s
Validate and deploy production / deploy (push) Successful in 1m17s
Validate and deploy staging / deploy (push) Successful in 35s

This commit is contained in:
jb
2026-07-31 22:39:00 -04:00
parent 3acc08c81d
commit aaf9e0ce97
10 changed files with 171 additions and 25 deletions
+14
View File
@@ -1047,6 +1047,20 @@ full-width band. Keep destructive archive controls isolated on the left side of
the action bar and use the established `.moderation-action.danger` treatment;
save and cancel remain grouped on the right.
### Weapon and gear renders
Weapon and gear editors offer an optional item-render upload separate from the
icon system. Operators may save a definition without artwork, then add, replace,
or remove the render in a later edit. The upload accepts JPEG, PNG, WebP, and
AVIF up to 5 MiB. The server center-crops each upload to 1000 × 1000 and stores
it as WebP. It does not call remove.bg, trim the scene, or add transparency.
Show the current square render in the upload control and as a compact square
thumbnail before the item name in ISAC registry rows. Keep the image decorative
when the adjacent text identifies the item. The control states the crop and
format contract so contributors do not confuse a render with a transparent
game-data icon.
Archived records that support restoration replace their destructive archive
control with a green outlined `.moderation-action.restore` control in the same
left-side position. The label must explicitly say “Unarchive” or “Restore”;