# Gadget resource inventory 2026-10-27. Read-only asset investigation; no original file was modified or executed. This report describes serialized resources and inspected pixels. It does not infer gadget timing, collision, selection policy or model attachment from filenames. Binary/input contracts belong in [gadget-controls.md](gadget-controls.md). ## Selection screen and original labels All following Canv IDs are from Original/omt/screens.omt, SHA256 `e8e95231f5d302b41f4fbf33df1c5a08ce4645370f9f519527ff1727b73b7a5e`. Canvas20 (`menu`) is640×480 and already contains the dim gadget tiles and Return/ Practice labels. Unsuffixed, suffix-b and suffix-c tile art are141×141. Their inspected appearances are green, white and blue respectively; which state selects a variant must come from the dispatcher, not the colour. The independent controls investigation reports constructor404E97..404F8B's inventory0..7-to-tile association; the displayed labels below are independently visible in the original pixels. | Group0 item | Original tile label | Unsuffixed / b / c Canv | HUD Canv/name | Control strip | |---:|---|---|---|---| |0|BUBBLE|11 /52 /178|94 `1bubble`|109 `BmenuLBubble`| |1|ROCKETSHIP|12 /46 /171|87 `2rocket`|115 `BmenuLRocketship`| |2|INVISIBLE|13 /47 /172|88 `3invisible`|111 `BmenuLInvisible`| |3|SHRINK RAY|14 /48 /173|89 `4raygun`|113 `BmenuLRayGun`| |4|SCOOTER|15 /49 /174|90 `5scooter`|116 `BmenuLScooter`| |5|REMOTE|16 /50 /175|91 `6remote`|114 `BmenuLRemote`| |6|BASEBALL|17 /51 /176|92 `7baseball`|118 `BmenuLBaseball`| |7|GRAPPLER|18 /45 /177|93 `8grappler`|110 `BmenuLGrappler`| Do not rename tile3 to Jetpack. The separate jetpack HUD canvas119 is named `9jetpack`, and control strip112 is `BmenuLJetPack`; strip113 visibly describes both SHRINK firing and JUMP/JETPACK. This agrees with the port's recovered item3-powered-jump association, but the art itself does not establish firing logic. The rendered selection background places bubble/rocket/scooter/remote across its first row and invisible/shrink/baseball/grappler across its second. Exact hit rectangles and hover/selected state are source-controller evidence, separate from this visual layout observation. The controls investigator specifically recovers white suffix-b as owned idle and green unsuffixed as mouseover; group0 state0/4 hide both to expose the dim background. The blue suffix-c resources are available assets but are not part of those current group0 bindings. Their existence does not justify inventing an unavailable overlay. Other useful screens.omt resources: | IDs / names | Dimensions | Asset role | |---|---|---| |109..116 plus118 `BmenuL*`|393×69|Nine left-side gadget control strips.| |108 `BmenuR2`,117 `BmenuR1`|247×69|Right-side instructions with SELECT/DESELECT INVENTIONS text.| |24/181/182 `return`/`return2`/`return3`|141×78|Return button variants.| |170/179/180 `practice`/`practice2`/`practice3`|141×78|Practice button variants.| |87..94 plus119|80×70|Eight gadget HUD icons and separate jetpack icon.| |84/85 `backpack`/`backpack2`|141×141|Backpack variants.| |253 `CrossHairs`|15×210|Vertical strip;14 square15×15 frames arithmetically fit. Frame meaning/timing is not inferred.| ## Export and integration tools/extractors/gadget_resources.py exports54 exact decoded canvases into a separate directory. It checks original IDs/names/dimensions before writing, uses the existing bounded OMT/RGB555/colour-key decoder, preserves alpha and records archive/payload/RGBA SHA256 plus source offsets/sizes. It protects the entire source asset root, including sibling ASE/png/gam directories when the archive is under omt/. No image generation or replacement art is used. ``` python3 tools/extractors/gadget_resources.py ../Original/omt/screens.omt --output artifacts/extracted/gadgets ``` The generated gadgets.json uses schema1, referenceWidth640/referenceHeight480 and textures with id/name/role/width/height/path/png/sourceOffset/sourceBytes/ sourceSha256/rgbaSha256. File paths are local `canvas_ID.rgba` and `.png`. `tiles` records artItem1..8, literal labels and normal/b/c IDs; suffix roles remain neutral so the source controller owns availability/highlight interpretation. This separate manifest leaves the existing eight HUD/practice resources unchanged. Primary owns prepare.py/package/runtime integration; this investigator did not edit those files. Runtime should reuse UiViewport scaling and pointer conversion. Generated inspection images are in artifacts/gadget-assets/: selection-sheet.png and canvas_20.png. ase-inventory.json records exact hashes/counts for the model files below. The fixture exporter wrote artifacts/extracted/gadgets/gadgets.json. Three regression groups pass in artifacts/gadget-assets/tests.log: exact original resource/pixel/dimension round-trip, rejection of all original asset subtrees, and rejecting changed dimensions before producing partial output. ## Shipped model and animation candidates These are file/content observations, not proof that a given runtime action uses every candidate. The ASE parser maps original coordinates using the existing verified `(x,z,y)` conversion. Jimmy clips share426 vertices/814 faces with the prepared standing mesh, so existing morph preparation can preserve its topology. | Source ASE | Samples / fps | Geometry and bounded use | |---|---|---| |jimshoot.ASE|2 /10|426 vertices/814 faces; original shooting pose candidate. Not in current default prepared animation list.| |jimfly.ASE|2 /10|426/814; already prepared for powered jumping.| |jimswing.ASE|2 /10|426/814; swing pose candidate.| |jimscooter.ASE, jimscooterstop.ASE|2 each /10|426/814; scooter poses.| |jimdrive.ASE|2 /10|426/814; driving pose.| |jimheadshrink.ASE|7 /5|426/814; distinct authored morph sequence, not an inferred uniform scale.| |godscooter.ASE, godscooter2.ASE|2 each /30|195 vertices/370 faces; reference `goddard02.png`.| |godrocket.ASE|3 /5|222 vertices/411 faces; rocket-form candidate.| |ray.ASE|2 /10|5 vertices/3 faces. Material text references `ray0002.ifl`; supplied PNGs ray0000..ray0003 exist. Sequence binding/cadence remains source work.| |hook.ASE|1 /10|40 vertices/68 faces; material references hook.bmp, supplied hook.png exists.| |rope01.ASE,rope02.ASE|1 each /30|6 vertices/6 faces and4 vertices/2 faces.| |laser02.ASE,missile.ASE|1 each /30|8 vertices/8 faces and7 vertices/10 faces; missile's goo.bmp reference is not a verified gadget attachment.| scooter.omt contains shape0 `goddard01`, shape1 `wheel`, matching material/canvas resources0 `goddard128` and1 `scooterwheel2`; archive SHA256 `8d4ffdafee5fd819c5220ee4f608c901a5988fe6b8b13316e15618f5eec75e81`. inventory.omt is an older-looking icon set with BUBBLE/GODJEEP/SCOOTER/jetpack etc; its names alone do not justify replacing screens.omt menu art or IDs. No explicit bubble-named ASE exists in the supplied directory; that bounded filename search does not prove the original bubble geometry was absent/generated. ## Already prepared sounds artifacts/extracted/effects/effects.json already preserves original SoundEffects.omt waves, paths and source byte ranges. Bank SHA256 is `c71e06d93b8a5ef4f4522a5c40220bc8aeaecb889b5de69445db44817fb9acb1`. Useful identities are0 `shrinkray`,1 `jetpack`,2 `gravitybubble`,3 `gravitybubbleoff`, 10 `goddard baseballs`,18 `pickupbaseball`,45 `rocketship`,46 `Scooter`,106 `bubble boing` and117 `click shrink ray`. These are archive identity/name facts; actual activation, repeat, ownership, volume and cancellation still need callers. The existing resource export is sufficient; no duplicate sound extraction is needed. ## Practical next addition and limits Original selection art and control labels are complete enough to implement a source-driven gadget screen without invented icons. For a usable gadget beyond the current powered jump, shrink firing has original pose, beam geometry/PNG frames and both successful-fire/click sounds available; it still needs recovered target, range, timing, energy and interruption policy. The selection3 naming overlap is an explicit reason to implement the combined shrink/jetpack controls coherently. Other gadget assets are candidates for later behavior recovery, not evidence that all eight gadget behaviors are currently implemented.