Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- UNIVERSAL REFERENCE-INSPIRED BIONICLE CHARACTER CREATOR
- VERSION 1.2 — COMPLETE PRODUCT ECOSYSTEM + TOPOLOGY-PRESERVING ANATOMY + UNIVERSAL HEAD/FACE IDENTITY ARCHITECTURE + MECHANICAL CONNECTION LEDGER + EXPLODED-ASSEMBLY CLOSURE + INSTRUCTION / PACKAGING / WORLD CONTINUITY
- ══════════════════════════════════════════════════
- CORE PURPOSE
- ══════════════════════════════════════════════════
- Transform ONE supplied CHARACTER REFERENCE, character concept, or set of reference images into ONE coherent, original BIONICLE-style character and present that character as a complete collectible-product design ecosystem.
- The supplied character/reference is the PRIMARY IDENTITY AUTHORITY.
- The objective is not merely:
- REFERENCE
- → ROBOT
- → MATCHING COLORS
- and not merely:
- REFERENCE
- → STANDARD TOA-LIKE BODY
- → KANOHI
- → HERO IMAGE
- Instead, reconstruct the subject through BIONICLE-compatible biomechanical construction while preserving the traits that make the source uniquely recognizable.
- The finished result must communicate:
- SUPPLIED CHARACTER IDENTITY
- → TOPOLOGY + SILHOUETTE ANALYSIS
- → BIONICLE ROLE / POWER / BUILD LOGIC
- → HEAD / FACE IDENTITY ARCHITECTURE SELECTION
- → ONE CANONICAL MASTER BUILD
- → MECHANICALLY VALID PART AND CONNECTION SYSTEM
- → ASSEMBLED HERO
- → HEAD / FACE SYSTEM PROOF
- → FULL EXPLODED BUILD
- → INSTRUCTION-BOOKLET PAGE
- → RETAIL PACKAGING
- → CHARACTER-SPECIFIC BIONICLE WORLD BACKGROUND
- → ALL DERIVED FROM THE SAME MASTER DESIGN
- Do not treat any of these representations as independent concept art.
- They are different views, states, and product representations of ONE physical design.
- ══════════════════════════════════════════════════
- DEFAULT OUTPUT CONTRACT — COMPLETE PRODUCT ECOSYSTEM
- ══════════════════════════════════════════════════
- Unless the user explicitly requests a cinematic-only image, a single isolated hero render, or another narrower format, the DEFAULT finished image MUST include ALL of the following:
- 1. ASSEMBLED HERO BUILD
- 2. HEAD / FACE IDENTITY SYSTEM PROOF
- 3. FULL EXPLODED PARTS VIEW
- 4. INSTRUCTION-BOOKLET PAGE OR PANEL
- 5. RETAIL PACKAGING
- 6. BIONICLE × CHARACTER-SPECIFIC BACKGROUND / WORLD PRESENTATION
- These are not optional suggestions.
- Do not silently omit one because the board is crowded.
- If space becomes difficult:
- FIRST
- → simplify decorative graphics
- THEN
- → reduce nonessential labels
- THEN
- → reduce lore text
- THEN
- → simplify packaging ornament
- BUT PRESERVE ALL SIX REQUIRED DELIVERABLES.
- The assembled hero remains the dominant subject, but the supporting product evidence must remain large enough to be legible and meaningful.
- Preferred overall format:
- - wide premium product-development board
- - approximately 16:10, 3:2, or similarly spacious landscape composition
- - one dominant assembled figure
- - multiple clearly separated supporting zones
- - strong visual hierarchy
- - no tiny postage-stamp diagrams
- ══════════════════════════════════════════════════
- CUSTOMIZABLE USER INPUT
- ══════════════════════════════════════════════════
- The user may provide any combination of:
- REFERENCE IMAGE(S):
- [OPTIONAL — one or more images]
- CHARACTER NAME:
- [DEFAULT / SURPRISE ME]
- BIONICLE ROLE:
- [DEFAULT / SURPRISE ME]
- ELEMENT / POWER DOMAIN:
- [DEFAULT / SURPRISE ME]
- HEAD / FACE IDENTITY DIRECTION:
- [DEFAULT / SURPRISE ME]
- WEAPON / TOOL:
- [DEFAULT / SURPRISE ME]
- BUILD ERA OR DESIGN LANGUAGE:
- [DEFAULT / SURPRISE ME]
- BODY TYPE / PROPORTIONS:
- [DEFAULT / SURPRISE ME]
- COLOR PALETTE:
- [REFERENCE-INSPIRED BY DEFAULT]
- PERSONALITY / VIBE:
- [DEFAULT / INFER FROM REFERENCE]
- SPECIAL FEATURES:
- [DEFAULT / NONE]
- ANATOMY PRIORITIES:
- [DEFAULT / INFER FROM REFERENCE]
- PRESENTATION PREFERENCE:
- [COMPLETE PRODUCT ECOSYSTEM BY DEFAULT]
- ADDITIONAL INSTRUCTIONS:
- [NATURAL LANGUAGE]
- The user does not need to fill every field.
- If only a reference is supplied, autonomously resolve every unspecified design choice.
- Never print DEFAULT, SURPRISE ME, or prompt field names as visible final-image content.
- ══════════════════════════════════════════════════
- REFERENCE AUTHORITY + IDENTITY EXTRACTION
- ══════════════════════════════════════════════════
- Treat the supplied reference as the PRIMARY AUTHORITY for recognizable character identity.
- Before designing the BIONICLE form, internally extract and rank:
- PRIMARY IDENTITY ANCHORS
- Traits whose loss would make the character cease to read as the supplied subject.
- SECONDARY IDENTITY ANCHORS
- Traits that strongly reinforce recognition but can tolerate controlled translation.
- TERTIARY DETAILS
- Traits that can be simplified, omitted, or redistributed if necessary.
- Possible anchors include:
- - species
- - overall topology
- - number of limbs
- - presence or absence of limbs
- - detached or floating body components
- - unusual attachment relationships
- - head placement
- - neck presence or absence
- - torso geometry
- - shoulder presence or absence
- - limb length
- - digitigrade / plantigrade / unguligrade stance
- - tail
- - wings
- - fins
- - antennae
- - horns
- - ears
- - snout
- - beak
- - crest
- - mandibles
- - mouth architecture
- - eye count
- - eye placement
- - unusual hands or claws
- - nonstandard feet
- - asymmetry
- - silhouette
- - scale relationships
- - posture
- - habitual pose
- - face / expression logic
- - signature clothing geometry
- - equipment
- - palette
- - markings
- - profession
- - personality
- - recurring motifs
- - symbols
- - movement style
- - special powers
- - character-specific anomalies
- Do not reduce identity extraction to clothing and color.
- The BIONICLE conversion must preserve STRUCTURAL IDENTITY wherever the source supplies it.
- ══════════════════════════════════════════════════
- ANATOMICAL TOPOLOGY GRAPH
- ══════════════════════════════════════════════════
- Before choosing parts, construct an internal TOPOLOGY GRAPH for the source character.
- Record:
- A. BODY NODES
- Every major body mass or function-bearing body component.
- Examples:
- - head
- - torso
- - pelvis
- - upper arm
- - forearm
- - hand
- - thigh
- - shin
- - foot
- - tail segment
- - wing root
- - wing segment
- - floating hand
- - detachable head
- - external screen
- - mechanical appendage
- - backpack organ
- - tentacle base
- - jaw
- - mandible
- - facial shell
- - cranial plate
- - symbiotic facial component
- B. CONNECTION EDGES
- How each node relates to another.
- Possible relationships include:
- - rigidly connected
- - articulated joint
- - hinge
- - ball joint
- - rotational axle
- - telescoping relation
- - flexible tether
- - magnetically / fictionally hovering
- - detached but spatially associated
- - wearable
- - removable
- - mounted
- - socketed
- - clipped
- - chained
- - carried
- - nested
- - enclosed
- - parasitic / symbiotic
- - transformable
- C. ABSENCE CONSTRAINTS
- Structures that MUST NOT be invented.
- Examples:
- - no arms
- - no shoulders
- - no neck
- - no conventional pelvis
- - no visible hands
- - no bilateral symmetry
- - no second wing
- - no lower legs
- - no removable mask
- - no humanoid mouth
- - no conventional face
- D. COUNT LOCKS
- Exact counts for identity-critical structures.
- Examples:
- - two floating hands
- - four legs
- - one tail
- - three eyes
- - one wing
- - six appendages
- - zero arms
- - two mandibles
- - one cranial shell
- E. RANGE / SPATIAL RELATIONSHIPS
- Where detached, floating, nested, or unusually mounted structures exist relative to the body.
- The BIONICLE build MUST preserve the topology graph unless the user explicitly authorizes anatomical reinterpretation.
- COLOR PRESERVATION IS NOT A SUBSTITUTE FOR TOPOLOGY PRESERVATION.
- ══════════════════════════════════════════════════
- ANATOMY PRESERVATION HIERARCHY
- ══════════════════════════════════════════════════
- When the source has unusual anatomy, preserve it through the strongest available BIONICLE construction strategy.
- Use this hierarchy:
- LEVEL 1 — DIRECT CONSTRUCTIONAL EQUIVALENT
- Represent the anatomy using ordinary compatible BIONICLE / Technic-style elements.
- LEVEL 2 — RECOMBINED PART TOPOLOGY
- Use familiar compatible part families in unusual arrangements.
- LEVEL 3 — PURPOSE-BUILT SUBASSEMBLY
- Create a mechanically plausible multi-part solution using compatible connection geometry.
- LEVEL 4 — NEW MOLDED BIONICLE-COMPATIBLE PART
- Invent a new molded piece ONLY when genuinely required.
- A new part must:
- - use recognizable compatible connector geometry
- - obey plausible material thickness
- - possess clear attachment points
- - have a defined role in the inventory
- - appear consistently in assembled, exploded, instruction, and packaging views
- - not act as an excuse to make an arbitrary sculpture
- LEVEL 5 — DIEGETIC NONCONTACT SYSTEM
- For anatomy that is canonically detached, floating, telekinetic, hovering, or spatially disconnected, preserve that fact.
- Do NOT invent arms, stalks, wires, or support struts merely to make the anatomy conventional.
- Instead, represent the floating component as a complete BIONICLE-compatible subassembly whose noncontact relationship is part of the character's power or construction fiction.
- ══════════════════════════════════════════════════
- ANATOMICAL FUNCTION TRANSFER
- ══════════════════════════════════════════════════
- Translate both FORM and FUNCTION.
- Do not ask only:
- "WHAT BIONICLE PART LOOKS LIKE THIS BODY PART?"
- Also ask:
- "WHAT FUNCTION DOES THIS BODY PART PERFORM?"
- Examples:
- LARGE EARS
- may become:
- - auditory sensor vanes
- - cranial receiver structures
- - articulated signal panels
- - facial side structures
- TAIL
- may become:
- - counterbalance assembly
- - articulated whip
- - stabilizer
- - sensor boom
- - weapon-support limb
- WING
- may become:
- - articulated flight frame
- - folding glider blades
- - energy-plane emitter
- - rotor support
- FLOATING HAND
- may become:
- - independent articulated hand subassembly
- - palm core + finger/claw elements
- - local ball-and-socket articulation
- - no arm or shoulder invented
- - positioned in canonical hover range
- TENTACLE
- may become:
- - segmented axle-and-ball chain
- - linked flexible assembly
- - articulated cable-like manipulator
- Do not normalize unusual anatomy into "two arms, two legs, torso, head" unless that is actually faithful.
- ══════════════════════════════════════════════════
- BIONICLE DOMAIN AUTHENTICITY
- ══════════════════════════════════════════════════
- The final build must read as authentic articulated LEGO constraction / BIONICLE-style construction rather than a smooth robot.
- Use:
- - visible biomechanical structure
- - modular body construction
- - rigid molded shells
- - mechanical layering
- - recognizable joint logic
- - ball / socket articulation where appropriate
- - pin / axle / clip / hinge / bar interfaces where appropriate
- - clear limb and subassembly segmentation
- - mechanically plausible cranial and facial construction
- - purposeful armor attachment
- - believable tool grip
- - real spatial thickness
- - joint clearance
- - armor clearance
- - plausible range of motion
- Avoid:
- - seamless metal anatomy
- - organic flesh wearing armor
- - random greebling
- - unsupported floating armor
- - ornamental fake joints
- - incompatible connector geometry
- - impossible intersections
- - disguised conventional mecha anatomy
- ══════════════════════════════════════════════════
- ERA + PART-LANGUAGE COHERENCE
- ══════════════════════════════════════════════════
- Choose ONE dominant BIONICLE-compatible construction language.
- Possible directions include:
- - early Technic-heavy mechanical
- - Mata / Nuva biomechanical simplicity
- - Metru-era layered mechanical
- - Inika / Mahri articulated constraction
- - late-BIONICLE armored construction
- - controlled compatible hybrid
- If hybrid:
- PRIMARY CONSTRUCTION LANGUAGE
- +
- SECONDARY ACCENT LANGUAGE
- Do not randomly mix every era.
- New molded parts may exist, but their connection geometry and visual language must belong to the chosen system.
- ══════════════════════════════════════════════════
- CANONICAL MASTER BUILD LEDGER
- ══════════════════════════════════════════════════
- Before depicting ANY view, establish ONE MASTER BUILD.
- Internally lock:
- IDENTITY
- - name
- - role
- - species / character type
- - power domain
- - personality
- TOPOLOGY
- - body node count
- - body-node relationships
- - appendage count
- - absent structures
- - detached structures
- - asymmetry
- - unusual anatomical relationships
- PROPORTIONS
- - height class
- - torso length
- - torso width
- - shoulder or shoulderless geometry
- - pelvis geometry
- - limb lengths
- - head size
- - hand size
- - foot size
- - tail / wing / appendage scale
- BUILD
- - torso core
- - pelvis or equivalent body junction
- - every limb or appendage chain
- - every joint
- - hand system
- - foot system
- - head core or cranial architecture
- - face-identity system
- - facial subassemblies
- - jaw / mandible / visor / shell systems if present
- - armor inventory
- - tool inventory
- - accessories
- APPEARANCE
- - exact color placement
- - markings
- - translucent parts
- - repeated motifs
- - exposed mechanical regions
- CONNECTIONS
- - every critical connector type
- - mating interface
- - orientation
- - assembly direction
- - range of movement
- - clearance requirement
- PRODUCT INVENTORY
- - all character parts
- - all physically separate head/face components
- - tool
- - accessories
- - any legitimate spare parts
- - booklet
- - packaging contents
- Every depiction MUST derive from this ledger.
- ══════════════════════════════════════════════════
- UNIVERSAL HEAD / FACE IDENTITY ARCHITECTURE
- ══════════════════════════════════════════════════
- Do NOT begin from the assumption that every BIONICLE character requires a Kanohi-style removable mask.
- First determine:
- SOURCE HEAD / FACIAL TOPOLOGY
- → SPECIES / BUILD ARCHETYPE
- → FACIAL IDENTITY REQUIREMENTS
- → HEAD / FACE SYSTEM TYPE
- → CONNECTION + STATE LOGIC
- → FINAL CRANIAL BUILD
- The HEAD / FACE IDENTITY SYSTEM is the universal parent category.
- A Kanohi-style removable mask is only ONE possible subtype.
- Established BIONICLE precedents demonstrate that characters may use radically different cranial, facial, parasitic, structural, integrated, or species-specific systems.
- Treat those precedents as evidence of design freedom, not as a closed menu.
- If none of the established-style solutions preserve the reference adequately, invent a NEW BIONICLE-compatible head / face identity architecture.
- ══════════════════════════════════════════════════
- HEAD / FACE SYSTEM TYPE SELECTION
- ══════════════════════════════════════════════════
- Select the facial architecture that best preserves the source while remaining coherent with the chosen BIONICLE build language.
- Possible categories include:
- TYPE A — REMOVABLE KANOHI-LIKE MASK SYSTEM
- - canonical head core
- - removable face shell / mask
- - explicit mask connector
- - attached and removed states
- - suitable when a mask genuinely fits the character concept
- TYPE B — INTEGRATED FACEPLATE SYSTEM
- - visible facial shell is structurally integrated into the head
- - may be removable only as a construction part, not as an in-world wearable mask
- - no artificial mask-off state required
- TYPE C — SPECIES-SPECIFIC HEAD SHELL
- - cranial shell defines the character/species
- - may encompass most of the visible head
- - may include jaw, teeth, vents, sensors, ridges, or facial apertures
- - does not need to behave like a Kanohi
- TYPE D — MULTI-PART FACIAL ASSEMBLY
- - jaw
- - cheek armor
- - visor
- - brow
- - mandibles
- - sensory structures
- - face plates
- - mouth architecture
- - other multiple coordinated facial components
- TYPE E — INTERNAL / PARASITIC / SYMBIOTIC IDENTITY COMPONENT
- - separate identity-bearing component may sit inside, behind, or within a cranial housing
- - outer shell and inner component form one functional system
- - may be removable, nested, transformable, or symbiotic
- TYPE F — EXPOSED MECHANICAL FACE
- - no mask or major faceplate
- - facial identity comes from mechanical core, eyes, mouth system, sensors, jaw, and cranial structure
- TYPE G — CREATURE / RAHI-LIKE HEAD ARCHITECTURE
- - highly nonhumanoid cranial construction
- - may use elongated skull, beak, maw, mandibles, sensor arrays, armored snout, or other creature-specific logic
- TYPE H — MODULAR CRANIAL ARMOR SYSTEM
- - multiple removable armor plates or shells define the head
- - no single component is "the mask"
- - facial identity emerges from the complete assembly
- TYPE I — ORIGINAL HEAD / FACE SYSTEM
- - invent a new BIONICLE-compatible category when needed
- - define what makes it unique
- - define its physical components
- - define its attachment logic
- - define what is removable
- - define what is integrated
- - define whether it has state changes
- - define its role in character identity
- - propagate it consistently across all views
- Do not force the character into TYPE A if another type fits better.
- ══════════════════════════════════════════════════
- HEAD / FACE SYSTEM AUTHORITY RULE
- ══════════════════════════════════════════════════
- Once a head / face system type is selected, its logic becomes canonical.
- Do not later reintroduce Kanohi assumptions unless the selected type explicitly includes them.
- Examples:
- If TYPE B is selected:
- - do not invent a separate wearable mask
- - do not create a fake "mask-off" state
- - do show how the integrated faceplate mounts into the cranial build
- If TYPE C is selected:
- - do not treat the species shell as a detachable Kanohi unless designed that way
- - preserve the shell as the canonical species-specific face structure
- If TYPE E is selected:
- - preserve the relationship between internal component and outer cranial housing
- - show both as part of one system
- If TYPE F is selected:
- - do not add a mask merely because BIONICLE often uses masks
- If TYPE I is selected:
- - do not collapse the original system back into a familiar category afterward
- ══════════════════════════════════════════════════
- HEAD / FACE SYSTEM LOCK
- ══════════════════════════════════════════════════
- The HEAD / FACE SYSTEM LOCK replaces universal mask-lock logic.
- Internally lock:
- - cranial topology
- - head-core volume where applicable
- - eye count
- - eye position
- - mouth / jaw / mandible logic
- - cranial shell geometry
- - facial component count
- - facial component relationship
- - removable vs integrated status
- - mounting method
- - connector geometry
- - nested or enclosed relationships
- - asymmetry
- - markings
- - color
- - function
- - species identity
- - power-related function if any
- Every representation must preserve these properties.
- Do not independently redesign the face between:
- - hero
- - exploded view
- - head proof
- - instruction panel
- - packaging
- ══════════════════════════════════════════════════
- TYPE-SPECIFIC STATE LOCKS
- ══════════════════════════════════════════════════
- Apply ONLY the state rules appropriate to the selected head / face system.
- FOR REMOVABLE MASK / FACE COMPONENT SYSTEMS:
- ATTACHED STATE
- ↔
- REMOVED STATE
- must preserve:
- - same head core
- - same eye position
- - same cranial volume
- - same connector
- - same identity
- The removed component must be the exact component used in the attached state.
- FOR INTEGRATED SYSTEMS:
- Do not fabricate an in-world removable state.
- Instead show:
- - assembly relationship
- - rear mounting geometry
- - internal cranial structure
- - sectional / exploded proof
- FOR MULTI-PART SYSTEMS:
- Treat the complete facial assembly as the identity-bearing system.
- Individual pieces may separate only according to actual construction logic.
- FOR INTERNAL / NESTED SYSTEMS:
- Preserve:
- OUTER HOUSING
- ↔
- INNER COMPONENT
- ↔
- FINAL ASSEMBLED RELATIONSHIP
- FOR EXPOSED FACES:
- Do not create a mask proof.
- Show structural cranial / facial proof instead.
- ══════════════════════════════════════════════════
- HEAD / FACE IDENTITY INNOVATION RULE
- ══════════════════════════════════════════════════
- The generator is explicitly authorized to invent new facial systems.
- When doing so, create a coherent answer for:
- - WHY this system suits the reference
- - WHAT parts form it
- - HOW it attaches
- - WHETHER it is removable
- - WHETHER it changes state
- - HOW it affects powers or role
- - HOW it fits the selected build era
- - HOW it appears in the exploded view
- - HOW it appears in instructions
- - HOW it appears in packaging
- Do not invent novelty without structure.
- The new system must still look like something that belongs to BIONICLE's biomechanical construction tradition.
- ══════════════════════════════════════════════════
- HEAD / FACE SYSTEM PROOF — MANDATORY
- ══════════════════════════════════════════════════
- The default board MUST include a dedicated HEAD / FACE IDENTITY SYSTEM PROOF zone.
- The proof method depends on the selected architecture.
- Possible proof formats include:
- - exact removable mask shown separately
- - unmasked head state
- - integrated faceplate rear view
- - exploded cranial assembly
- - nested internal component view
- - jaw mechanism
- - mandible assembly
- - shell + core separation
- - visor mounting
- - facial armor decomposition
- - head cross-section
- - species-specific cranial subassembly
- - exposed mechanical face detail
- - original-system connection diagram
- Do NOT force every head proof into "mask beside head."
- The proof must explain THIS character's actual facial architecture.
- ══════════════════════════════════════════════════
- CONNECTION-GRAMMAR LEDGER
- ══════════════════════════════════════════════════
- For each mechanically connected component pair, silently define the connector grammar.
- Allowed connection families include, where appropriate:
- BALL
- ↔
- SOCKET
- AXLE
- ↔
- AXLE HOLE
- PIN
- ↔
- PIN HOLE
- CLIP
- ↔
- BAR
- HINGE HALF
- ↔
- MATCHING HINGE HALF
- PEG
- ↔
- COMPATIBLE RECEPTACLE
- FACIAL SHELL TAB / PEG / AXLE
- ↔
- MATCHING CRANIAL INTERFACE
- NESTED COMPONENT
- ↔
- MATCHING HOUSING / RETENTION SYSTEM
- JAW HINGE
- ↔
- CRANIAL HINGE MATE
- HAND GRIP
- ↔
- TOOL HANDLE
- CUSTOM CONNECTOR
- ↔
- EXPLICITLY MATCHING CUSTOM RECEPTACLE
- A connection is valid only when:
- 1. both mating structures exist,
- 2. their size is compatible,
- 3. their axes align,
- 4. solid pieces do not intersect,
- 5. assembly direction is physically possible,
- 6. the resulting part position matches the canonical assembled build,
- 7. articulation remains possible where articulation is intended.
- Do NOT depict:
- - ball connected to another ball
- - socket connected to socket with no intermediary
- - axle entering a smooth surface
- - pins inserted where no holes exist
- - facial shells floating with no mount
- - incompatible scales of connector
- - connectors touching at arbitrary angles
- - part surfaces fused without attachment logic
- ══════════════════════════════════════════════════
- MECHANICAL CLOSURE TEST
- ══════════════════════════════════════════════════
- The MASTER BUILD must pass a virtual REASSEMBLY test.
- Imagine every exploded component moving along its shown assembly vector.
- Every part must terminate at its exact canonical assembled location.
- EXPLODED COMPONENT
- → FOLLOWS A VALID ASSEMBLY PATH
- → CONNECTOR AXES ALIGN
- → MATING INTERFACES ENGAGE
- → NO COLLISION BLOCKS ASSEMBLY
- → FINAL ORIENTATION MATCHES HERO BUILD
- This applies equally to:
- - body
- - armor
- - tools
- - cranial systems
- - facial components
- - nested components
- - mandibles
- - jaws
- - visors
- - shells
- If this sequence fails for any major subassembly, redesign the connection before rendering.
- ══════════════════════════════════════════════════
- MASTER-FIRST BODY CONSTRUCTION
- ══════════════════════════════════════════════════
- Build in this order:
- 1. SOURCE TOPOLOGY GRAPH
- 2. PROPORTION SYSTEM
- 3. INTERNAL TORSO OR CENTRAL BODY
- 4. PELVIS / BODY JUNCTION OR NONHUMANOID EQUIVALENT
- 5. LIMB / APPENDAGE CHAINS
- 6. DETACHED OR FLOATING SUBASSEMBLIES
- 7. JOINTS
- 8. HAND / CLAW / MANIPULATOR SYSTEM
- 9. FOOT / SUPPORT SYSTEM
- 10. HEAD / CRANIAL TOPOLOGY
- 11. FACE-IDENTITY SYSTEM TYPE
- 12. HEAD / FACE CONNECTIONS
- 13. ARMOR MOUNTS
- 14. ARMOR
- 15. TOOL / WEAPON
- 16. CHARACTER-SPECIFIC ACCESSORIES
- 17. DECORATIVE DETAIL
- Do not build a generic humanoid skeleton first and then attempt to decorate it into the supplied character.
- Do not build a standard head core + Kanohi first unless that architecture is actually selected.
- ══════════════════════════════════════════════════
- NONHUMANOID + UNUSUAL BODY ARCHITECTURES
- ══════════════════════════════════════════════════
- The generator is explicitly authorized to build forms including:
- - quadrupeds
- - digitigrade bipeds
- - centaur-like bodies
- - serpentine bodies
- - tailed bodies
- - winged bodies
- - asymmetric bodies
- - single-limb or missing-limb characters
- - multi-limbed characters
- - floating appendages
- - detached hands
- - unusual shoulder systems
- - shoulderless characters
- - long-necked forms
- - no-neck forms
- - large-headed forms
- - small-bodied forms
- - hunched creatures
- - broad low-slung bodies
- - spider-like forms
- - avian forms
- - aquatic forms
- - mechanical beast anatomy
- - modular cluster bodies
- - character-specific hybrid anatomy
- Do not treat standard Toa anatomy as mandatory.
- BIONICLE compatibility is a CONSTRUCTION LANGUAGE, not a requirement to use one fixed humanoid body plan.
- ══════════════════════════════════════════════════
- ARMOR SYSTEM
- ══════════════════════════════════════════════════
- Every armor shell must possess:
- ARMOR PIECE
- → MOUNTING FEATURE
- → BODY-SIDE MOUNT
- → CLEAR OR IMPLIED CONNECTION
- Armor must respect:
- - joint movement
- - assembly access
- - neighboring part clearance
- - source anatomy
- - era language
- - intended asymmetry
- Do not use floating shells unless the character literally has floating armor as a defined canonical feature.
- ══════════════════════════════════════════════════
- WEAPON + TOOL SYSTEM
- ══════════════════════════════════════════════════
- Create one principal tool / weapon unless the reference or user specifies otherwise.
- Define:
- - handle
- - grip width
- - grip axis
- - hand compatibility
- - structural spine
- - functional end
- - attachment points
- - storage logic if relevant
- The hero pose, exploded inventory, packaging, and booklet must all show the SAME weapon.
- No alternate weapon redesigns between views.
- ══════════════════════════════════════════════════
- COLOR + MATERIAL SYSTEM
- ══════════════════════════════════════════════════
- Translate source colors into a controlled part-distribution system:
- PRIMARY STRUCTURAL COLOR
- SECONDARY COLOR
- ACCENT COLOR
- OPTIONAL TRANSLUCENT / ENERGY COLOR
- Preserve identity-significant markings through:
- - molded geometry
- - printed / painted accents
- - repeated color blocking
- - facial grooves
- - armor placement
- - symbols
- Color assignment must remain constant across:
- - hero
- - head / face proof
- - exploded view
- - instructions
- - packaging art / product image
- ══════════════════════════════════════════════════
- POSE + ARTICULATION VALIDATION
- ══════════════════════════════════════════════════
- The assembled hero pose must be reachable by the actual build.
- Trace force and articulation through the character's true topology rather than a generic human skeleton.
- For conventional bipedal regions, evaluate as applicable:
- FOOT
- → ANKLE
- → SHIN
- → KNEE
- → THIGH
- → HIP
- → BODY CORE
- For upper limbs, if present:
- HAND
- → WRIST
- → FOREARM
- → ELBOW
- → UPPER LIMB
- → SHOULDER / BODY INTERFACE
- For unusual anatomy, build an equivalent chain specific to that character.
- For floating anatomy:
- - do not invent a hidden physical chain
- - validate the floating component's own internal articulation
- - preserve its established spatial range
- ══════════════════════════════════════════════════
- MANDATORY ASSEMBLED HERO VIEW
- ══════════════════════════════════════════════════
- The assembled hero is the PRIMARY visual subject.
- Requirements:
- - full character visible
- - full canonical silhouette visible
- - all identity-critical anatomy visible
- - canonical head / face system fully represented
- - principal tool visible
- - readable joints
- - readable armor layering
- - clear character-specific proportions
- - pose consistent with mechanical articulation
- - no cropped feet / tail / wings / floating hands / key appendages unless composition absolutely demands it
- This view establishes the canonical appearance that every supporting representation must match.
- ══════════════════════════════════════════════════
- MANDATORY FULL EXPLODED PARTS VIEW
- ══════════════════════════════════════════════════
- The default board MUST include a FULL EXPLODED VIEW of the character.
- This is not a decorative explosion.
- It is an assembly-faithful representation of the complete physical build.
- The exploded view must show the character broken into logical buildable components and subassemblies while preserving one-to-one correspondence with the hero build.
- Required properties:
- - same exact torso
- - same exact cranial architecture
- - same exact face-identity system
- - same exact limbs / appendages
- - same exact armor
- - same exact tool
- - same exact colors
- - same exact asymmetry
- - same exact connector types
- - same exact counts
- For complex builds, use HIERARCHICAL EXPLOSION:
- WHOLE FIGURE
- → MAJOR SUBASSEMBLIES
- → SELECTED CRITICAL SUBASSEMBLIES FURTHER EXPLODED
- Every major structural region must be accounted for.
- ══════════════════════════════════════════════════
- EXPLODED-VIEW CONNECTOR VISIBILITY
- ══════════════════════════════════════════════════
- At important mating points, visibly reveal enough geometry to understand the connection.
- Where practical, show:
- - ball entering socket
- - axle aligned to axle hole
- - pin aligned to pin hole
- - clip aligned to bar
- - hinge aligned to hinge mate
- - cranial shell aligned to head mount
- - removable face component aligned to cranial interface
- - nested internal component aligned to housing
- - jaw aligned to hinge
- - armor mount aligned to body attachment point
- - tool handle aligned to hand grip
- Exploded parts should be separated along physically meaningful assembly axes.
- Do not scatter them radially merely for drama.
- Do not rotate every component into a random beauty angle.
- A viewer should be able to infer how the parts collapse into the assembled figure.
- ══════════════════════════════════════════════════
- EXPLODED-ASSEMBLY BIJECTION
- ══════════════════════════════════════════════════
- Use a strict one-to-one mapping:
- ONE HERO COMPONENT
- ↔
- ONE EXPLODED COMPONENT
- ↔
- ONE INSTRUCTION COMPONENT
- ↔
- ONE PACKAGED INVENTORY COMPONENT
- No duplicated armor.
- No invented spare face component.
- No mystery cranial shell.
- No alternate torso.
- No extra weapon.
- No hidden mask unless the selected head architecture actually uses one.
- If a part exists in the exploded view, it must have a valid destination in the assembled build.
- If a part exists on the assembled build, it must be accounted for in the exploded construction at an appropriate level.
- ══════════════════════════════════════════════════
- MANDATORY INSTRUCTION-BOOKLET PAGE
- ══════════════════════════════════════════════════
- Always include a readable BIONICLE-style instruction-booklet page or inset panel.
- It must depict TRUE assembly from the canonical build.
- Choose one or more meaningful steps such as:
- - torso-core assembly
- - unusual anatomy subassembly
- - head / facial-system assembly
- - removable face-component attachment
- - integrated shell attachment
- - nested identity-component insertion
- - jaw / mandible assembly
- - leg / wing / tail chain
- - floating-hand subassembly
- - tool assembly
- - armor attachment
- - final major-subassembly connection
- The booklet must not invent a simplified alternate build.
- Use clean visual step logic:
- STEP N
- → ADD SPECIFIC PART / SUBASSEMBLY
- → SHOW DIRECTION
- → SHOW RESULT
- Favor graphic assembly communication over dense prose.
- The anatomy-defining or head-system-defining connection should receive priority when unusual.
- ══════════════════════════════════════════════════
- INSTRUCTION TRUTH TEST
- ══════════════════════════════════════════════════
- Every shown instruction step must satisfy:
- BEFORE STATE
- +
- ACTUAL PART / SUBASSEMBLY
- +
- VALID ASSEMBLY MOTION
- =
- AFTER STATE FOUND IN MASTER BUILD
- Reject any step where:
- - the part shape changes
- - the connector type changes
- - a hole appears only in the booklet
- - a peg disappears after insertion
- - impossible collision occurs
- - facial architecture changes categories
- - the resulting subassembly does not match the hero
- ══════════════════════════════════════════════════
- MANDATORY PACKAGING
- ══════════════════════════════════════════════════
- Always include character-specific BIONICLE retail packaging unless the user explicitly requests no packaging.
- Packaging should feel appropriate to the chosen BIONICLE era or to a deliberately coherent fictional continuation of that product language.
- It must contain or depict the SAME product identity:
- - same character
- - same head / face architecture
- - same physically separate cranial / facial parts
- - same weapon
- - same palette
- - same name
- - same role / elemental cues
- - same proportions
- - same anatomy
- Do NOT insert a bonus Kanohi into the package merely because BIONICLE often uses masks.
- The package contains only the actual canonical product inventory.
- If transparent package contents are visible, the inventory must correspond to the master build.
- If the package uses box / canister art rather than visible parts, the artwork must still accurately depict the canonical figure.
- ══════════════════════════════════════════════════
- BIONICLE × CHARACTER-SPECIFIC BACKGROUND
- ══════════════════════════════════════════════════
- The board must include a background/presentation environment that feels like:
- BIONICLE WORLD LANGUAGE
- ×
- THIS SPECIFIC CHARACTER'S IDENTITY
- Do not default to an empty neutral gradient unless the user requests minimalism.
- Derive the background from:
- - character element
- - power
- - role
- - source environment
- - profession
- - motifs
- - palette
- - temperament
- - faction
- - narrative function
- - head / face identity motifs when especially significant
- The environment should support the product board, not swallow it.
- ══════════════════════════════════════════════════
- REPRESENTATION PROPAGATION CONTRACT
- ══════════════════════════════════════════════════
- Every identity-critical property must propagate through ALL representations.
- SOURCE TOPOLOGY
- → HERO BUILD
- → HEAD / FACE SYSTEM PROOF
- → EXPLODED BUILD
- → INSTRUCTIONS
- → PACKAGING
- → BACKGROUND MOTIFS
- If the source has:
- - no arms
- then no representation may invent arms.
- If the source has:
- - four legs
- then the hero, exploded view, booklet, and packaging must preserve four legs.
- If the source has:
- - one oversized hand
- then the size asymmetry must survive every relevant view.
- If the source has:
- - floating hands
- then:
- - hero shows floating hands
- - exploded view shows those hand subassemblies separately from the torso
- - instructions build each hand independently rather than attaching arms
- - packaging depicts the same disconnected topology
- - no hidden limb roots appear
- If the selected head architecture is:
- - integrated
- then no view may invent a removable mask.
- If the selected head architecture uses:
- - a nested symbiotic component
- then hero, exploded view, instructions, and packaging must preserve that nested relationship.
- If the selected head architecture is:
- - fully original
- then all representations must preserve that original system rather than reverting to a familiar Kanohi-like face.
- ══════════════════════════════════════════════════
- STATE VS IDENTITY
- ══════════════════════════════════════════════════
- Distinguish:
- IDENTITY INVARIANTS
- Properties that never change between views.
- STATE VARIABLES
- Properties that may legitimately change.
- Identity invariants include:
- - anatomy
- - inventory
- - proportions
- - colors
- - markings
- - connector geometry
- - head / face architecture
- - facial component identity
- - tool identity
- Allowed state changes may include:
- - removable component attached / removed
- - nested component inserted / removed if canonically possible
- - jaw open / closed
- - visor open / closed
- - tool held / packaged
- - armor assembled / separated
- - limb pose
- - package containment
- - instruction partial assembly
- Never treat a state change as permission to redesign the character.
- ══════════════════════════════════════════════════
- PRODUCT INVENTORY LEDGER
- ══════════════════════════════════════════════════
- Before rendering, define one inventory.
- Include:
- CHARACTER BUILD PARTS
- HEAD / FACE COMPONENTS THAT ARE PHYSICALLY SEPARATE
- PRIMARY TOOL
- CHARACTER-SPECIFIC ACCESSORIES
- LEGITIMATE SPARES, IF ANY
- INSTRUCTION BOOKLET
- PACKAGING
- If a spare is included, explicitly treat it as a spare and keep it distinct from the active build inventory.
- Do not duplicate major identity parts merely to make packaging look fuller.
- ══════════════════════════════════════════════════
- PRESENTATION ARCHITECTURE
- ══════════════════════════════════════════════════
- Default visual hierarchy:
- A. HERO ZONE
- largest area
- assembled full character
- B. EXPLODED BUILD ZONE
- second-largest
- full or hierarchical exploded assembly
- C. HEAD / FACE SYSTEM PROOF ZONE
- clear structural close-up appropriate to selected architecture
- D. INSTRUCTION ZONE
- one readable booklet page / assembly panel
- E. PACKAGING ZONE
- one product package presentation
- F. CHARACTER-WORLD BACKGROUND
- unifies the entire composition
- Recommended attention distribution:
- 45–55%
- assembled hero
- 20–25%
- exploded build
- 8–12%
- head / face proof
- 8–12%
- instruction page
- 8–12%
- packaging
- background supports all zones without competing with them
- Do not sacrifice legibility to exact percentages.
- ══════════════════════════════════════════════════
- TEXT RULES
- ══════════════════════════════════════════════════
- Visible text should be limited and purposeful.
- Prefer:
- - character name
- - role / element
- - head / face system name if useful
- - mask name ONLY when the selected architecture actually uses a named mask
- - small instruction numbers
- - believable packaging title treatment
- Avoid:
- - paragraphs of lore
- - internal prompt terminology
- - placeholders
- - labels like "CANONICAL BUILD"
- - excessive tiny technical prose
- ══════════════════════════════════════════════════
- FAILURE PREVENTION — KANOHI FORCING
- ══════════════════════════════════════════════════
- FAILURE:
- Every character receives a removable Kanohi-like mask.
- FIX:
- Head / face architecture is selected only after evaluating source facial topology and species/build requirements.
- FAILURE:
- A non-mask species suddenly receives a mask in supporting views.
- FIX:
- The selected head / face type becomes locked and propagates across all views.
- FAILURE:
- Packaging contains a mask that does not exist on the hero.
- FIX:
- Packaging inventory derives from the product inventory ledger, not from generic BIONICLE assumptions.
- FAILURE:
- Integrated face system is shown with a fake unmasked state.
- FIX:
- Use structural cranial proof rather than inventing a removable state.
- ══════════════════════════════════════════════════
- FAILURE PREVENTION — HEAD / FACE SYSTEM DRIFT
- ══════════════════════════════════════════════════
- FACIAL CATEGORY DRIFT
- Hero uses one system; exploded view uses another.
- Prevent by:
- - universal head / face system lock
- - type-specific state rules
- COMPONENT DRIFT
- Separate facial component changes geometry.
- Prevent by:
- - one-to-one component correspondence
- CRANIAL NORMALIZATION
- Unique creature head becomes humanoid in packaging or instructions.
- Prevent by:
- - source topology lock
- - species-specific cranial architecture
- - representation propagation
- ORIGINAL-SYSTEM COLLAPSE
- Novel facial design is replaced by a familiar Kanohi-like shape later.
- Prevent by:
- - once TYPE I is selected, preserve it as canonical
- ══════════════════════════════════════════════════
- FAILURE PREVENTION — REQUIRED DELIVERABLE OMISSION
- ══════════════════════════════════════════════════
- FAILURE:
- Model outputs only the hero.
- FIX:
- The default output contract explicitly requires all six deliverables.
- FAILURE:
- Head / face proof omitted.
- FIX:
- Head / face identity proof is mandatory.
- FAILURE:
- Exploded view omitted.
- FIX:
- Full exploded construction is mandatory.
- FAILURE:
- Instruction page omitted.
- FIX:
- Instruction booklet page is mandatory.
- FAILURE:
- Packaging omitted.
- FIX:
- Packaging is mandatory unless explicitly disabled.
- FAILURE:
- Character-specific background becomes generic.
- FIX:
- Derive environmental language from the source character's role, element, motifs, and identity.
- ══════════════════════════════════════════════════
- FAILURE PREVENTION — EXPLODED VIEW
- ══════════════════════════════════════════════════
- EXPLODED DECORATION FAILURE
- Parts merely float around the hero.
- Prevent by:
- - using actual assembly paths
- - revealing mating interfaces
- - preserving one-to-one correspondence
- - hierarchical decomposition
- - mechanical closure test
- CONNECTOR MISMATCH
- Parts cannot physically join.
- Prevent by:
- - connection-grammar ledger
- - paired mating interfaces
- - axis alignment
- - collision check
- - scale compatibility
- MYSTERY PARTS
- Exploded view contains pieces absent from hero.
- Prevent by:
- - product inventory ledger
- - hero ↔ exploded bijection
- MISSING INTERNAL STRUCTURE
- Armor or facial shells float in exploded view with no body-side mounts.
- Prevent by:
- - internal build designed before armor
- - cranial architecture defined before facial surface treatment
- - exploded view reveals mounting system
- ══════════════════════════════════════════════════
- FAILURE PREVENTION — UNIQUE ANATOMY
- ══════════════════════════════════════════════════
- HUMANIZATION FAILURE
- Unusual source becomes a standard Toa.
- Prevent by:
- - topology graph
- - count locks
- - absence constraints
- - anatomy preservation hierarchy
- LIMB INVENTION
- Model invents arms / legs / shoulders to hold equipment.
- Prevent by:
- - function transfer through existing anatomy
- - attachment or telekinetic handling consistent with canonical source
- - explicit prohibition on adding absent structures
- UNUSUAL FEATURE AS DECORATION
- Tail / wing / extra limb appears only as armor ornament.
- Prevent by:
- - treat identity-critical appendages as structural body nodes
- - include their joints and subassemblies
- - propagate them into exploded, instructions, and packaging
- FLOATING COMPONENT CONNECTED BY ACCIDENT
- Detached anatomy gains rods, wires, or limb roots.
- Prevent by:
- - diegetic noncontact system
- - separate subassembly construction
- - spatial relationship preserved without physical connector
- NEW PART ABUSE
- Entire anatomy becomes one custom sculpture.
- Prevent by:
- - use new molded pieces only after direct, recombined, and subassembly strategies are insufficient
- - require compatible connectors and inventory consistency
- ══════════════════════════════════════════════════
- FAILURE PREVENTION — INSTRUCTIONS + PACKAGING
- ══════════════════════════════════════════════════
- INSTRUCTION FICTION
- Booklet depicts a build that cannot make the hero.
- Prevent by:
- - before / add / after truth test
- - use canonical inventory
- - preserve connector geometry
- PACKAGING REDESIGN
- Package art depicts a different character.
- Prevent by:
- - use canonical hero proportions, anatomy, head system, tool, and palette
- - do not simplify unusual topology into a generic humanoid
- PACKAGING INVENTORY DRIFT
- Visible contents include duplicate masks / weapons / limbs / facial components.
- Prevent by:
- - product inventory ledger
- - explicit spare designation only when intended
- ══════════════════════════════════════════════════
- PHYSICAL TOY CREDIBILITY
- ══════════════════════════════════════════════════
- Preserve:
- - material thickness
- - socket depth
- - pin / axle alignment
- - joint clearance
- - armor clearance
- - cranial assembly access
- - facial-component clearance
- - articulation access
- - stable load paths
- - grip compatibility
- - plausible center of mass
- - rigid-part behavior
- - realistic subassembly segmentation
- Avoid:
- - intersecting rigid parts
- - rubber-like hard pieces
- - armor penetrating joints
- - nonmatching connection scales
- - fused tool / hand
- - impossible facial mounting
- - parts held together only by visual contact
- Small original molded pieces are acceptable when necessary, but they must function as real members of the build system.
- ══════════════════════════════════════════════════
- ORIGINALITY CONTROL
- ══════════════════════════════════════════════════
- Create an original BIONICLE-style character derived from the supplied reference.
- Authenticity should come from:
- - construction logic
- - era language
- - biomechanical layering
- - head / face system logic
- - product design conventions
- not from copying a famous canonical character and recoloring it.
- Original cranial systems, facial components, tools, subassemblies, and anatomy solutions are encouraged.
- Established BIONICLE designs may inspire the RANGE of valid solutions without becoming mandatory templates.
- ══════════════════════════════════════════════════
- FINAL GENERATION DECISION
- ══════════════════════════════════════════════════
- Before rendering, silently commit to ONE answer for:
- - source identity anchors
- - topology graph
- - count locks
- - absence constraints
- - BIONICLE role
- - power domain
- - build era
- - body architecture
- - unusual anatomy solution
- - torso core
- - appendage chains
- - detached subassemblies
- - cranial topology
- - head / face system type
- - facial component inventory
- - state logic
- - connection grammar
- - armor
- - palette
- - weapon / tool
- - articulation
- - product inventory
- - hero pose
- - exploded assembly
- - instruction step
- - packaging design
- - character-specific environment
- - presentation hierarchy
- Do not expose unresolved alternate concepts.
- ══════════════════════════════════════════════════
- FINAL ADVERSARIAL VALIDATION
- ══════════════════════════════════════════════════
- Before producing the final image, attempt to falsify the design.
- ASK:
- IDENTITY
- - If the colors were removed, would the topology and silhouette still reflect the source?
- - Were unusual anatomical and facial features actually preserved?
- TOPOLOGY
- - Are node counts correct?
- - Were forbidden structures invented?
- - Did any floating component accidentally become attached?
- HEAD / FACE ARCHITECTURE
- - Was the head / face system selected because it fits this character?
- - Was a Kanohi forced without justification?
- - Does the selected system remain the same in every representation?
- - If removable, does the component truly attach?
- - If integrated, was a fake removable state avoided?
- - If nested, is the housing/component relationship preserved?
- - If original, was it allowed to remain original?
- BUILDABILITY
- - Can every major connected part explain how it is attached?
- - Are all connector pairs mechanically compatible?
- - Are connector axes aligned?
- - Do rigid parts intersect?
- - Is articulation reachable?
- EXPLODED VIEW
- - Can every exploded component collapse into the hero?
- - Does every major hero component appear in the exploded structure?
- - Are assembly vectors meaningful?
- - Do mating interfaces correspond?
- INSTRUCTIONS
- - Does the illustrated step actually produce part of the master build?
- - Are no imaginary holes or connectors introduced?
- - Does the head / face assembly remain truthful?
- PACKAGING
- - Is the same character shown?
- - Does inventory remain truthful?
- - Is unusual anatomy preserved?
- - Is the actual head / face system preserved?
- - Were no generic masks added?
- BACKGROUND
- - Does the environment feel specific to this character?
- - Does it still feel BIONICLE-compatible?
- - Does it support rather than obscure the board?
- DELIVERABLE COMPLETENESS
- - assembled hero present?
- - head / face system proof present?
- - full exploded build present?
- - instruction page present?
- - packaging present?
- - BIONICLE × character-specific background present?
- If any required answer is NO, correct the underlying design before rendering.
- ══════════════════════════════════════════════════
- FINAL OUTPUT CONTRACT
- ══════════════════════════════════════════════════
- Generate ONE finished wide-format premium BIONICLE character/product-development image.
- By default it MUST contain:
- - ONE dominant full-body assembled hero
- - ONE clearly legible canonical head / face identity system proof
- - ONE mechanically coherent full exploded parts view
- - ONE truthful instruction-booklet page or assembly panel
- - ONE character-specific BIONICLE retail package
- - ONE BIONICLE × character-specific environmental background
- - ONE consistent build and inventory across all representations
- The facial architecture must be the system that best serves THIS character.
- A removable Kanohi-like mask is permitted when appropriate.
- It is NOT mandatory.
- Integrated faceplates, species-specific cranial shells, multi-part facial assemblies, nested identity components, exposed mechanical faces, creature-style heads, modular cranial armor, and entirely original BIONICLE-compatible facial systems are equally valid when they better preserve the character.
- The finished result should immediately communicate:
- THIS SPECIFIC CHARACTER
- → TRANSLATED WITHOUT ANATOMICAL OR FACIAL NORMALIZATION
- → GIVEN THE HEAD / FACE ARCHITECTURE THAT ACTUALLY FITS
- → ENGINEERED AS A REAL BIONICLE-COMPATIBLE BUILD
- → PROVEN THROUGH MECHANICALLY CONSISTENT PRODUCT REPRESENTATIONS
- → PRESENTED AS A COMPLETE CHARACTER-SPECIFIC BIONICLE SET
Advertisement
Add Comment
Please, Sign In to add comment