LuckyMouse420

Untitled

Sep 3rd, 2026
48
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 56.37 KB | None | 0 0
  1. UNIVERSAL CATAPULT CREW + CASTLE ASSAULT IMAGE GENERATOR
  2. VERSION 1.0 — MULTI-REFERENCE CHARACTER CASTING + SIEGE-ENGINE CREW LOGIC + CASTLE TARGET SYSTEM + CUSTOM PROJECTILE WARFARE
  3.  
  4. ══════════════════════════════════════════════════
  5. CORE PURPOSE
  6. ══════════════════════════════════════════════════
  7.  
  8. 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.
  9.  
  10. The generator must be capable of working from:
  11.  
  12. - one character reference sheet
  13. - several character reference sheets
  14. - repeated use of one referenced character
  15. - several distinct referenced characters
  16. - one or more castle/environment references
  17. - no castle reference at all
  18. - minimal user customization
  19. - extensive user customization
  20. - conventional siege ammunition
  21. - absurd, comedic, fantastical, symbolic, oversized, improvised, or user-defined projectiles
  22.  
  23. The image should read as a coherent siege scene rather than as unrelated characters standing beside siege equipment.
  24.  
  25. The governing process is:
  26.  
  27. USER CUSTOMIZATION
  28. → REFERENCE AUTHORITY ASSIGNMENT
  29. → CHARACTER CAST LEDGER
  30. → CASTLE MASTER
  31. → CATAPULT MASTER
  32. → CREW ASSIGNMENT
  33. → PROJECTILE SYSTEM
  34. → SIEGE ACTION STATE
  35. → SPATIAL BATTLE MAP
  36. → CAMERA + SCALE
  37. → EFFECTS + IMPACT CONTINUITY
  38. → IDENTITY VALIDATION
  39. → FINAL IMAGE
  40.  
  41. The references are source material for ONE unified scene.
  42.  
  43. Do not make a reference sheet, character lineup, design board, collage, split-screen presentation, or disconnected collection of mini-scenes unless explicitly requested.
  44.  
  45. Generate one complete scene.
  46.  
  47. ══════════════════════════════════════════════════
  48. CUSTOMIZABLE INPUTS
  49. ══════════════════════════════════════════════════
  50.  
  51. Accept any natural-language combination of the following fields.
  52.  
  53. CHARACTER REFERENCES:
  54. [ATTACH ONE OR MORE CHARACTER REFERENCE SHEETS / IMAGES]
  55.  
  56. CHARACTER USAGE:
  57. [DEFAULT / SURPRISE ME / specify which characters appear, how many times each appears, or who belongs to which crew]
  58.  
  59. NUMBER OF CATAPULTS:
  60. [DEFAULT / SURPRISE ME / exact number]
  61.  
  62. CREW SIZE:
  63. [DEFAULT / SURPRISE ME / exact number per catapult / different sizes by crew]
  64.  
  65. CREW ROLES:
  66. [DEFAULT / SURPRISE ME / specify operator, loader, spotter, commander, hauler, defender, etc.]
  67.  
  68. CATAPULT TYPE:
  69. [DEFAULT / SURPRISE ME / traction trebuchet / counterweight trebuchet / mangonel / onager / fantasy catapult / improvised siege engine / other]
  70.  
  71. CASTLE:
  72. [DEFAULT / SURPRISE ME / description]
  73.  
  74. CASTLE REFERENCE:
  75. [OPTIONAL ATTACHED IMAGE OR IMAGES]
  76.  
  77. CASTLE CONDITION:
  78. [DEFAULT intact-but-under-attack / pristine / damaged / heavily besieged / breached / burning / fantastical / other]
  79.  
  80. CASTLE DEFENDERS:
  81. [NONE by default / SURPRISE ME / specify]
  82.  
  83. PROJECTILE:
  84. [Watermelons]
  85.  
  86. PROJECTILE VARIATION:
  87. [SAME OBJECT FROM ALL CATAPULTS / DIFFERENT OBJECT PER CATAPULT / SURPRISE ME]
  88.  
  89. SIEGE MOMENT:
  90. [DEFAULT mixed active assault / loading / tensioning / release / projectile in flight / impact / aftermath / coordinated volley / other]
  91.  
  92. TONE:
  93. [DEFAULT cinematic adventure / serious / heroic / comedic / absurd / dark / chaotic / whimsical / epic / other]
  94.  
  95. SETTING:
  96. [DEFAULT medieval-inspired battlefield / user-defined]
  97.  
  98. TIME + WEATHER:
  99. [DEFAULT / SURPRISE ME / user-defined]
  100.  
  101. VISUAL STYLE:
  102. [DEFAULT polished cinematic illustration / photorealistic / painterly / animation-inspired / miniature diorama / graphic novel / other]
  103.  
  104. CAMERA:
  105. [DEFAULT / user-defined]
  106.  
  107. ASPECT RATIO:
  108. [DEFAULT 16:9 / user-defined]
  109.  
  110. ADDITIONAL INSTRUCTIONS:
  111. [OPTIONAL NATURAL-LANGUAGE OVERRIDES]
  112.  
  113. Any field left at DEFAULT or blank must be completed intelligently.
  114.  
  115. Do not print the word DEFAULT into the image.
  116.  
  117. The generator must still produce a complete scene if the user provides only character references and nothing else.
  118.  
  119. ══════════════════════════════════════════════════
  120. REFERENCE AUTHORITY SYSTEM
  121. ══════════════════════════════════════════════════
  122.  
  123. Assign every supplied reference an explicit role before constructing the scene.
  124.  
  125. CHARACTER REFERENCES are the PRIMARY IDENTITY AUTHORITY for the characters derived from them.
  126.  
  127. Preserve, as applicable:
  128.  
  129. - species
  130. - body type
  131. - anatomy
  132. - topology
  133. - proportions
  134. - head shape
  135. - face
  136. - fur, skin, scales, feathers, shell, or equivalent surface
  137. - eye design
  138. - hair
  139. - ears
  140. - horns
  141. - tails
  142. - wings
  143. - unusual limb arrangements
  144. - detached or floating anatomy
  145. - markings
  146. - palette
  147. - clothing
  148. - armor
  149. - signature accessories
  150. - symbols
  151. - distinctive asymmetry
  152. - age presentation
  153. - sex presentation
  154. - recognizable personality cues
  155.  
  156. Do not normalize unusual characters into generic humans.
  157.  
  158. Do not replace species-specific anatomy merely to make operating the catapult easier.
  159.  
  160. Instead, adapt crew behavior, stance, grip, controls, equipment position, and catapult interface around the actual anatomy of the referenced character.
  161.  
  162. CASTLE REFERENCES control only the castle/environment dimensions they visibly establish or that the user assigns to them.
  163.  
  164. Possible castle-reference authority includes:
  165.  
  166. - architectural identity
  167. - silhouette
  168. - towers
  169. - walls
  170. - gates
  171. - battlements
  172. - materials
  173. - color
  174. - terrain
  175. - surrounding city
  176. - landscape
  177. - architectural era
  178. - decorative motifs
  179. - damage state if intentionally shown
  180. - overall atmospheric identity
  181.  
  182. Do not let a castle reference redesign the attacking characters.
  183.  
  184. Do not let a character reference redesign the castle unless the user explicitly requests a character-themed fortress.
  185.  
  186. STYLE REFERENCES, when supplied as such, control style rather than identity.
  187.  
  188. POSE REFERENCES control pose/action only.
  189.  
  190. The same image may hold more than one role only when that interpretation is clearly intended.
  191.  
  192. ══════════════════════════════════════════════════
  193. CHARACTER CAST LEDGER
  194. ══════════════════════════════════════════════════
  195.  
  196. Before staging the battle, establish a CAST LEDGER.
  197.  
  198. For every distinct referenced character selected for the image, determine:
  199.  
  200. - canonical identity
  201. - source reference
  202. - number of diegetic instances
  203. - crew assignment
  204. - role
  205. - scale relative to other characters
  206. - required anatomy
  207. - clothing and equipment
  208. - personality expression
  209. - any user-requested modifications
  210.  
  211. Do not design each appearance independently.
  212.  
  213. Every instance derived from the same character reference must remain recognizably that character.
  214.  
  215. If the user requests the same character several times, those are intentional duplicate diegetic instances of the same character design.
  216.  
  217. If the user supplies several reference sheets, do not accidentally merge their features into one hybrid unless the user explicitly requests fusion.
  218.  
  219. Maintain strict reference-to-character correspondence:
  220.  
  221. REFERENCE A
  222. → CHARACTER A
  223.  
  224. REFERENCE B
  225. → CHARACTER B
  226.  
  227. REFERENCE C
  228. → CHARACTER C
  229.  
  230. and so on.
  231.  
  232. No facial swapping.
  233.  
  234. No costume swapping.
  235.  
  236. No species blending.
  237.  
  238. No accidental color exchange.
  239.  
  240. No identity drift merely because several characters occupy the same crew.
  241.  
  242. ══════════════════════════════════════════════════
  243. MULTI-REFERENCE CASTING LOGIC
  244. ══════════════════════════════════════════════════
  245.  
  246. Use the supplied reference cast intelligently.
  247.  
  248. When CHARACTER USAGE is unspecified:
  249.  
  250. - include enough referenced characters to make the siege feel populated and purposeful
  251. - prioritize using distinct references rather than inventing unrelated generic crew
  252. - reuse referenced characters only when necessary for crew completeness or composition
  253. - do not overcrowd the scene merely to include every possible reference if the requested image cannot support them legibly
  254.  
  255. If the number of supplied characters fits the selected crew count exactly, assign each one once by default.
  256.  
  257. If more characters are supplied than can fit clearly:
  258.  
  259. 1. preserve the most visually distinct characters
  260. 2. prioritize user-emphasized characters
  261. 3. adjust crew size or number of catapults when feasible
  262. 4. omit only when necessary for image readability
  263.  
  264. If fewer characters are supplied than needed:
  265.  
  266. - reuse supplied characters as additional instances when appropriate
  267. - or reduce crew size
  268. - avoid inventing prominent new characters unless necessary
  269.  
  270. Incidental distant figures may be generic only when they are visually minor and do not compete with the reference cast.
  271.  
  272. The referenced characters should remain the principal attackers.
  273.  
  274. ══════════════════════════════════════════════════
  275. CREW ROLE ENGINE
  276. ══════════════════════════════════════════════════
  277.  
  278. Every visible attacker should have a believable battlefield purpose.
  279.  
  280. Possible roles include:
  281.  
  282. CATAPULT COMMANDER
  283.  
  284. Signals timing, points toward the target, coordinates the crew, watches trajectory, or gives orders.
  285.  
  286. AIMER / GUNNER
  287.  
  288. Adjusts orientation, elevation, release angle, sling placement, or mechanical aiming components where appropriate to the siege engine type.
  289.  
  290. LOADER
  291.  
  292. Positions the projectile into the sling, cup, basket, or launch cradle.
  293.  
  294. TENSION / WINCH OPERATOR
  295.  
  296. Works ropes, capstans, winches, counterweight controls, torsion systems, or drawing mechanisms.
  297.  
  298. ROPE CREW
  299.  
  300. Pulls traction ropes or handles other force-generating systems when appropriate.
  301.  
  302. AMMUNITION HANDLER
  303.  
  304. Carries, rolls, drags, lifts, or prepares incoming projectiles.
  305.  
  306. SPOTTER
  307.  
  308. Observes the castle and estimates where the shot lands.
  309.  
  310. DEFENDER
  311.  
  312. Protects the machine with shield, weapon, magic, or other user-compatible means if battlefield defenders are desired.
  313.  
  314. SUPPORT CREW
  315.  
  316. Brings ammunition, tools, replacement rope, water, repairs, or other siege necessities.
  317.  
  318. Roles should be adapted to the selected catapult.
  319.  
  320. Do not show characters pretending to operate controls that do not exist.
  321.  
  322. Do not make every crew member adopt the same generic pushing pose.
  323.  
  324. The image should communicate distributed teamwork.
  325.  
  326. ══════════════════════════════════════════════════
  327. ANATOMY-TO-SIEGE INTERFACE
  328. ══════════════════════════════════════════════════
  329.  
  330. Build every character's interaction with the siege engine around their actual anatomy.
  331.  
  332. For characters with ordinary arms and hands:
  333.  
  334. - hands should wrap around real ropes, handles, cranks, levers, frames, tools, or ammunition
  335. - grips must correspond to physical contact points
  336. - arm direction should align with the force being applied
  337.  
  338. For characters with paws, claws, talons, hooves, tentacles, floating hands, unusual limb counts, wings, tails, or other anatomy:
  339.  
  340. translate the operator interface to something they can plausibly use.
  341.  
  342. Examples of compatible adaptation include:
  343.  
  344. - larger handholds
  345. - lower cranks
  346. - rope loops
  347. - harnesses
  348. - widened platforms
  349. - tail-assisted bracing
  350. - tentacle-compatible rope bundles
  351. - floating-hand operation
  352. - species-scaled ladders or footrests
  353.  
  354. Do not generate human arms merely because the mechanism expects hands.
  355.  
  356. Do not give extra limbs unless canon or user instruction allows them.
  357.  
  358. Do not fuse a character into the catapult.
  359.  
  360. CHARACTER
  361. ↔ CONTACT POINT
  362. ↔ FORCE DIRECTION
  363. ↔ MACHINE RESPONSE
  364.  
  365. must remain readable.
  366.  
  367. ══════════════════════════════════════════════════
  368. CATAPULT MASTER SYSTEM
  369. ══════════════════════════════════════════════════
  370.  
  371. Construct each siege engine as a believable complete mechanism before posing the crew around it.
  372.  
  373. The selected siege-engine type determines its anatomy.
  374.  
  375. Possible structural elements may include:
  376.  
  377. - base frame
  378. - wheels or sled runners
  379. - throwing arm
  380. - axle
  381. - sling or launch cup
  382. - release hook
  383. - counterweight
  384. - torsion bundle
  385. - traction ropes
  386. - winch
  387. - ratchet
  388. - capstan
  389. - bracing
  390. - stabilizers
  391. - rope rigging
  392. - loading track
  393. - ammunition cradle
  394. - repair tools
  395.  
  396. Use only features appropriate to the selected machine.
  397.  
  398. Do not create a random hybrid of trebuchet, ballista, and catapult unless a fantastical hybrid is specifically requested.
  399.  
  400. The mechanism should remain visually legible enough that the action can be understood.
  401.  
  402. 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.
  403.  
  404. Do not accidentally produce a different siege-engine category for every machine unless requested.
  405.  
  406. ══════════════════════════════════════════════════
  407. CHARACTER-INFLUENCED SIEGE DESIGN
  408. ══════════════════════════════════════════════════
  409.  
  410. When appropriate, subtly adapt each catapult to its crew without turning it into a novelty sculpture.
  411.  
  412. Character influence may affect:
  413.  
  414. - paint
  415. - banners
  416. - shield emblems
  417. - carved motifs
  418. - rope colors
  419. - trim
  420. - armor plates
  421. - crew-scale controls
  422. - seats or platforms
  423. - ammunition racks
  424. - faction markings
  425. - practical accommodations for body shape or anatomy
  426.  
  427. Identity influence should feel functional and integrated.
  428.  
  429. Avoid simply painting the whole catapult in the character's colors and calling it customized.
  430.  
  431. Do not reshape the machine so aggressively that it ceases to function as the chosen siege engine.
  432.  
  433. ══════════════════════════════════════════════════
  434. CASTLE MASTER
  435. ══════════════════════════════════════════════════
  436.  
  437. Establish one coherent castle or fortified target before applying siege damage.
  438.  
  439. The castle should have stable spatial logic.
  440.  
  441. Define:
  442.  
  443. - overall silhouette
  444. - wall perimeter
  445. - major towers
  446. - gatehouse
  447. - battlements
  448. - central keep if applicable
  449. - visible wall faces
  450. - material
  451. - terrain relationship
  452. - approach route
  453. - defensive height
  454. - relevant architectural motifs
  455. - location of existing damage
  456. - location of new impact activity
  457.  
  458. If a castle reference is attached, reconstruct these features from the reference to the extent visible.
  459.  
  460. If several castle references depict different views of the SAME castle, treat them as complementary evidence for one canonical structure.
  461.  
  462. Do not independently redesign the castle from angle to angle within the same image.
  463.  
  464. If the references instead depict multiple sources of inspiration, merge only compatible architectural traits into one coherent fortress.
  465.  
  466. ══════════════════════════════════════════════════
  467. CASTLE CUSTOMIZATION + REFERENCE INFLUENCE
  468. ══════════════════════════════════════════════════
  469.  
  470. The castle may range from historically grounded to fantastical.
  471.  
  472. Possible customization may include:
  473.  
  474. - medieval stone fortress
  475. - gothic citadel
  476. - desert fortress
  477. - icy stronghold
  478. - toy castle
  479. - candy castle
  480. - futuristic fortified city
  481. - cartoon kingdom
  482. - haunted fortress
  483. - character-themed stronghold
  484. - floating castle
  485. - improvised fortification
  486. - any user-defined target
  487.  
  488. When a reference is present, preserve the recognizable castle identity before adding siege context.
  489.  
  490. Do not turn a supplied castle into a generic fortress simply because generic stone walls are easier.
  491.  
  492. If the castle comes from a known visual reference, protect its distinctive silhouette and defining architectural motifs.
  493.  
  494. ══════════════════════════════════════════════════
  495. BATTLEFIELD SPATIAL MAP
  496. ══════════════════════════════════════════════════
  497.  
  498. Construct one stable spatial relationship:
  499.  
  500. ATTACKING ARMY
  501. → CATAPULT LINE
  502. → OPEN TRAJECTORY SPACE
  503. → CASTLE DEFENSE ZONE
  504. → CASTLE
  505.  
  506. The geometry should clearly communicate which direction the assault is moving.
  507.  
  508. By default:
  509.  
  510. - attackers occupy the foreground and middle ground
  511. - catapults face toward the castle
  512. - the castle occupies middle distance or background
  513. - projectile trajectories travel from attackers toward the fortress
  514. - defensive fire, if present, travels in the opposite direction
  515.  
  516. Keep left/right and near/far relationships stable.
  517.  
  518. Do not accidentally reverse a catapult so its throwing arm launches away from the castle.
  519.  
  520. Do not point characters toward one target while the machine points elsewhere.
  521.  
  522. Do not make projectiles appear to originate from the castle unless they are explicitly defensive.
  523.  
  524. ══════════════════════════════════════════════════
  525. PROJECTILE MASTER SYSTEM
  526. ══════════════════════════════════════════════════
  527.  
  528. Treat the user's launched object as a real projectile occupying a specific stage of the siege process.
  529.  
  530. Determine:
  531.  
  532. - what the object is
  533. - its physical scale
  534. - mass implication
  535. - rigidity or flexibility
  536. - orientation in the sling or cup
  537. - how crew members handle it
  538. - whether special loading equipment is needed
  539. - whether it remains intact in flight
  540. - whether it changes after impact
  541. - whether multiples exist
  542. - whether several catapults use the same projectile class
  543.  
  544. The projectile must remain recognizable.
  545.  
  546. Do not reduce unusual custom projectiles to generic rocks.
  547.  
  548. 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.
  549.  
  550. ══════════════════════════════════════════════════
  551. PROJECTILE SCALE + LAUNCH FEASIBILITY
  552. ══════════════════════════════════════════════════
  553.  
  554. Scale the projectile relative to the siege engine in a way that supports the intended tone.
  555.  
  556. For grounded scenes:
  557.  
  558. respect plausible loading scale and machine capacity.
  559.  
  560. For fantastical or comedic scenes:
  561.  
  562. extreme scale may be accepted, but the image should still acknowledge the physical consequence.
  563.  
  564. An oversized projectile may require:
  565.  
  566. - a huge custom catapult
  567. - several loaders
  568. - rollers
  569. - ramps
  570. - ropes
  571. - cranes
  572. - magical assistance
  573. - exaggerated fantasy engineering
  574.  
  575. 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.
  576.  
  577. When physical realism is intentionally broken, make the violation feel deliberate rather than accidental.
  578.  
  579. ══════════════════════════════════════════════════
  580. PROJECTILE STATE CONTINUITY
  581. ══════════════════════════════════════════════════
  582.  
  583. When several examples of the projectile appear in the image, establish one canonical projectile design.
  584.  
  585. LOADED PROJECTILE
  586. ↔ IN-FLIGHT PROJECTILE
  587. ↔ IMPACTED PROJECTILE
  588.  
  589. must remain recognizably the same type of object.
  590.  
  591. Authorized differences may include:
  592.  
  593. - rotation
  594. - motion blur
  595. - dust
  596. - deformation
  597. - breakage after impact
  598. - burning after impact if applicable
  599. - debris generated by the collision
  600.  
  601. Do not redesign the object in mid-flight.
  602.  
  603. Do not make the loaded version one object and the airborne version another.
  604.  
  605. Do not show impact damage before impact unless the projectile began damaged.
  606.  
  607. ══════════════════════════════════════════════════
  608. SIEGE ACTION STATE ENGINE
  609. ══════════════════════════════════════════════════
  610.  
  611. By default, create a MIXED ACTIVE ASSAULT rather than freezing every machine at the same stage.
  612.  
  613. Across multiple catapults, useful simultaneous stages may include:
  614.  
  615. - one being loaded
  616. - one under tension
  617. - one at the instant of release
  618. - one projectile already in flight
  619. - one recent impact visible on the castle
  620.  
  621. This creates narrative depth while still representing one coherent battlefield moment.
  622.  
  623. Each individual catapult must occupy ONE mechanically reachable state.
  624.  
  625. Do not combine incompatible phases on the same machine.
  626.  
  627. A single catapult should not simultaneously have:
  628.  
  629. - its arm cocked
  630. - its arm released
  631. - the projectile still loaded
  632. - and that same projectile already halfway to the castle
  633.  
  634. unless separate projectiles and separate temporal logic are clearly established.
  635.  
  636. ══════════════════════════════════════════════════
  637. CATAPULT STATE CONTRACT
  638. ══════════════════════════════════════════════════
  639.  
  640. For each machine, internally choose one state.
  641.  
  642. LOADING STATE
  643.  
  644. - throwing arm lowered or positioned appropriately
  645. - projectile being placed
  646. - sling/cup accessible
  647. - crew working near loading area
  648.  
  649. COCKING / TENSIONING STATE
  650.  
  651. - projectile secured
  652. - mechanism visibly accumulating energy
  653. - crew working winches, ropes, capstans, or traction system
  654. - throwing arm positioned according to machine type
  655.  
  656. RELEASE STATE
  657.  
  658. - arm moving through launch arc
  659. - projectile leaving sling/cup
  660. - crew reacting to force
  661. - ropes and mechanism responding coherently
  662.  
  663. POST-RELEASE STATE
  664.  
  665. - projectile clear of machine
  666. - arm completing or having completed its swing
  667. - crew watching trajectory or preparing reset
  668.  
  669. RESET STATE
  670.  
  671. - crew restoring mechanism
  672. - no projectile magically already present unless a new one is being loaded
  673.  
  674. Mechanics may be stylized, but state relationships must remain understandable.
  675.  
  676. ══════════════════════════════════════════════════
  677. TRAJECTORY + FLIGHT LOGIC
  678. ══════════════════════════════════════════════════
  679.  
  680. Projectile paths should reinforce the siege geometry.
  681.  
  682. Use trajectories appropriate to the weapon.
  683.  
  684. Catapult and trebuchet projectiles generally travel in visible ballistic arcs.
  685.  
  686. Do not treat them like straight laser beams.
  687.  
  688. When several projectiles are airborne:
  689.  
  690. - vary their position along related arcs
  691. - maintain clear origin direction
  692. - avoid trajectory tangles that obscure the characters
  693. - avoid filling the sky with unnecessary ammunition unless a massive volley is requested
  694.  
  695. A projectile may overlap part of the scene through perspective, but the origin and destination should remain intelligible.
  696.  
  697. 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.
  698.  
  699. ══════════════════════════════════════════════════
  700. IMPACT + CASTLE DAMAGE CONTINUITY
  701. ══════════════════════════════════════════════════
  702.  
  703. Every major visible impact should have a readable cause.
  704.  
  705. PROJECTILE TRAJECTORY
  706. → IMPACT POINT
  707. → MATERIAL RESPONSE
  708. → LOCAL DAMAGE
  709. → DEBRIS / DUST / EFFECT
  710.  
  711. Castle damage should correspond to the material and projectile.
  712.  
  713. Stone may:
  714.  
  715. - crack
  716. - chip
  717. - shed masonry
  718. - create localized breaches
  719. - generate dust and fragments
  720.  
  721. Wood may:
  722.  
  723. - splinter
  724. - bend
  725. - break
  726. - ignite when appropriate
  727.  
  728. Metal may:
  729.  
  730. - dent
  731. - deform
  732. - spark if the collision justifies it
  733.  
  734. Fantastical materials should react according to their established logic.
  735.  
  736. Do not scatter random explosion effects over unrelated areas of the castle.
  737.  
  738. Do not erase large sections of architecture without a corresponding destructive event.
  739.  
  740. If the castle begins partially damaged, distinguish pre-existing damage from the currently depicted strike through placement and action cues.
  741.  
  742. ══════════════════════════════════════════════════
  743. CHARACTER PERFORMANCE + PERSONALITY
  744. ══════════════════════════════════════════════════
  745.  
  746. Do not merely preserve the characters physically.
  747.  
  748. Preserve how they would plausibly participate in the siege.
  749.  
  750. Translate personality cues from the references into:
  751.  
  752. - expressions
  753. - confidence
  754. - fear
  755. - enthusiasm
  756. - frustration
  757. - command posture
  758. - teamwork style
  759. - recklessness
  760. - professionalism
  761. - smugness
  762. - panic
  763. - humor
  764. - determination
  765.  
  766. A stoic character may operate with disciplined focus.
  767.  
  768. A chaotic character may gleefully overcommit to the launch.
  769.  
  770. A nervous character may brace for impact.
  771.  
  772. A heroic character may command from the front.
  773.  
  774. These are controlled extrapolations.
  775.  
  776. Do not overwrite a clearly established character personality with generic battle rage unless requested.
  777.  
  778. ══════════════════════════════════════════════════
  779. EQUIPMENT + COSTUME CONTINUITY
  780. ══════════════════════════════════════════════════
  781.  
  782. Preserve reference clothing and signature gear unless the user requests an alternate outfit.
  783.  
  784. When practical siege additions are useful, they may include:
  785.  
  786. - gloves
  787. - belts
  788. - harnesses
  789. - protective helmets
  790. - aprons
  791. - shields
  792. - ammunition pouches
  793. - tools
  794.  
  795. However, additions must not obscure or replace defining reference traits.
  796.  
  797. Use minimal adaptation.
  798.  
  799. A character should still be identifiable from their original sheet.
  800.  
  801. If a referenced outfit would realistically interfere with operating the machine, adapt pose and interface first rather than redesigning the outfit without permission.
  802.  
  803. ══════════════════════════════════════════════════
  804. CREW-TO-CATAPULT COUNT LOCK
  805. ══════════════════════════════════════════════════
  806.  
  807. Internally inventory:
  808.  
  809. NUMBER OF CATAPULTS
  810. → NUMBER OF CREWS
  811. → NUMBER OF CHARACTERS PER CREW
  812. → TOTAL CHARACTER INSTANCES
  813.  
  814. Do not accidentally create:
  815.  
  816. - an extra catapult
  817. - an unassigned duplicate crew
  818. - floating operators with no machine
  819. - one crew apparently operating two distant machines simultaneously
  820. - missing characters after the user specified exact counts
  821.  
  822. If one character belongs to a specific catapult, preserve that assignment.
  823.  
  824. When several machines overlap in perspective, keep the crew grouping readable through proximity, pose direction, and machine contact.
  825.  
  826. ══════════════════════════════════════════════════
  827. CASTLE DEFENDERS
  828. ══════════════════════════════════════════════════
  829.  
  830. Castle defenders are absent by default so the attacking reference cast remains the focus.
  831.  
  832. 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.
  833.  
  834. Possible defenders include:
  835.  
  836. - archers
  837. - guards
  838. - siege crews
  839. - magical defenders
  840. - creatures
  841. - user-supplied reference characters
  842.  
  843. Their defensive actions should originate from plausible positions such as:
  844.  
  845. - battlements
  846. - towers
  847. - gatehouse
  848. - arrow slits
  849. - wall platforms
  850.  
  851. Do not add numerous unrelated generic defenders that clutter the reference characters.
  852.  
  853. ══════════════════════════════════════════════════
  854. CAMERA + COMPOSITION ENGINE
  855. ══════════════════════════════════════════════════
  856.  
  857. Choose a camera that proves:
  858.  
  859. 1. the referenced characters are recognizable
  860. 2. the catapults are clearly readable
  861. 3. the castle is visibly the target
  862. 4. projectile motion or siege activity is understandable
  863. 5. the image still feels like one dramatic composition
  864.  
  865. The default is a wide cinematic three-quarter battlefield view from the attacking side.
  866.  
  867. This typically places:
  868.  
  869. - one hero catapult crew prominently in the foreground
  870. - other catapults staggered into the middle ground
  871. - open trajectory space above and beyond them
  872. - the castle large enough to remain visually important in the background
  873.  
  874. Use perspective to create depth rather than arranging every character in a flat horizontal row.
  875.  
  876. A slightly low or ground-level camera may emphasize siege-engine scale.
  877.  
  878. A moderately elevated view may be used when several crews and trajectory relationships must remain readable.
  879.  
  880. Do not use an extreme bird's-eye shot if it makes the reference characters unrecognizable.
  881.  
  882. Do not use a tight portrait shot if it hides the catapult mechanism or castle.
  883.  
  884. ══════════════════════════════════════════════════
  885. PRIMARY VISUAL HIERARCHY
  886. ══════════════════════════════════════════════════
  887.  
  888. The image hierarchy should normally be:
  889.  
  890. PRIMARY:
  891. the active referenced catapult crews and their siege engines
  892.  
  893. SECONDARY:
  894. the castle target and projectile action
  895.  
  896. TERTIARY:
  897. battlefield debris, background forces, smoke, environmental storytelling, distant defenders, supplementary machinery
  898.  
  899. The castle may become co-primary when its architecture is itself a major user-supplied reference.
  900.  
  901. Do not let smoke, explosions, armies, or scenery overwhelm the characters.
  902.  
  903. Do not shrink the reference cast into tiny unidentifiable battlefield specks merely to show an enormous panorama.
  904.  
  905. ══════════════════════════════════════════════════
  906. CHARACTER LEGIBILITY BUDGET
  907. ══════════════════════════════════════════════════
  908.  
  909. When many reference characters are present, preserve identity through composition rather than demanding identical visual prominence for everyone.
  910.  
  911. At minimum, each important character should retain enough visible information to recognize:
  912.  
  913. - head/face
  914. - silhouette
  915. - primary colors
  916. - species/body type
  917. - signature clothing or markings
  918.  
  919. Foreground characters may receive greater facial detail.
  920.  
  921. Midground characters may rely more heavily on silhouette and palette.
  922.  
  923. Avoid placing a critical character completely behind:
  924.  
  925. - the throwing arm
  926. - counterweight
  927. - projectile
  928. - another character
  929. - dense smoke
  930. - frame edge
  931.  
  932. unless only incidental partial occlusion occurs.
  933.  
  934. ══════════════════════════════════════════════════
  935. SCALE + DEPTH CONTRACT
  936. ══════════════════════════════════════════════════
  937.  
  938. Maintain coherent scale across:
  939.  
  940. CHARACTERS
  941. ↔ CATAPULTS
  942. ↔ PROJECTILES
  943. ↔ CASTLE
  944. ↔ TERRAIN
  945.  
  946. Characters must appear physically capable of standing on, beside, or operating their assigned machines.
  947.  
  948. Catapults should not arbitrarily change size across the battlefield due only to composition.
  949.  
  950. Castle scale should communicate real distance and fortification mass.
  951.  
  952. Atmospheric perspective may reduce detail with distance, but architectural proportions should remain stable.
  953.  
  954. Use overlap, diminishing scale, ground-plane perspective, and atmospheric depth rather than random resizing.
  955.  
  956. ══════════════════════════════════════════════════
  957. ENVIRONMENTAL SUPPORT
  958. ══════════════════════════════════════════════════
  959.  
  960. Construct only environmental elements that support the siege.
  961.  
  962. Useful details may include:
  963.  
  964. - wheel tracks
  965. - churned earth
  966. - ropes
  967. - ammunition piles
  968. - carts
  969. - broken masonry
  970. - siege ladders
  971. - shields
  972. - repair tools
  973. - banners
  974. - camp structures
  975. - smoke from previous impacts
  976. - trenches
  977. - muddy or scorched terrain
  978.  
  979. These should establish history and function.
  980.  
  981. Do not fill the image with unrelated fantasy clutter.
  982.  
  983. The environment should explain that the assault has been underway rather than looking like pristine characters placed on an empty field.
  984.  
  985. ══════════════════════════════════════════════════
  986. TONE TRANSLATION
  987. ══════════════════════════════════════════════════
  988.  
  989. SERIOUS / HISTORICAL
  990.  
  991. Favor believable engineering, grounded materials, disciplined crews, restrained effects, and physical scale.
  992.  
  993. EPIC FANTASY
  994.  
  995. Allow monumental architecture, stylized machines, magical materials, heroic atmosphere, and dramatic effects while preserving mechanical readability.
  996.  
  997. COMEDIC / ABSURD
  998.  
  999. Let projectile choice, character reactions, incongruous siege preparation, or exaggerated engineering carry the humor.
  1000.  
  1001. Do not abandon visual coherence merely because the premise is absurd.
  1002.  
  1003. CARTOON / WHIMSICAL
  1004.  
  1005. Simplify forms and increase expressive posing while preserving character identity and catapult logic.
  1006.  
  1007. DARK / BRUTAL
  1008.  
  1009. Increase environmental wear, smoke, damage, harsh weather, and battlefield stress without automatically turning the scene into graphic gore.
  1010.  
  1011. ══════════════════════════════════════════════════
  1012. STYLE TRANSLATION
  1013. ══════════════════════════════════════════════════
  1014.  
  1015. The requested visual style affects rendering, not system coherence.
  1016.  
  1017. PHOTOREALISTIC:
  1018. credible materials, believable light, realistic depth, physically convincing machines and debris.
  1019.  
  1020. CINEMATIC ILLUSTRATION:
  1021. polished dramatic lighting, strong depth, expressive posing, controlled stylization.
  1022.  
  1023. PAINTERLY:
  1024. visible artistic interpretation while preserving reference identity and readable mechanical relationships.
  1025.  
  1026. ANIMATION-INSPIRED:
  1027. clean silhouettes, expressive poses, simplified yet coherent machinery.
  1028.  
  1029. MINIATURE DIORAMA:
  1030. all subjects must read as physical scale models with tangible materials and practical miniature construction.
  1031.  
  1032. GRAPHIC NOVEL:
  1033. strong shape language, readable action, controlled impact effects, bold composition.
  1034.  
  1035. Do not allow style transformation to erase the species, anatomy, costume, or identity established by the references.
  1036.  
  1037. ══════════════════════════════════════════════════
  1038. CUSTOM PROJECTILE INFERENCE
  1039. ══════════════════════════════════════════════════
  1040.  
  1041. The projectile field may be extremely open-ended.
  1042.  
  1043. Infer all necessary consequences.
  1044.  
  1045. If PROJECTILE = giant pumpkin:
  1046.  
  1047. - provide a cradle or sling capable of holding it
  1048. - allow loaders to strain or roll it into place
  1049. - preserve pumpkin form in flight
  1050. - depict appropriate impact debris
  1051.  
  1052. If PROJECTILE = piano:
  1053.  
  1054. - engineer loading logistics around a rigid heavy rectangular object
  1055. - orient the sling accordingly
  1056. - preserve keys/body identity in flight
  1057. - do not turn it into a generic wooden block
  1058.  
  1059. If PROJECTILE = water balloon:
  1060.  
  1061. - use a suitable container or launch solution
  1062. - show elasticity
  1063. - avoid treating it like stone
  1064. - impact should create water rather than masonry-style debris
  1065.  
  1066. If PROJECTILE = magical energy orb:
  1067.  
  1068. - the siege machine may include a compatible containment cradle
  1069. - maintain a clear origin from the machine
  1070. - do not turn the catapult itself into an unrelated spellcaster unless requested
  1071.  
  1072. These examples demonstrate inference only.
  1073.  
  1074. Do not copy them unless the user requests those projectiles.
  1075.  
  1076. ══════════════════════════════════════════════════
  1077. SURPRISE-ME ENGINE
  1078. ══════════════════════════════════════════════════
  1079.  
  1080. When fields are left to SURPRISE ME, make one decisive coherent choice rather than combining many random possibilities.
  1081.  
  1082. Randomization should produce relationships.
  1083.  
  1084. For example, if the system chooses:
  1085.  
  1086. - a snowy mountain fortress
  1087.  
  1088. then propagate that into:
  1089.  
  1090. - winter lighting
  1091. - snow accumulation
  1092. - terrain
  1093. - siege-engine wear
  1094. - crew footing
  1095. - appropriate battlefield atmosphere
  1096.  
  1097. If it chooses:
  1098.  
  1099. - oversized fruit as ammunition
  1100.  
  1101. then propagate that into:
  1102.  
  1103. - storage piles
  1104. - loading behavior
  1105. - splatter on impact
  1106. - comedic or surreal tone
  1107.  
  1108. Do not randomize each field independently into contradiction.
  1109.  
  1110. ══════════════════════════════════════════════════
  1111. REFERENCE-BASED DESIGN INFLUENCE
  1112. ══════════════════════════════════════════════════
  1113.  
  1114. When useful, let the supplied characters influence the attacking force's visual identity.
  1115.  
  1116. Shared faction presentation may derive from recurring reference traits such as:
  1117.  
  1118. - colors
  1119. - symbols
  1120. - motifs
  1121. - cultural cues
  1122. - technological language
  1123. - costume materials
  1124.  
  1125. This may appear in:
  1126.  
  1127. - banners
  1128. - shields
  1129. - siege-engine paint
  1130. - command flags
  1131. - crew tools
  1132. - ammunition carts
  1133.  
  1134. However, do not force unrelated referenced characters into identical uniforms unless the user asks for one army aesthetic.
  1135.  
  1136. If the supplied cast is intentionally eclectic, preserve that eclecticism.
  1137.  
  1138. ══════════════════════════════════════════════════
  1139. CASTLE REFERENCE RECONSTRUCTION RULE
  1140. ══════════════════════════════════════════════════
  1141.  
  1142. When a castle reference is attached, first reconstruct the castle as though it were intact and unobstructed.
  1143.  
  1144. Internally identify:
  1145.  
  1146. - main massing
  1147. - wall arrangement
  1148. - tower count and placement
  1149. - tallest structures
  1150. - gate location
  1151. - roof forms
  1152. - distinctive windows
  1153. - decorative motifs
  1154. - major colors/materials
  1155.  
  1156. Then apply:
  1157.  
  1158. - battlefield atmosphere
  1159. - siege damage
  1160. - smoke
  1161. - debris
  1162. - lighting
  1163.  
  1164. Do not begin with generic damaged walls and attempt to decorate them afterward to resemble the reference.
  1165.  
  1166. REFERENCE CASTLE
  1167. → CANONICAL CASTLE
  1168. → SIEGE STATE
  1169.  
  1170. not:
  1171.  
  1172. GENERIC CASTLE
  1173. → DAMAGE
  1174. → VAGUE REFERENCE COLORS
  1175.  
  1176. ══════════════════════════════════════════════════
  1177. CASTLE DAMAGE IDENTITY LOCK
  1178. ══════════════════════════════════════════════════
  1179.  
  1180. Damage must not erase the architectural identity that the user wanted preserved.
  1181.  
  1182. Protect enough undamaged structure that the castle remains recognizable.
  1183.  
  1184. 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.
  1185.  
  1186. The siege should affect the castle.
  1187.  
  1188. It should not replace the castle.
  1189.  
  1190. ══════════════════════════════════════════════════
  1191. ACTION-READABILITY CONTRACT
  1192. ══════════════════════════════════════════════════
  1193.  
  1194. The viewer should be able to answer all of the following at a glance:
  1195.  
  1196. WHO is attacking?
  1197.  
  1198. WHAT are they using?
  1199.  
  1200. WHAT are they launching?
  1201.  
  1202. WHERE is it going?
  1203.  
  1204. WHAT are they attacking?
  1205.  
  1206. WHAT stage of the assault is happening?
  1207.  
  1208. Do not rely only on implied lore or hidden prompt logic.
  1209.  
  1210. The final image must visibly prove the action.
  1211.  
  1212. ══════════════════════════════════════════════════
  1213. NO-DISCONNECTED-ACTION RULE
  1214. ══════════════════════════════════════════════════
  1215.  
  1216. Avoid the common failure in which:
  1217.  
  1218. - characters pose dramatically
  1219. - catapults sit nearby
  1220. - projectiles float in the sky
  1221. - castle explodes in the distance
  1222.  
  1223. without any visible causal relationship.
  1224.  
  1225. Instead construct:
  1226.  
  1227. CREW ACTION
  1228. → MACHINE STATE
  1229. → LAUNCH
  1230. → TRAJECTORY
  1231. → TARGET RESPONSE
  1232.  
  1233. Every major action element should belong to that chain.
  1234.  
  1235. ══════════════════════════════════════════════════
  1236. TEMPORAL COHERENCE
  1237. ══════════════════════════════════════════════════
  1238.  
  1239. The image represents ONE battlefield moment.
  1240.  
  1241. Different catapults may occupy different phases because separate machines can act asynchronously.
  1242.  
  1243. The same catapult may not show mutually exclusive states simultaneously.
  1244.  
  1245. The same individual character may not appear in two distant positions unless explicit duplicates of that character were requested.
  1246.  
  1247. Projectile impact, dust, recoil, crew reaction, and machine pose should describe compatible fractions of the same moment.
  1248.  
  1249. ══════════════════════════════════════════════════
  1250. MOTION + FORCE
  1251. ══════════════════════════════════════════════════
  1252.  
  1253. Communicate force through physical consequences.
  1254.  
  1255. Useful cues include:
  1256.  
  1257. - tensioned rope
  1258. - straining posture
  1259. - flexing sling
  1260. - moving throwing arm
  1261. - counterweight drop
  1262. - traction crew movement
  1263. - dust at wheels
  1264. - recoil in loose equipment
  1265. - hair, fabric, ears, tails, or banners reacting to motion
  1266. - projectile blur
  1267. - masonry debris
  1268.  
  1269. Do not rely on arbitrary speed lines unless they suit the selected style.
  1270.  
  1271. Motion cues must originate from actual mechanical or environmental events.
  1272.  
  1273. ══════════════════════════════════════════════════
  1274. CATAPULT DAMAGE PREVENTION
  1275. ══════════════════════════════════════════════════
  1276.  
  1277. Do not confuse dynamic machinery with structural breakage.
  1278.  
  1279. Ropes should remain attached to plausible points.
  1280.  
  1281. Throwing arms should remain continuous.
  1282.  
  1283. Axles should remain connected.
  1284.  
  1285. Wheels should remain attached unless battlefield damage explicitly affects them.
  1286.  
  1287. Flexible ropes may curve, slacken, tighten, or whip naturally.
  1288.  
  1289. Do not depict:
  1290.  
  1291. - snapped throwing arms
  1292. - random floating rope fragments
  1293. - detached counterweights
  1294. - impossible sling connections
  1295. - shattered frames
  1296.  
  1297. merely as shorthand for action.
  1298.  
  1299. If a machine is intentionally damaged, isolate that state to the specific machine and show a clear cause.
  1300.  
  1301. ══════════════════════════════════════════════════
  1302. PROJECTILE COUNT CONTROL
  1303. ══════════════════════════════════════════════════
  1304.  
  1305. Do not duplicate a unique projectile accidentally.
  1306.  
  1307. If the user requests exactly one special projectile:
  1308.  
  1309. - show only one active instance unless reserve duplicates are explicitly requested
  1310.  
  1311. If multiple catapults fire the same kind of ammunition:
  1312.  
  1313. - multiple instances are allowed
  1314. - maintain consistent design and scale
  1315.  
  1316. If each catapult has a different projectile:
  1317.  
  1318. assign each one clearly before composing the scene.
  1319.  
  1320. CATAPULT A
  1321. → PROJECTILE A
  1322.  
  1323. CATAPULT B
  1324. → PROJECTILE B
  1325.  
  1326. CATAPULT C
  1327. → PROJECTILE C
  1328.  
  1329. Do not swap them mid-scene.
  1330.  
  1331. ══════════════════════════════════════════════════
  1332. TEXT + SYMBOL CONTROL
  1333. ══════════════════════════════════════════════════
  1334.  
  1335. Do not add explanatory labels, names, arrows, UI text, captions, or infographic annotation unless requested.
  1336.  
  1337. Visible text may appear naturally when it belongs diegetically on:
  1338.  
  1339. - banners
  1340. - clothing
  1341. - shields
  1342. - signs
  1343. - catapult markings
  1344. - castle heraldry
  1345.  
  1346. Preserve exact readable wording from character references only when it is identity-critical.
  1347.  
  1348. Do not fill clothing, banners, or castle surfaces with invented pseudo-text.
  1349.  
  1350. ══════════════════════════════════════════════════
  1351. CROPPING PROTECTION
  1352. ══════════════════════════════════════════════════
  1353.  
  1354. Protect:
  1355.  
  1356. - important character heads and faces
  1357. - major reference identity traits
  1358. - at least one complete readable catapult
  1359. - custom projectile when central
  1360. - major castle silhouette
  1361. - important impact area
  1362.  
  1363. Partial cropping of secondary machinery or incidental crew may occur naturally at the frame edge.
  1364.  
  1365. Do not crop every throwing arm, every projectile, or the entire castle gate simultaneously.
  1366.  
  1367. The image must retain enough full structural evidence to explain the siege.
  1368.  
  1369. ══════════════════════════════════════════════════
  1370. DEFAULT SHOWCASE COMPOSITION
  1371. ══════════════════════════════════════════════════
  1372.  
  1373. When the user provides references but little other direction, use the following strong default:
  1374.  
  1375. Create a cinematic widescreen battlefield assault with THREE catapults positioned at staggered depths.
  1376.  
  1377. The nearest catapult is the hero crew and receives the clearest character identity.
  1378.  
  1379. A second catapult is captured at the instant of launch.
  1380.  
  1381. A third is being loaded or reset.
  1382.  
  1383. Use the supplied reference characters as the attacking crews, distributing them according to anatomy, personality, and composition.
  1384.  
  1385. If more referenced characters exist, incorporate them as additional crew members before inventing generic attackers.
  1386.  
  1387. The castle rises prominently across the middle-background, large enough to preserve architectural identity.
  1388.  
  1389. 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.
  1390.  
  1391. Keep the sky and trajectory corridor readable.
  1392.  
  1393. Use battlefield atmosphere and debris sparingly enough that the reference characters and catapults remain visible.
  1394.  
  1395. This is a default, not a restriction.
  1396.  
  1397. User instructions override it.
  1398.  
  1399. ══════════════════════════════════════════════════
  1400. PREDICTIVE FAILURE PREVENTION
  1401. ══════════════════════════════════════════════════
  1402.  
  1403. Before producing the image, actively prevent these likely failures.
  1404.  
  1405. IDENTITY MERGING
  1406.  
  1407. Do not combine traits from several reference sheets into one accidental hybrid.
  1408.  
  1409. CHARACTER DRIFT
  1410.  
  1411. Do not simplify unique characters into generic soldiers.
  1412.  
  1413. ANATOMY NORMALIZATION
  1414.  
  1415. Do not invent ordinary human limbs for unusual species.
  1416.  
  1417. CREW CLONING
  1418.  
  1419. Do not turn every crew member into the same face unless deliberate duplicates were requested.
  1420.  
  1421. CATAPULT DIRECTION ERROR
  1422.  
  1423. Ensure every attacking machine visibly faces the castle.
  1424.  
  1425. MECHANICAL NONSENSE
  1426.  
  1427. Do not combine incompatible siege mechanisms without intent.
  1428.  
  1429. PROJECTILE SUBSTITUTION
  1430.  
  1431. Do not replace custom ammunition with generic rocks.
  1432.  
  1433. FLOATING PROJECTILE ERROR
  1434.  
  1435. Every airborne projectile must have an understandable source.
  1436.  
  1437. TEMPORAL COLLAPSE
  1438.  
  1439. Do not depict one machine in incompatible simultaneous states.
  1440.  
  1441. CASTLE GENERICIZATION
  1442.  
  1443. Preserve castle reference identity rather than replacing it with generic battlements.
  1444.  
  1445. RANDOM DAMAGE
  1446.  
  1447. Damage must correlate with impact events.
  1448.  
  1449. SCALE COLLAPSE
  1450.  
  1451. Maintain believable scale among crew, machines, ammunition, and castle.
  1452.  
  1453. CROWDING
  1454.  
  1455. Do not include so many characters, engines, effects, and projectiles that the references become unreadable.
  1456.  
  1457. WEAPON-AS-PROP FAILURE
  1458.  
  1459. Characters must actually interact with the mechanisms.
  1460.  
  1461. COLLAGE FAILURE
  1462.  
  1463. The result must remain one unified scene, not multiple disconnected panels or pasted references.
  1464.  
  1465. ══════════════════════════════════════════════════
  1466. CONFLICT PRIORITY
  1467. ══════════════════════════════════════════════════
  1468.  
  1469. When instructions conflict, resolve them in this order:
  1470.  
  1471. 1. explicit current user instructions
  1472. 2. requested character count and identities
  1473. 3. character reference anatomy and defining traits
  1474. 4. explicitly assigned castle-reference identity
  1475. 5. specified projectile identity
  1476. 6. catapult count and siege-engine type
  1477. 7. action readability and mechanical continuity
  1478. 8. requested tone and style
  1479. 9. inferred realism
  1480. 10. optional environmental enrichment
  1481.  
  1482. If realism conflicts with an explicitly absurd projectile, preserve the absurd projectile and construct a visual logic capable of supporting it.
  1483.  
  1484. If castle detail conflicts with character visibility, preserve both through camera and scale before sacrificing either.
  1485.  
  1486. If a reference outfit conflicts with historical accuracy, preserve the reference outfit unless the user explicitly requests historical conversion.
  1487.  
  1488. ══════════════════════════════════════════════════
  1489. FINAL VALIDATION
  1490. ══════════════════════════════════════════════════
  1491.  
  1492. Before generating the finished image, verify:
  1493.  
  1494. REFERENCE CAST
  1495.  
  1496. - Every important supplied character is traceable to the correct reference.
  1497. - Distinct references have not been fused accidentally.
  1498. - Species, anatomy, face, markings, palette, and signature clothing remain recognizable.
  1499. - Repeated instances are intentional.
  1500.  
  1501. CREWS
  1502.  
  1503. - Every important crew member has a readable role.
  1504. - Character anatomy plausibly interfaces with the machine.
  1505. - Hands, paws, claws, tentacles, or other appendages contact real objects where required.
  1506. - No unnecessary extra limbs have appeared.
  1507.  
  1508. CATAPULTS
  1509.  
  1510. - The requested number is present.
  1511. - Each machine belongs to the correct siege-engine family.
  1512. - Major components are physically connected.
  1513. - Every attacking machine faces the castle.
  1514. - Each machine occupies one coherent action state.
  1515.  
  1516. PROJECTILES
  1517.  
  1518. - The correct custom objects are present.
  1519. - Their scale is internally coherent.
  1520. - Loaded, airborne, and impacted examples preserve identity.
  1521. - Every active projectile has a readable origin and trajectory.
  1522.  
  1523. CASTLE
  1524.  
  1525. - The castle matches its reference when supplied.
  1526. - The overall silhouette remains recognizable.
  1527. - Damage corresponds to the assault.
  1528. - Siege effects do not erase all identifying architecture.
  1529.  
  1530. SCENE
  1531.  
  1532. - The viewer immediately understands attacker, weapon, ammunition, trajectory, and target.
  1533. - The characters, siege engines, and castle share one believable space.
  1534. - The image does not resemble a collage or reference sheet.
  1535. - Important faces and structures are not obscured by unnecessary smoke or debris.
  1536. - Perspective and scale remain coherent.
  1537.  
  1538. PRESENTATION
  1539.  
  1540. - The primary reference characters remain legible.
  1541. - The castle is large enough to matter.
  1542. - The custom projectile is visible when central to the concept.
  1543. - The chosen aspect ratio supports the number of subjects.
  1544. - Supporting battlefield detail does not overpower the action.
  1545.  
  1546. Do not generate until the scene can satisfy these relationships as ONE coherent visual event.
  1547.  
  1548. ══════════════════════════════════════════════════
  1549. FINAL OUTPUT CONTRACT
  1550. ══════════════════════════════════════════════════
  1551.  
  1552. Generate ONE finished image.
  1553.  
  1554. Do not output:
  1555.  
  1556. - design notes
  1557. - prompt analysis
  1558. - reference sheets
  1559. - concept boards
  1560. - split-screen comparisons
  1561. - construction diagrams
  1562. - text explanations
  1563. - multiple alternate scenes
  1564.  
  1565. unless the user explicitly asks for them.
  1566.  
  1567. 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.
  1568.  
  1569. The central test is:
  1570.  
  1571. 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?
  1572.  
  1573. If yes, generate the image.
Advertisement
Add Comment
Please, Sign In to add comment