Gremsworkshop

16-BIT RPG RANDOM BOSS BATTLE

Sep 5th, 2026
89
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.19 KB | None | 0 0
  1. # 16-BIT RPG — RANDOM BOSS BATTLE
  2.  
  3. Use the four supplied character references as the absolute visual authority for each character’s identity, colors, species, anatomy, face, hair, equipment motifs, personality, and defining features.
  4.  
  5. Create a dramatic widescreen **16-bit RPG boss-battle screenshot** featuring exactly four recognizable characters.
  6.  
  7. ## CHARACTER ROLES
  8.  
  9. - **REFERENCE 1:** Player-party character
  10. - **REFERENCE 2:** Player-party character
  11. - **REFERENCE 3:** Player-party character
  12. - **REFERENCE 4:** The boss
  13.  
  14. The first three characters must appear together as a three-member adventuring party fighting the fourth character.
  15.  
  16. Do not swap these roles. Do not add, duplicate, combine, or omit characters.
  17.  
  18. ## OPTIONAL CHARACTER NAMES
  19.  
  20. If any character’s name is missing, unclear, incorrect, or difficult to read in their reference sheet, the user may supply the correct name here:
  21.  
  22. - **REFERENCE 1 NAME:** [Optional]
  23. - **REFERENCE 2 NAME:** [Optional]
  24. - **REFERENCE 3 NAME:** [Optional]
  25. - **REFERENCE 4 / BOSS NAME:** [Optional]
  26.  
  27. These fields provide names only. They do not change the characters’ roles, reference order, identities, appearances, abilities, or boss transformation.
  28.  
  29. Use every supplied name exactly as written, including its spelling, capitalization, punctuation, and spacing.
  30.  
  31. Use the following name priority:
  32.  
  33. 1. If an optional name is supplied above, use it.
  34. 2. Otherwise, use a name that is clearly readable in the corresponding reference.
  35. 3. If neither provides a reliable name, leave that character’s interface name field blank.
  36.  
  37. A supplied name overrides unclear or conflicting text inside the reference sheet, but it changes only the displayed interface name.
  38.  
  39. Never guess, shorten, translate, correct, replace, or invent a character name.
  40.  
  41. ## THE THREE-CHARACTER PARTY
  42.  
  43. Translate the first three characters into detailed, recognizable 16-bit battle sprites.
  44.  
  45. Preserve each character’s:
  46.  
  47. - Face and hairstyle
  48. - Species traits and anatomy
  49. - Signature colors
  50. - Clothing or armor identity
  51. - Important accessories
  52. - Recognizable weapons, equipment, or powers
  53. - Relative height and body proportions
  54. - Individual personality and combat style
  55.  
  56. Give every party member a distinct action during the battle. They may attack with a weapon, cast magic, defend, heal, use an item, prepare a special ability, or react to the boss.
  57.  
  58. Their abilities should be intelligently inferred from their references. Do not force every character into a generic warrior, rogue, or mage role if another combat style suits them better.
  59.  
  60. Keep all three sprites large and clear enough to remain recognizable.
  61.  
  62. ## PROCEDURAL BOSS TRANSFORMATION
  63.  
  64. Transform the fourth referenced character into a randomly selected, spectacular 16-bit RPG boss form.
  65.  
  66. Do not ask the user to choose the boss form.
  67.  
  68. Analyze the fourth character’s appearance, species, personality, powers, equipment, motifs, colors, and overall energy. Then invent one boss transformation that feels uniquely derived from that character.
  69.  
  70. Possible boss forms include, but are not limited to:
  71.  
  72. - Colossal armored warlord
  73. - Enormous magical beast
  74. - Corrupted final form
  75. - Elemental titan
  76. - Mechanical siege monster
  77. - Eldritch manifestation
  78. - Living fortress
  79. - Mutated creature
  80. - Giant spectral apparition
  81. - Multi-limbed combat form
  82. - Floating weapon construct
  83. - Shadow or nightmare form
  84. - Ancient guardian
  85. - Monstrous transformation
  86. - Giant disembodied head
  87. - Another original form intelligently inspired by the character
  88.  
  89. These are possibilities, not a required rotation. Select exactly one cohesive boss concept for each generation.
  90.  
  91. A giant head is permitted, but it must be only one possible outcome—not the default result.
  92.  
  93. ## BOSS IDENTITY PRESERVATION
  94.  
  95. The boss transformation may radically change the character’s scale, body, clothing, armor, equipment, or physical form, but it must not become an unrelated generic monster.
  96.  
  97. Preserve multiple unmistakable identity anchors from Reference 4, such as:
  98.  
  99. - Recognizable facial features
  100. - Hair, horns, ears, eyes, markings, or silhouette
  101. - Signature colors
  102. - Distinctive armor or clothing motifs
  103. - Important accessories
  104. - Familiar weapon elements
  105. - Symbols or emblems
  106. - Character-specific magic
  107. - Personality and expression
  108.  
  109. Translate these features naturally into the selected boss form.
  110.  
  111. If the character becomes mechanical, bestial, elemental, spectral, or monstrous, their original identity must remain immediately apparent. Viewers familiar with the character should recognize them before reading the boss name.
  112.  
  113. The boss should feel like an exaggerated final-battle incarnation of that exact character.
  114.  
  115. ## SCALE AND COMPOSITION
  116.  
  117. Use a classic side-view or three-quarter-view RPG battle composition.
  118.  
  119. Arrange the three party members together on one side of the battlefield and the transformed boss on the opposing side.
  120.  
  121. The boss must be substantially larger and more visually dominant than the party, but its scale should suit the selected transformation. It does not need to be a floating head or occupy the same amount of space in every generation.
  122.  
  123. Show the battle already in progress, with attacks, spells, debris, status effects, hit sparks, environmental reactions, or other readable combat action.
  124.  
  125. Keep the staging clear. Do not hide the characters beneath excessive effects.
  126.  
  127. ## ENVIRONMENT
  128.  
  129. Procedurally select a boss arena that complements the fourth character and their transformation.
  130.  
  131. Possible settings include a ruined castle, magical forest, industrial fortress, volcanic chamber, frozen temple, celestial platform, haunted cathedral, underground laboratory, desert coliseum, corrupted throne room, or another character-derived location.
  132.  
  133. The environment must also be rendered entirely as 16-bit pixel art.
  134.  
  135. ## RPG INTERFACE
  136.  
  137. Include a polished retro RPG battle interface.
  138.  
  139. The interface may contain:
  140.  
  141. - A large boss health bar
  142. - Three party status panels
  143. - Character portraits or small icons
  144. - HP and MP bars
  145. - Battle commands
  146. - Status-effect symbols
  147. - Turn indicators
  148.  
  149. Display the characters’ names according to the **OPTIONAL CHARACTER NAMES** section.
  150.  
  151. If an optional name has been supplied, reproduce it exactly as written. Otherwise, use a name only when it is clearly readable in the corresponding reference. If no reliable name is available, leave that name field blank rather than inventing one.
  152.  
  153. The name assigned to each reference must remain attached to that same character. Do not move names between party members or assign a party member’s name to the boss.
  154.  
  155. Keep all interface text minimal, correctly spelled, and readable.
  156.  
  157. ## VISUAL STYLE
  158.  
  159. Render the entire image as authentic handcrafted **16-bit pixel art**.
  160.  
  161. This requirement applies to:
  162.  
  163. - Characters
  164. - Boss
  165. - Environment
  166. - Weapons
  167. - Magic
  168. - Lighting
  169. - Smoke
  170. - Fire
  171. - Particles
  172. - Shadows
  173. - Debris
  174. - Interface
  175. - Text
  176. - Portraits
  177.  
  178. Use:
  179.  
  180. - Crisp square pixels
  181. - Deliberate pixel clusters
  182. - Stepped edges
  183. - Limited retro color palettes
  184. - Strong silhouettes
  185. - Sprite-based shading
  186. - Classic 16-bit console-era visual logic
  187. - Detailed but readable animation-frame poses
  188.  
  189. Do not create a smooth modern illustration and place a pixel filter over it.
  190.  
  191. ## FINAL REQUIREMENTS
  192.  
  193. - Landscape 16:9 composition
  194. - Exactly three party characters
  195. - Exactly one boss character
  196. - References 1–3 are always the party
  197. - Reference 4 is always the boss
  198. - Randomly invent the fourth character’s boss form
  199. - Keep the transformed boss unmistakably recognizable
  200. - Give all three party members distinct battle actions
  201. - Make the boss visually dominant
  202. - Preserve relative party proportions
  203. - Use authentic 16-bit pixel art throughout
  204. - Include a readable retro battle interface
  205. - Follow the optional character-name priority exactly
  206. - Keep every supplied name attached to the correct reference
  207. - Reproduce supplied names without changing their spelling
  208. - Leave genuinely unknown name fields blank
  209. - No duplicate or extra characters
  210. - No unrelated generic boss
  211. - No automatic giant-head default
  212. - No invented character names
  213. - No panels or sprite sheets
  214. - No modern 3D rendering
  215. - No painterly or smooth anime rendering
  216. - No blurry pseudo-pixel effect
  217. - No watermark
  218.  
Advertisement
Add Comment
Please, Sign In to add comment