Apoco Assault Rifle

Stage: original-release evidence verified; replacement AAA concept candidate. No native upgrade accepted.

The first generic long-rifle direction was rejected by the owner. This replacement returns to the original's compact, bulky olive body, crimson upper/rear housings, narrow projecting barrel and gold lower fittings. It is a candidate, not an approved model or gameplay capture. Its generated inset is illustrative; the separately extracted icon below is the exact original.

One canonical design will receive personally authored model/texture work in two selectable treatments: Minecraft-fit and concept-faithful. The visual toggle must not change the weapon's authoritative mechanics.

Rejected first concept retained for history

This is a red-and-olive conventional AoA gun, upgraded from the Mechanical Assault Rifle with an Apoco Upgrade Kit. Its TaCZ concept should feel like an imposing, tactile fantasy-industrial rifle, keeping the original color identity while improving readable construction, handling and feedback.

Lore-informed concept study

This study brings a fungal-cap reading of the scarlet forms and rootlike lower fittings into the mechanical design. These organic motifs are our artistic interpretation, not confirmed original creator intent. The earlier metal-focused sheet remains above for comparison and history. Neither candidate is an accepted model. Review original silhouette, hand space, surface complexity and both visual treatments before selecting the final canonical design.

Candidate review

Origin and lore review

The confirmed lineage is Mechanical Assault Rifle + Apoco Upgrade Kit; that kit is associated with Vox Ponds and appears in its packaged loot table. Its incomplete mechanical base also appears in Iro Crate loot and is completed with Power Core and Mecha Gear. The documented Iromine ancestry and Vox Ponds upgrade must both guide the design. The checked sources do not identify an in-world maker.

The red forms' mushroom-like reading and the fittings' root-like reading remain visual interpretations, not confirmed creator intent. Do not silently replace those readings with generic metal housings. Any added organic growth or construction story must be labeled as our adaptation until sourced.

Verified provenance and interpretation boundaries · Pinned entry hashes

The current replacement concept still needs this lore review; improved outline alone is not final acceptance.

Exact-version original

Pinned target: Minecraft 1.20.1 / AoA 3.7.1. The released class inherits BaseGun behavior, uses Limonite Bullets and creates RedBulletEntity. The released renderer registration traces through bootstrap 194 to lambda$static$84: ColouredTexturedProjectileRenderer with ColourUtil.RED and the Limonite bullet texture. This is source evidence, not a game capture.

Stored registration values: base damage 5.625, durability 5920, delay 6 ticks, recoil modifier 0.6000000238418579. Configs, enchantments, targets and inherited timing affect actual gameplay; these values are not a universal final damage or measured firing-rate claim.

The original item model is a generated gun item using this exact icon. Keep the icon and versioned baseline beside every later concept/model comparison.

Crafting and progression

The released upgrade-kit recipe takes aoa3:mechanical_assault_rifle and aoa3:apoco_upgrade_kit to produce aoa3:apoco_assault_rifle. The upgraded armory should preserve that path, then add clearly documented optional component work and earned cosmetics. New recipes or costs remain design proposals until implemented and tested.

Proposed complete experience

• A red/olive/brass canonical family with visible receiver/feed continuity and enough hand/trigger-guard space. The rejected first concept's expanded stock is removed. The replacement's compact proportions and upper housings still need orthographic fidelity and aiming review.
• Crisp red shot feedback, short controllable tracer trails and material-aware sparks. The concept impact shower is cosmetic direction; it does not establish explosive or area damage.
• Optional optics, handling pieces and muzzle modules with distinct silhouettes and resolved stats. Cosmetic swaps cannot secretly alter mechanics.
• Retained-magazine service and inspect choreography with explicit hand ownership and safe interruption; the sheet is only a storyboard.
• Earned red/brass variant, charm sockets, static/animated/emissive stickers and emblems. Effects and charms need clear gameplay provenance and bounded costs.
• Projectile, muzzle, impact, decal and finisher channels must be independently configurable. Original behavior and future upgrade mechanics must remain separately documented.

Still required before acceptance

Full orthographic/model sheets; projectile/impact and finisher storyboards; every attachment family and recipe; source model and UV/textures; all handling/fire/service/inspect clips and sounds; native hand fit; confirmed-shot resource accounting; saved builds; multiplayer; optional-mod tests; measured startup/frame-time costs; actual in-game original-versus-upgraded footage.

Complete weapon standard applies in full. No feature is silently waived because this first concept sheet does not show it.

Exact evidence and first-pass feature status

Original AoA identity/assets: Tslat and contributors. Concept candidate: generated project artwork, not a native game screenshot. No final visual or gameplay acceptance.

Exterior modeling reference

This generated sheet guides hand-authored geometry, but its views retain perspective and detail differences. It is not a validated orthographic blueprint or native model. Compare against the retained hero concept and exact original sprite. Review and limitations.

Local reconstruction reference

The local CPU trial produced actual editable reference meshes. A 256-grid extraction reused saved scene code and produced 56,708 triangles; it still has soft detail, invented hidden surfaces and ten disconnected components that are not authored animation parts. Three faces fall below the chosen near-zero-area threshold, although none have exactly zero area. It remains unaccepted for canonical/native use.

Study and editable reference bundle. Use it for volume inspection and deliberate retopology alongside the preserved concepts, never as a finished weapon.

Recoil interpretation

For this pinned 1.20.1 release, the stored constructor recoil input is not the inherited modifier getter: the inspected BaseGun.getRecoilModifier() returns approximately 0.35. The per-shot method and later client application determine the actual recoil path. Do not infer a stronger or weaker measured kick from the constructor column alone. This clarification does not change the original values, weapon balance or acceptance state. Resolved method routing.