Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- UNIVERSAL CATAPULT CREW + CASTLE ASSAULT IMAGE GENERATOR
- VERSION 1.0 — MULTI-REFERENCE CHARACTER CASTING + SIEGE-ENGINE CREW LOGIC + CASTLE TARGET SYSTEM + CUSTOM PROJECTILE WARFARE
- ══════════════════════════════════════════════════
- CORE PURPOSE
- ══════════════════════════════════════════════════
- Create ONE finished image depicting one or more CATAPULT CREWS composed from supplied character reference sheets actively attacking a customizable CASTLE or fortified structure with customizable objects launched from the catapults.
- The generator must be capable of working from:
- - one character reference sheet
- - several character reference sheets
- - repeated use of one referenced character
- - several distinct referenced characters
- - one or more castle/environment references
- - no castle reference at all
- - minimal user customization
- - extensive user customization
- - conventional siege ammunition
- - absurd, comedic, fantastical, symbolic, oversized, improvised, or user-defined projectiles
- The image should read as a coherent siege scene rather than as unrelated characters standing beside siege equipment.
- The governing process is:
- USER CUSTOMIZATION
- → REFERENCE AUTHORITY ASSIGNMENT
- → CHARACTER CAST LEDGER
- → CASTLE MASTER
- → CATAPULT MASTER
- → CREW ASSIGNMENT
- → PROJECTILE SYSTEM
- → SIEGE ACTION STATE
- → SPATIAL BATTLE MAP
- → CAMERA + SCALE
- → EFFECTS + IMPACT CONTINUITY
- → IDENTITY VALIDATION
- → FINAL IMAGE
- The references are source material for ONE unified scene.
- Do not make a reference sheet, character lineup, design board, collage, split-screen presentation, or disconnected collection of mini-scenes unless explicitly requested.
- Generate one complete scene.
- ══════════════════════════════════════════════════
- CUSTOMIZABLE INPUTS
- ══════════════════════════════════════════════════
- Accept any natural-language combination of the following fields.
- CHARACTER REFERENCES:
- [ATTACH ONE OR MORE CHARACTER REFERENCE SHEETS / IMAGES]
- CHARACTER USAGE:
- [DEFAULT / SURPRISE ME / specify which characters appear, how many times each appears, or who belongs to which crew]
- NUMBER OF CATAPULTS:
- [DEFAULT / SURPRISE ME / exact number]
- CREW SIZE:
- [DEFAULT / SURPRISE ME / exact number per catapult / different sizes by crew]
- CREW ROLES:
- [DEFAULT / SURPRISE ME / specify operator, loader, spotter, commander, hauler, defender, etc.]
- CATAPULT TYPE:
- [DEFAULT / SURPRISE ME / traction trebuchet / counterweight trebuchet / mangonel / onager / fantasy catapult / improvised siege engine / other]
- CASTLE:
- [DEFAULT / SURPRISE ME / description]
- CASTLE REFERENCE:
- [OPTIONAL ATTACHED IMAGE OR IMAGES]
- CASTLE CONDITION:
- [DEFAULT intact-but-under-attack / pristine / damaged / heavily besieged / breached / burning / fantastical / other]
- CASTLE DEFENDERS:
- [NONE by default / SURPRISE ME / specify]
- PROJECTILE:
- [Watermelons]
- PROJECTILE VARIATION:
- [SAME OBJECT FROM ALL CATAPULTS / DIFFERENT OBJECT PER CATAPULT / SURPRISE ME]
- SIEGE MOMENT:
- [DEFAULT mixed active assault / loading / tensioning / release / projectile in flight / impact / aftermath / coordinated volley / other]
- TONE:
- [DEFAULT cinematic adventure / serious / heroic / comedic / absurd / dark / chaotic / whimsical / epic / other]
- SETTING:
- [DEFAULT medieval-inspired battlefield / user-defined]
- TIME + WEATHER:
- [DEFAULT / SURPRISE ME / user-defined]
- VISUAL STYLE:
- [DEFAULT polished cinematic illustration / photorealistic / painterly / animation-inspired / miniature diorama / graphic novel / other]
- CAMERA:
- [DEFAULT / user-defined]
- ASPECT RATIO:
- [DEFAULT 16:9 / user-defined]
- ADDITIONAL INSTRUCTIONS:
- [OPTIONAL NATURAL-LANGUAGE OVERRIDES]
- Any field left at DEFAULT or blank must be completed intelligently.
- Do not print the word DEFAULT into the image.
- The generator must still produce a complete scene if the user provides only character references and nothing else.
- ══════════════════════════════════════════════════
- REFERENCE AUTHORITY SYSTEM
- ══════════════════════════════════════════════════
- Assign every supplied reference an explicit role before constructing the scene.
- CHARACTER REFERENCES are the PRIMARY IDENTITY AUTHORITY for the characters derived from them.
- Preserve, as applicable:
- - species
- - body type
- - anatomy
- - topology
- - proportions
- - head shape
- - face
- - fur, skin, scales, feathers, shell, or equivalent surface
- - eye design
- - hair
- - ears
- - horns
- - tails
- - wings
- - unusual limb arrangements
- - detached or floating anatomy
- - markings
- - palette
- - clothing
- - armor
- - signature accessories
- - symbols
- - distinctive asymmetry
- - age presentation
- - sex presentation
- - recognizable personality cues
- Do not normalize unusual characters into generic humans.
- Do not replace species-specific anatomy merely to make operating the catapult easier.
- Instead, adapt crew behavior, stance, grip, controls, equipment position, and catapult interface around the actual anatomy of the referenced character.
- CASTLE REFERENCES control only the castle/environment dimensions they visibly establish or that the user assigns to them.
- Possible castle-reference authority includes:
- - architectural identity
- - silhouette
- - towers
- - walls
- - gates
- - battlements
- - materials
- - color
- - terrain
- - surrounding city
- - landscape
- - architectural era
- - decorative motifs
- - damage state if intentionally shown
- - overall atmospheric identity
- Do not let a castle reference redesign the attacking characters.
- Do not let a character reference redesign the castle unless the user explicitly requests a character-themed fortress.
- STYLE REFERENCES, when supplied as such, control style rather than identity.
- POSE REFERENCES control pose/action only.
- The same image may hold more than one role only when that interpretation is clearly intended.
- ══════════════════════════════════════════════════
- CHARACTER CAST LEDGER
- ══════════════════════════════════════════════════
- Before staging the battle, establish a CAST LEDGER.
- For every distinct referenced character selected for the image, determine:
- - canonical identity
- - source reference
- - number of diegetic instances
- - crew assignment
- - role
- - scale relative to other characters
- - required anatomy
- - clothing and equipment
- - personality expression
- - any user-requested modifications
- Do not design each appearance independently.
- Every instance derived from the same character reference must remain recognizably that character.
- If the user requests the same character several times, those are intentional duplicate diegetic instances of the same character design.
- If the user supplies several reference sheets, do not accidentally merge their features into one hybrid unless the user explicitly requests fusion.
- Maintain strict reference-to-character correspondence:
- REFERENCE A
- → CHARACTER A
- REFERENCE B
- → CHARACTER B
- REFERENCE C
- → CHARACTER C
- and so on.
- No facial swapping.
- No costume swapping.
- No species blending.
- No accidental color exchange.
- No identity drift merely because several characters occupy the same crew.
- ══════════════════════════════════════════════════
- MULTI-REFERENCE CASTING LOGIC
- ══════════════════════════════════════════════════
- Use the supplied reference cast intelligently.
- When CHARACTER USAGE is unspecified:
- - include enough referenced characters to make the siege feel populated and purposeful
- - prioritize using distinct references rather than inventing unrelated generic crew
- - reuse referenced characters only when necessary for crew completeness or composition
- - do not overcrowd the scene merely to include every possible reference if the requested image cannot support them legibly
- If the number of supplied characters fits the selected crew count exactly, assign each one once by default.
- If more characters are supplied than can fit clearly:
- 1. preserve the most visually distinct characters
- 2. prioritize user-emphasized characters
- 3. adjust crew size or number of catapults when feasible
- 4. omit only when necessary for image readability
- If fewer characters are supplied than needed:
- - reuse supplied characters as additional instances when appropriate
- - or reduce crew size
- - avoid inventing prominent new characters unless necessary
- Incidental distant figures may be generic only when they are visually minor and do not compete with the reference cast.
- The referenced characters should remain the principal attackers.
- ══════════════════════════════════════════════════
- CREW ROLE ENGINE
- ══════════════════════════════════════════════════
- Every visible attacker should have a believable battlefield purpose.
- Possible roles include:
- CATAPULT COMMANDER
- Signals timing, points toward the target, coordinates the crew, watches trajectory, or gives orders.
- AIMER / GUNNER
- Adjusts orientation, elevation, release angle, sling placement, or mechanical aiming components where appropriate to the siege engine type.
- LOADER
- Positions the projectile into the sling, cup, basket, or launch cradle.
- TENSION / WINCH OPERATOR
- Works ropes, capstans, winches, counterweight controls, torsion systems, or drawing mechanisms.
- ROPE CREW
- Pulls traction ropes or handles other force-generating systems when appropriate.
- AMMUNITION HANDLER
- Carries, rolls, drags, lifts, or prepares incoming projectiles.
- SPOTTER
- Observes the castle and estimates where the shot lands.
- DEFENDER
- Protects the machine with shield, weapon, magic, or other user-compatible means if battlefield defenders are desired.
- SUPPORT CREW
- Brings ammunition, tools, replacement rope, water, repairs, or other siege necessities.
- Roles should be adapted to the selected catapult.
- Do not show characters pretending to operate controls that do not exist.
- Do not make every crew member adopt the same generic pushing pose.
- The image should communicate distributed teamwork.
- ══════════════════════════════════════════════════
- ANATOMY-TO-SIEGE INTERFACE
- ══════════════════════════════════════════════════
- Build every character's interaction with the siege engine around their actual anatomy.
- For characters with ordinary arms and hands:
- - hands should wrap around real ropes, handles, cranks, levers, frames, tools, or ammunition
- - grips must correspond to physical contact points
- - arm direction should align with the force being applied
- For characters with paws, claws, talons, hooves, tentacles, floating hands, unusual limb counts, wings, tails, or other anatomy:
- translate the operator interface to something they can plausibly use.
- Examples of compatible adaptation include:
- - larger handholds
- - lower cranks
- - rope loops
- - harnesses
- - widened platforms
- - tail-assisted bracing
- - tentacle-compatible rope bundles
- - floating-hand operation
- - species-scaled ladders or footrests
- Do not generate human arms merely because the mechanism expects hands.
- Do not give extra limbs unless canon or user instruction allows them.
- Do not fuse a character into the catapult.
- CHARACTER
- ↔ CONTACT POINT
- ↔ FORCE DIRECTION
- ↔ MACHINE RESPONSE
- must remain readable.
- ══════════════════════════════════════════════════
- CATAPULT MASTER SYSTEM
- ══════════════════════════════════════════════════
- Construct each siege engine as a believable complete mechanism before posing the crew around it.
- The selected siege-engine type determines its anatomy.
- Possible structural elements may include:
- - base frame
- - wheels or sled runners
- - throwing arm
- - axle
- - sling or launch cup
- - release hook
- - counterweight
- - torsion bundle
- - traction ropes
- - winch
- - ratchet
- - capstan
- - bracing
- - stabilizers
- - rope rigging
- - loading track
- - ammunition cradle
- - repair tools
- Use only features appropriate to the selected machine.
- Do not create a random hybrid of trebuchet, ballista, and catapult unless a fantastical hybrid is specifically requested.
- The mechanism should remain visually legible enough that the action can be understood.
- When multiple catapults are present, they may share the same overall design family while showing modest practical variation from wear, scale, crew adaptation, decoration, or faction styling.
- Do not accidentally produce a different siege-engine category for every machine unless requested.
- ══════════════════════════════════════════════════
- CHARACTER-INFLUENCED SIEGE DESIGN
- ══════════════════════════════════════════════════
- When appropriate, subtly adapt each catapult to its crew without turning it into a novelty sculpture.
- Character influence may affect:
- - paint
- - banners
- - shield emblems
- - carved motifs
- - rope colors
- - trim
- - armor plates
- - crew-scale controls
- - seats or platforms
- - ammunition racks
- - faction markings
- - practical accommodations for body shape or anatomy
- Identity influence should feel functional and integrated.
- Avoid simply painting the whole catapult in the character's colors and calling it customized.
- Do not reshape the machine so aggressively that it ceases to function as the chosen siege engine.
- ══════════════════════════════════════════════════
- CASTLE MASTER
- ══════════════════════════════════════════════════
- Establish one coherent castle or fortified target before applying siege damage.
- The castle should have stable spatial logic.
- Define:
- - overall silhouette
- - wall perimeter
- - major towers
- - gatehouse
- - battlements
- - central keep if applicable
- - visible wall faces
- - material
- - terrain relationship
- - approach route
- - defensive height
- - relevant architectural motifs
- - location of existing damage
- - location of new impact activity
- If a castle reference is attached, reconstruct these features from the reference to the extent visible.
- If several castle references depict different views of the SAME castle, treat them as complementary evidence for one canonical structure.
- Do not independently redesign the castle from angle to angle within the same image.
- If the references instead depict multiple sources of inspiration, merge only compatible architectural traits into one coherent fortress.
- ══════════════════════════════════════════════════
- CASTLE CUSTOMIZATION + REFERENCE INFLUENCE
- ══════════════════════════════════════════════════
- The castle may range from historically grounded to fantastical.
- Possible customization may include:
- - medieval stone fortress
- - gothic citadel
- - desert fortress
- - icy stronghold
- - toy castle
- - candy castle
- - futuristic fortified city
- - cartoon kingdom
- - haunted fortress
- - character-themed stronghold
- - floating castle
- - improvised fortification
- - any user-defined target
- When a reference is present, preserve the recognizable castle identity before adding siege context.
- Do not turn a supplied castle into a generic fortress simply because generic stone walls are easier.
- If the castle comes from a known visual reference, protect its distinctive silhouette and defining architectural motifs.
- ══════════════════════════════════════════════════
- BATTLEFIELD SPATIAL MAP
- ══════════════════════════════════════════════════
- Construct one stable spatial relationship:
- ATTACKING ARMY
- → CATAPULT LINE
- → OPEN TRAJECTORY SPACE
- → CASTLE DEFENSE ZONE
- → CASTLE
- The geometry should clearly communicate which direction the assault is moving.
- By default:
- - attackers occupy the foreground and middle ground
- - catapults face toward the castle
- - the castle occupies middle distance or background
- - projectile trajectories travel from attackers toward the fortress
- - defensive fire, if present, travels in the opposite direction
- Keep left/right and near/far relationships stable.
- Do not accidentally reverse a catapult so its throwing arm launches away from the castle.
- Do not point characters toward one target while the machine points elsewhere.
- Do not make projectiles appear to originate from the castle unless they are explicitly defensive.
- ══════════════════════════════════════════════════
- PROJECTILE MASTER SYSTEM
- ══════════════════════════════════════════════════
- Treat the user's launched object as a real projectile occupying a specific stage of the siege process.
- Determine:
- - what the object is
- - its physical scale
- - mass implication
- - rigidity or flexibility
- - orientation in the sling or cup
- - how crew members handle it
- - whether special loading equipment is needed
- - whether it remains intact in flight
- - whether it changes after impact
- - whether multiples exist
- - whether several catapults use the same projectile class
- The projectile must remain recognizable.
- Do not reduce unusual custom projectiles to generic rocks.
- If the user requests, for example, a recognizable everyday object, food item, vehicle, mascot, prop, treasure chest, appliance, or other absurd projectile, preserve its defining form throughout loading, launch, and impact states.
- ══════════════════════════════════════════════════
- PROJECTILE SCALE + LAUNCH FEASIBILITY
- ══════════════════════════════════════════════════
- Scale the projectile relative to the siege engine in a way that supports the intended tone.
- For grounded scenes:
- respect plausible loading scale and machine capacity.
- For fantastical or comedic scenes:
- extreme scale may be accepted, but the image should still acknowledge the physical consequence.
- An oversized projectile may require:
- - a huge custom catapult
- - several loaders
- - rollers
- - ramps
- - ropes
- - cranes
- - magical assistance
- - exaggerated fantasy engineering
- Do not depict a tiny wooden catapult casually launching an object many times larger than itself unless impossible scale is intentionally part of the joke.
- When physical realism is intentionally broken, make the violation feel deliberate rather than accidental.
- ══════════════════════════════════════════════════
- PROJECTILE STATE CONTINUITY
- ══════════════════════════════════════════════════
- When several examples of the projectile appear in the image, establish one canonical projectile design.
- LOADED PROJECTILE
- ↔ IN-FLIGHT PROJECTILE
- ↔ IMPACTED PROJECTILE
- must remain recognizably the same type of object.
- Authorized differences may include:
- - rotation
- - motion blur
- - dust
- - deformation
- - breakage after impact
- - burning after impact if applicable
- - debris generated by the collision
- Do not redesign the object in mid-flight.
- Do not make the loaded version one object and the airborne version another.
- Do not show impact damage before impact unless the projectile began damaged.
- ══════════════════════════════════════════════════
- SIEGE ACTION STATE ENGINE
- ══════════════════════════════════════════════════
- By default, create a MIXED ACTIVE ASSAULT rather than freezing every machine at the same stage.
- Across multiple catapults, useful simultaneous stages may include:
- - one being loaded
- - one under tension
- - one at the instant of release
- - one projectile already in flight
- - one recent impact visible on the castle
- This creates narrative depth while still representing one coherent battlefield moment.
- Each individual catapult must occupy ONE mechanically reachable state.
- Do not combine incompatible phases on the same machine.
- A single catapult should not simultaneously have:
- - its arm cocked
- - its arm released
- - the projectile still loaded
- - and that same projectile already halfway to the castle
- unless separate projectiles and separate temporal logic are clearly established.
- ══════════════════════════════════════════════════
- CATAPULT STATE CONTRACT
- ══════════════════════════════════════════════════
- For each machine, internally choose one state.
- LOADING STATE
- - throwing arm lowered or positioned appropriately
- - projectile being placed
- - sling/cup accessible
- - crew working near loading area
- COCKING / TENSIONING STATE
- - projectile secured
- - mechanism visibly accumulating energy
- - crew working winches, ropes, capstans, or traction system
- - throwing arm positioned according to machine type
- RELEASE STATE
- - arm moving through launch arc
- - projectile leaving sling/cup
- - crew reacting to force
- - ropes and mechanism responding coherently
- POST-RELEASE STATE
- - projectile clear of machine
- - arm completing or having completed its swing
- - crew watching trajectory or preparing reset
- RESET STATE
- - crew restoring mechanism
- - no projectile magically already present unless a new one is being loaded
- Mechanics may be stylized, but state relationships must remain understandable.
- ══════════════════════════════════════════════════
- TRAJECTORY + FLIGHT LOGIC
- ══════════════════════════════════════════════════
- Projectile paths should reinforce the siege geometry.
- Use trajectories appropriate to the weapon.
- Catapult and trebuchet projectiles generally travel in visible ballistic arcs.
- Do not treat them like straight laser beams.
- When several projectiles are airborne:
- - vary their position along related arcs
- - maintain clear origin direction
- - avoid trajectory tangles that obscure the characters
- - avoid filling the sky with unnecessary ammunition unless a massive volley is requested
- A projectile may overlap part of the scene through perspective, but the origin and destination should remain intelligible.
- Do not place the projectile so close to the camera that it hides the entire battle unless a dramatic projectile-focused shot is explicitly requested.
- ══════════════════════════════════════════════════
- IMPACT + CASTLE DAMAGE CONTINUITY
- ══════════════════════════════════════════════════
- Every major visible impact should have a readable cause.
- PROJECTILE TRAJECTORY
- → IMPACT POINT
- → MATERIAL RESPONSE
- → LOCAL DAMAGE
- → DEBRIS / DUST / EFFECT
- Castle damage should correspond to the material and projectile.
- Stone may:
- - crack
- - chip
- - shed masonry
- - create localized breaches
- - generate dust and fragments
- Wood may:
- - splinter
- - bend
- - break
- - ignite when appropriate
- Metal may:
- - dent
- - deform
- - spark if the collision justifies it
- Fantastical materials should react according to their established logic.
- Do not scatter random explosion effects over unrelated areas of the castle.
- Do not erase large sections of architecture without a corresponding destructive event.
- If the castle begins partially damaged, distinguish pre-existing damage from the currently depicted strike through placement and action cues.
- ══════════════════════════════════════════════════
- CHARACTER PERFORMANCE + PERSONALITY
- ══════════════════════════════════════════════════
- Do not merely preserve the characters physically.
- Preserve how they would plausibly participate in the siege.
- Translate personality cues from the references into:
- - expressions
- - confidence
- - fear
- - enthusiasm
- - frustration
- - command posture
- - teamwork style
- - recklessness
- - professionalism
- - smugness
- - panic
- - humor
- - determination
- A stoic character may operate with disciplined focus.
- A chaotic character may gleefully overcommit to the launch.
- A nervous character may brace for impact.
- A heroic character may command from the front.
- These are controlled extrapolations.
- Do not overwrite a clearly established character personality with generic battle rage unless requested.
- ══════════════════════════════════════════════════
- EQUIPMENT + COSTUME CONTINUITY
- ══════════════════════════════════════════════════
- Preserve reference clothing and signature gear unless the user requests an alternate outfit.
- When practical siege additions are useful, they may include:
- - gloves
- - belts
- - harnesses
- - protective helmets
- - aprons
- - shields
- - ammunition pouches
- - tools
- However, additions must not obscure or replace defining reference traits.
- Use minimal adaptation.
- A character should still be identifiable from their original sheet.
- If a referenced outfit would realistically interfere with operating the machine, adapt pose and interface first rather than redesigning the outfit without permission.
- ══════════════════════════════════════════════════
- CREW-TO-CATAPULT COUNT LOCK
- ══════════════════════════════════════════════════
- Internally inventory:
- NUMBER OF CATAPULTS
- → NUMBER OF CREWS
- → NUMBER OF CHARACTERS PER CREW
- → TOTAL CHARACTER INSTANCES
- Do not accidentally create:
- - an extra catapult
- - an unassigned duplicate crew
- - floating operators with no machine
- - one crew apparently operating two distant machines simultaneously
- - missing characters after the user specified exact counts
- If one character belongs to a specific catapult, preserve that assignment.
- When several machines overlap in perspective, keep the crew grouping readable through proximity, pose direction, and machine contact.
- ══════════════════════════════════════════════════
- CASTLE DEFENDERS
- ══════════════════════════════════════════════════
- Castle defenders are absent by default so the attacking reference cast remains the focus.
- If defenders are requested or SURPRISE ME selects them, keep them visually subordinate unless the user specifically wants a battle between two equally important factions.
- Possible defenders include:
- - archers
- - guards
- - siege crews
- - magical defenders
- - creatures
- - user-supplied reference characters
- Their defensive actions should originate from plausible positions such as:
- - battlements
- - towers
- - gatehouse
- - arrow slits
- - wall platforms
- Do not add numerous unrelated generic defenders that clutter the reference characters.
- ══════════════════════════════════════════════════
- CAMERA + COMPOSITION ENGINE
- ══════════════════════════════════════════════════
- Choose a camera that proves:
- 1. the referenced characters are recognizable
- 2. the catapults are clearly readable
- 3. the castle is visibly the target
- 4. projectile motion or siege activity is understandable
- 5. the image still feels like one dramatic composition
- The default is a wide cinematic three-quarter battlefield view from the attacking side.
- This typically places:
- - one hero catapult crew prominently in the foreground
- - other catapults staggered into the middle ground
- - open trajectory space above and beyond them
- - the castle large enough to remain visually important in the background
- Use perspective to create depth rather than arranging every character in a flat horizontal row.
- A slightly low or ground-level camera may emphasize siege-engine scale.
- A moderately elevated view may be used when several crews and trajectory relationships must remain readable.
- Do not use an extreme bird's-eye shot if it makes the reference characters unrecognizable.
- Do not use a tight portrait shot if it hides the catapult mechanism or castle.
- ══════════════════════════════════════════════════
- PRIMARY VISUAL HIERARCHY
- ══════════════════════════════════════════════════
- The image hierarchy should normally be:
- PRIMARY:
- the active referenced catapult crews and their siege engines
- SECONDARY:
- the castle target and projectile action
- TERTIARY:
- battlefield debris, background forces, smoke, environmental storytelling, distant defenders, supplementary machinery
- The castle may become co-primary when its architecture is itself a major user-supplied reference.
- Do not let smoke, explosions, armies, or scenery overwhelm the characters.
- Do not shrink the reference cast into tiny unidentifiable battlefield specks merely to show an enormous panorama.
- ══════════════════════════════════════════════════
- CHARACTER LEGIBILITY BUDGET
- ══════════════════════════════════════════════════
- When many reference characters are present, preserve identity through composition rather than demanding identical visual prominence for everyone.
- At minimum, each important character should retain enough visible information to recognize:
- - head/face
- - silhouette
- - primary colors
- - species/body type
- - signature clothing or markings
- Foreground characters may receive greater facial detail.
- Midground characters may rely more heavily on silhouette and palette.
- Avoid placing a critical character completely behind:
- - the throwing arm
- - counterweight
- - projectile
- - another character
- - dense smoke
- - frame edge
- unless only incidental partial occlusion occurs.
- ══════════════════════════════════════════════════
- SCALE + DEPTH CONTRACT
- ══════════════════════════════════════════════════
- Maintain coherent scale across:
- CHARACTERS
- ↔ CATAPULTS
- ↔ PROJECTILES
- ↔ CASTLE
- ↔ TERRAIN
- Characters must appear physically capable of standing on, beside, or operating their assigned machines.
- Catapults should not arbitrarily change size across the battlefield due only to composition.
- Castle scale should communicate real distance and fortification mass.
- Atmospheric perspective may reduce detail with distance, but architectural proportions should remain stable.
- Use overlap, diminishing scale, ground-plane perspective, and atmospheric depth rather than random resizing.
- ══════════════════════════════════════════════════
- ENVIRONMENTAL SUPPORT
- ══════════════════════════════════════════════════
- Construct only environmental elements that support the siege.
- Useful details may include:
- - wheel tracks
- - churned earth
- - ropes
- - ammunition piles
- - carts
- - broken masonry
- - siege ladders
- - shields
- - repair tools
- - banners
- - camp structures
- - smoke from previous impacts
- - trenches
- - muddy or scorched terrain
- These should establish history and function.
- Do not fill the image with unrelated fantasy clutter.
- The environment should explain that the assault has been underway rather than looking like pristine characters placed on an empty field.
- ══════════════════════════════════════════════════
- TONE TRANSLATION
- ══════════════════════════════════════════════════
- SERIOUS / HISTORICAL
- Favor believable engineering, grounded materials, disciplined crews, restrained effects, and physical scale.
- EPIC FANTASY
- Allow monumental architecture, stylized machines, magical materials, heroic atmosphere, and dramatic effects while preserving mechanical readability.
- COMEDIC / ABSURD
- Let projectile choice, character reactions, incongruous siege preparation, or exaggerated engineering carry the humor.
- Do not abandon visual coherence merely because the premise is absurd.
- CARTOON / WHIMSICAL
- Simplify forms and increase expressive posing while preserving character identity and catapult logic.
- DARK / BRUTAL
- Increase environmental wear, smoke, damage, harsh weather, and battlefield stress without automatically turning the scene into graphic gore.
- ══════════════════════════════════════════════════
- STYLE TRANSLATION
- ══════════════════════════════════════════════════
- The requested visual style affects rendering, not system coherence.
- PHOTOREALISTIC:
- credible materials, believable light, realistic depth, physically convincing machines and debris.
- CINEMATIC ILLUSTRATION:
- polished dramatic lighting, strong depth, expressive posing, controlled stylization.
- PAINTERLY:
- visible artistic interpretation while preserving reference identity and readable mechanical relationships.
- ANIMATION-INSPIRED:
- clean silhouettes, expressive poses, simplified yet coherent machinery.
- MINIATURE DIORAMA:
- all subjects must read as physical scale models with tangible materials and practical miniature construction.
- GRAPHIC NOVEL:
- strong shape language, readable action, controlled impact effects, bold composition.
- Do not allow style transformation to erase the species, anatomy, costume, or identity established by the references.
- ══════════════════════════════════════════════════
- CUSTOM PROJECTILE INFERENCE
- ══════════════════════════════════════════════════
- The projectile field may be extremely open-ended.
- Infer all necessary consequences.
- If PROJECTILE = giant pumpkin:
- - provide a cradle or sling capable of holding it
- - allow loaders to strain or roll it into place
- - preserve pumpkin form in flight
- - depict appropriate impact debris
- If PROJECTILE = piano:
- - engineer loading logistics around a rigid heavy rectangular object
- - orient the sling accordingly
- - preserve keys/body identity in flight
- - do not turn it into a generic wooden block
- If PROJECTILE = water balloon:
- - use a suitable container or launch solution
- - show elasticity
- - avoid treating it like stone
- - impact should create water rather than masonry-style debris
- If PROJECTILE = magical energy orb:
- - the siege machine may include a compatible containment cradle
- - maintain a clear origin from the machine
- - do not turn the catapult itself into an unrelated spellcaster unless requested
- These examples demonstrate inference only.
- Do not copy them unless the user requests those projectiles.
- ══════════════════════════════════════════════════
- SURPRISE-ME ENGINE
- ══════════════════════════════════════════════════
- When fields are left to SURPRISE ME, make one decisive coherent choice rather than combining many random possibilities.
- Randomization should produce relationships.
- For example, if the system chooses:
- - a snowy mountain fortress
- then propagate that into:
- - winter lighting
- - snow accumulation
- - terrain
- - siege-engine wear
- - crew footing
- - appropriate battlefield atmosphere
- If it chooses:
- - oversized fruit as ammunition
- then propagate that into:
- - storage piles
- - loading behavior
- - splatter on impact
- - comedic or surreal tone
- Do not randomize each field independently into contradiction.
- ══════════════════════════════════════════════════
- REFERENCE-BASED DESIGN INFLUENCE
- ══════════════════════════════════════════════════
- When useful, let the supplied characters influence the attacking force's visual identity.
- Shared faction presentation may derive from recurring reference traits such as:
- - colors
- - symbols
- - motifs
- - cultural cues
- - technological language
- - costume materials
- This may appear in:
- - banners
- - shields
- - siege-engine paint
- - command flags
- - crew tools
- - ammunition carts
- However, do not force unrelated referenced characters into identical uniforms unless the user asks for one army aesthetic.
- If the supplied cast is intentionally eclectic, preserve that eclecticism.
- ══════════════════════════════════════════════════
- CASTLE REFERENCE RECONSTRUCTION RULE
- ══════════════════════════════════════════════════
- When a castle reference is attached, first reconstruct the castle as though it were intact and unobstructed.
- Internally identify:
- - main massing
- - wall arrangement
- - tower count and placement
- - tallest structures
- - gate location
- - roof forms
- - distinctive windows
- - decorative motifs
- - major colors/materials
- Then apply:
- - battlefield atmosphere
- - siege damage
- - smoke
- - debris
- - lighting
- Do not begin with generic damaged walls and attempt to decorate them afterward to resemble the reference.
- REFERENCE CASTLE
- → CANONICAL CASTLE
- → SIEGE STATE
- not:
- GENERIC CASTLE
- → DAMAGE
- → VAGUE REFERENCE COLORS
- ══════════════════════════════════════════════════
- CASTLE DAMAGE IDENTITY LOCK
- ══════════════════════════════════════════════════
- Damage must not erase the architectural identity that the user wanted preserved.
- Protect enough undamaged structure that the castle remains recognizable.
- When an iconic tower, gate, roofline, emblem, silhouette, or facade feature defines the reference castle, do not destroy all of those defining landmarks at once unless the user explicitly requests total ruin.
- The siege should affect the castle.
- It should not replace the castle.
- ══════════════════════════════════════════════════
- ACTION-READABILITY CONTRACT
- ══════════════════════════════════════════════════
- The viewer should be able to answer all of the following at a glance:
- WHO is attacking?
- WHAT are they using?
- WHAT are they launching?
- WHERE is it going?
- WHAT are they attacking?
- WHAT stage of the assault is happening?
- Do not rely only on implied lore or hidden prompt logic.
- The final image must visibly prove the action.
- ══════════════════════════════════════════════════
- NO-DISCONNECTED-ACTION RULE
- ══════════════════════════════════════════════════
- Avoid the common failure in which:
- - characters pose dramatically
- - catapults sit nearby
- - projectiles float in the sky
- - castle explodes in the distance
- without any visible causal relationship.
- Instead construct:
- CREW ACTION
- → MACHINE STATE
- → LAUNCH
- → TRAJECTORY
- → TARGET RESPONSE
- Every major action element should belong to that chain.
- ══════════════════════════════════════════════════
- TEMPORAL COHERENCE
- ══════════════════════════════════════════════════
- The image represents ONE battlefield moment.
- Different catapults may occupy different phases because separate machines can act asynchronously.
- The same catapult may not show mutually exclusive states simultaneously.
- The same individual character may not appear in two distant positions unless explicit duplicates of that character were requested.
- Projectile impact, dust, recoil, crew reaction, and machine pose should describe compatible fractions of the same moment.
- ══════════════════════════════════════════════════
- MOTION + FORCE
- ══════════════════════════════════════════════════
- Communicate force through physical consequences.
- Useful cues include:
- - tensioned rope
- - straining posture
- - flexing sling
- - moving throwing arm
- - counterweight drop
- - traction crew movement
- - dust at wheels
- - recoil in loose equipment
- - hair, fabric, ears, tails, or banners reacting to motion
- - projectile blur
- - masonry debris
- Do not rely on arbitrary speed lines unless they suit the selected style.
- Motion cues must originate from actual mechanical or environmental events.
- ══════════════════════════════════════════════════
- CATAPULT DAMAGE PREVENTION
- ══════════════════════════════════════════════════
- Do not confuse dynamic machinery with structural breakage.
- Ropes should remain attached to plausible points.
- Throwing arms should remain continuous.
- Axles should remain connected.
- Wheels should remain attached unless battlefield damage explicitly affects them.
- Flexible ropes may curve, slacken, tighten, or whip naturally.
- Do not depict:
- - snapped throwing arms
- - random floating rope fragments
- - detached counterweights
- - impossible sling connections
- - shattered frames
- merely as shorthand for action.
- If a machine is intentionally damaged, isolate that state to the specific machine and show a clear cause.
- ══════════════════════════════════════════════════
- PROJECTILE COUNT CONTROL
- ══════════════════════════════════════════════════
- Do not duplicate a unique projectile accidentally.
- If the user requests exactly one special projectile:
- - show only one active instance unless reserve duplicates are explicitly requested
- If multiple catapults fire the same kind of ammunition:
- - multiple instances are allowed
- - maintain consistent design and scale
- If each catapult has a different projectile:
- assign each one clearly before composing the scene.
- CATAPULT A
- → PROJECTILE A
- CATAPULT B
- → PROJECTILE B
- CATAPULT C
- → PROJECTILE C
- Do not swap them mid-scene.
- ══════════════════════════════════════════════════
- TEXT + SYMBOL CONTROL
- ══════════════════════════════════════════════════
- Do not add explanatory labels, names, arrows, UI text, captions, or infographic annotation unless requested.
- Visible text may appear naturally when it belongs diegetically on:
- - banners
- - clothing
- - shields
- - signs
- - catapult markings
- - castle heraldry
- Preserve exact readable wording from character references only when it is identity-critical.
- Do not fill clothing, banners, or castle surfaces with invented pseudo-text.
- ══════════════════════════════════════════════════
- CROPPING PROTECTION
- ══════════════════════════════════════════════════
- Protect:
- - important character heads and faces
- - major reference identity traits
- - at least one complete readable catapult
- - custom projectile when central
- - major castle silhouette
- - important impact area
- Partial cropping of secondary machinery or incidental crew may occur naturally at the frame edge.
- Do not crop every throwing arm, every projectile, or the entire castle gate simultaneously.
- The image must retain enough full structural evidence to explain the siege.
- ══════════════════════════════════════════════════
- DEFAULT SHOWCASE COMPOSITION
- ══════════════════════════════════════════════════
- When the user provides references but little other direction, use the following strong default:
- Create a cinematic widescreen battlefield assault with THREE catapults positioned at staggered depths.
- The nearest catapult is the hero crew and receives the clearest character identity.
- A second catapult is captured at the instant of launch.
- A third is being loaded or reset.
- Use the supplied reference characters as the attacking crews, distributing them according to anatomy, personality, and composition.
- If more referenced characters exist, incorporate them as additional crew members before inventing generic attackers.
- The castle rises prominently across the middle-background, large enough to preserve architectural identity.
- Show at least one clearly recognizable custom projectile in flight and one active or recent impact on the fortress when compatible with the selected siege moment.
- Keep the sky and trajectory corridor readable.
- Use battlefield atmosphere and debris sparingly enough that the reference characters and catapults remain visible.
- This is a default, not a restriction.
- User instructions override it.
- ══════════════════════════════════════════════════
- PREDICTIVE FAILURE PREVENTION
- ══════════════════════════════════════════════════
- Before producing the image, actively prevent these likely failures.
- IDENTITY MERGING
- Do not combine traits from several reference sheets into one accidental hybrid.
- CHARACTER DRIFT
- Do not simplify unique characters into generic soldiers.
- ANATOMY NORMALIZATION
- Do not invent ordinary human limbs for unusual species.
- CREW CLONING
- Do not turn every crew member into the same face unless deliberate duplicates were requested.
- CATAPULT DIRECTION ERROR
- Ensure every attacking machine visibly faces the castle.
- MECHANICAL NONSENSE
- Do not combine incompatible siege mechanisms without intent.
- PROJECTILE SUBSTITUTION
- Do not replace custom ammunition with generic rocks.
- FLOATING PROJECTILE ERROR
- Every airborne projectile must have an understandable source.
- TEMPORAL COLLAPSE
- Do not depict one machine in incompatible simultaneous states.
- CASTLE GENERICIZATION
- Preserve castle reference identity rather than replacing it with generic battlements.
- RANDOM DAMAGE
- Damage must correlate with impact events.
- SCALE COLLAPSE
- Maintain believable scale among crew, machines, ammunition, and castle.
- CROWDING
- Do not include so many characters, engines, effects, and projectiles that the references become unreadable.
- WEAPON-AS-PROP FAILURE
- Characters must actually interact with the mechanisms.
- COLLAGE FAILURE
- The result must remain one unified scene, not multiple disconnected panels or pasted references.
- ══════════════════════════════════════════════════
- CONFLICT PRIORITY
- ══════════════════════════════════════════════════
- When instructions conflict, resolve them in this order:
- 1. explicit current user instructions
- 2. requested character count and identities
- 3. character reference anatomy and defining traits
- 4. explicitly assigned castle-reference identity
- 5. specified projectile identity
- 6. catapult count and siege-engine type
- 7. action readability and mechanical continuity
- 8. requested tone and style
- 9. inferred realism
- 10. optional environmental enrichment
- If realism conflicts with an explicitly absurd projectile, preserve the absurd projectile and construct a visual logic capable of supporting it.
- If castle detail conflicts with character visibility, preserve both through camera and scale before sacrificing either.
- If a reference outfit conflicts with historical accuracy, preserve the reference outfit unless the user explicitly requests historical conversion.
- ══════════════════════════════════════════════════
- FINAL VALIDATION
- ══════════════════════════════════════════════════
- Before generating the finished image, verify:
- REFERENCE CAST
- - Every important supplied character is traceable to the correct reference.
- - Distinct references have not been fused accidentally.
- - Species, anatomy, face, markings, palette, and signature clothing remain recognizable.
- - Repeated instances are intentional.
- CREWS
- - Every important crew member has a readable role.
- - Character anatomy plausibly interfaces with the machine.
- - Hands, paws, claws, tentacles, or other appendages contact real objects where required.
- - No unnecessary extra limbs have appeared.
- CATAPULTS
- - The requested number is present.
- - Each machine belongs to the correct siege-engine family.
- - Major components are physically connected.
- - Every attacking machine faces the castle.
- - Each machine occupies one coherent action state.
- PROJECTILES
- - The correct custom objects are present.
- - Their scale is internally coherent.
- - Loaded, airborne, and impacted examples preserve identity.
- - Every active projectile has a readable origin and trajectory.
- CASTLE
- - The castle matches its reference when supplied.
- - The overall silhouette remains recognizable.
- - Damage corresponds to the assault.
- - Siege effects do not erase all identifying architecture.
- SCENE
- - The viewer immediately understands attacker, weapon, ammunition, trajectory, and target.
- - The characters, siege engines, and castle share one believable space.
- - The image does not resemble a collage or reference sheet.
- - Important faces and structures are not obscured by unnecessary smoke or debris.
- - Perspective and scale remain coherent.
- PRESENTATION
- - The primary reference characters remain legible.
- - The castle is large enough to matter.
- - The custom projectile is visible when central to the concept.
- - The chosen aspect ratio supports the number of subjects.
- - Supporting battlefield detail does not overpower the action.
- Do not generate until the scene can satisfy these relationships as ONE coherent visual event.
- ══════════════════════════════════════════════════
- FINAL OUTPUT CONTRACT
- ══════════════════════════════════════════════════
- Generate ONE finished image.
- Do not output:
- - design notes
- - prompt analysis
- - reference sheets
- - concept boards
- - split-screen comparisons
- - construction diagrams
- - text explanations
- - multiple alternate scenes
- unless the user explicitly asks for them.
- The result should feel like a real, fully staged siege moment built specifically around the supplied reference cast, their actual anatomy and identities, a coherent family of working siege engines, a recognizable customizable castle, and ammunition whose physical and visual consequences propagate through the entire scene.
- The central test is:
- Could the viewer identify WHO is attacking, understand HOW they are operating the siege engines, recognize WHAT they are launching, trace WHERE it is going, and see WHAT it is doing to the intended castle—all without sacrificing the identities established by the supplied references?
- If yes, generate the image.
Advertisement
Add Comment
Please, Sign In to add comment