Untitled
you are strictly responsible for the creation of the assets, ignore anything else, just use it as context
I am developing Runebound, a mobile-friendly 2D side-view exploration and action game with mining, crafting, equipment, spells, enemies, biomes, and bosses. Solving math problems is part of casting spells.
I want you to undertake two substantial tasks:
1. Regenerate the game’s boss characters, their animations, and their visual effects, with a consistent art style and much stronger animation quality. Also regenerate the playable character and its animation set so the characters belong to the same visual world.
2. Design and generate approximately 600 NEW spells, with varied mechanics, silhouettes, animation, movement patterns, purposes, and progression roles.
Treat this as a production task. Develop actual usable assets and structured specifications, work through them in recoverable batches, and inspect the animations in motion. Do not stop after a list of ideas or a few example images.
1. Understand the game before generating assets
Runebound is a side-view sandbox action game inspired by the broad experience of exploring, mining, crafting, and fighting in games such as Terraria, while having its own characters, artwork, progression, and math-based spellcasting.
Players can:
- Walk, jump, aim, and fight.
- Explore the surface, caves, and deeper biomes.
- Mine blocks and gather materials.
- Craft equipment and improve their combat capabilities.
- Find and equip spells.
- Fight biome-specific enemies and bosses.
- Solve math problems to cast magic while the world continues moving.
The game should remain readable and comfortable on a phone. Combat effects need to look impressive while allowing players to see enemies, terrain, incoming attacks, and their own character.
Spells are associated with problems. For example, a weak fire spell can involve solving a quadratic equation, with coefficients changing between casts. More advanced spells can involve harder problems. The game is not intended to interrupt combat with a full mathematics lesson.
Players should be able to move, jump, aim, and interact with the answer interface during combat. Design animations around that freedom. Do not assume every spell requires the player to stand still through a long animation.
If I provide the project, inspect its actual code, assets, animation definitions, coordinate system, rendering scale, and existing mechanics first. The current project and my explicit instructions take priority over assumptions in this prompt.
Do not invent existing implementation details. Clearly distinguish what you found in the project from new designs you propose.
2. Overall visual direction
Create original, cohesive pixel art suitable for a detailed 2D action game.
Aim for:
- Recognizable silhouettes.
- Strong character identity.
- Deliberate pixel placement.
- Consistent pixel density.
- Materials that read clearly at gameplay scale.
- Lighting and shading that fit the existing game.
- Expressive animation with convincing weight.
- Distinct visual identities for different biomes and magical families.
Avoid having some assets look like tiny retro sprites while others look like reduced-resolution paintings.
Use the game’s existing artwork as the starting point when available. Improve its quality while preserving recognizable identities.
Do not copy Terraria sprites or assets from other games.
Keep backgrounds transparent. Avoid baked-in checkerboards, accidental borders, isolated pixels, halos, and effects clipped by the canvas.
Check every asset against both dark and bright backgrounds.
3. Boss roster and regeneration scope
The known boss roster includes:
1. Briarback Behemoth.
2. Furnace Tortoise.
3. Gearmaw Centipede.
4. Bloom Tyrant.
5. Crown of the Deep.
6. Glass Leviathan.
7. Bell Colossus.
8. Star-Eating Roc.
9. Mire Devourer.
10. Rimehorn Matriarch.
Verify the complete roster in the project and include any additional bosses already present.
For every boss, regenerate the complete visual package required by its actual mechanics:
- Main character sprites.
- Idle or resting movement.
- Movement and locomotion.
- Turning or directional variants where needed.
- Attack anticipation.
- Attack execution.
- Recovery.
- Damage reactions.
- Stagger or vulnerability states.
- Phase transitions.
- Spawn or entrance.
- Defeat and disappearance.
- Projectiles.
- Summoned creatures.
- Persistent hazards.
- Impact effects.
- Environmental effects.
- Boss-specific magic and attack telegraphs.
Do not produce a single generic attack animation and reuse it for every move.
For segmented or exceptionally large bosses, use separate components when appropriate. A whole creature does not need to fit into one enormous sprite sheet.
Account for attachment points, pivots, segment connections, draw order, and collision alignment.
Furnace Tortoise
Preserve these established mechanics:
- It is enormous, tall enough to occupy the vertical space of its hell arena.
- It moves horizontally in a straight line, chasing the player left or right.
- It seals off the hell area with unbreakable blocks during the encounter.
- When the player dies, the boss disappears and the seal is removed.
- It spits lava balls.
- It summons smaller turtles that curl into balls and launch themselves at the player.
Its animation should communicate overwhelming weight and forward pressure.
Generate the necessary visuals for its locomotion, lava attack, smaller turtles, curling transformation, launch, impacts, seal formation, and encounter ending.
A charging turtle should visibly compress, curl, and accelerate. Its rolling state must have a readable silhouette.
Glass Leviathan
Preserve its fast movement and multiple attack patterns, including rapid vertical charges toward the player.
Its animation should convey speed without making its location or attack direction impossible to understand.
Provide distinct anticipation, acceleration, travel, braking or turning, and recovery where the mechanics require them.
If its body is segmented, make the segment motion continuous and connected. Avoid visible gaps and disconnected pieces.
Glass-related effects should remain readable on mobile screens rather than becoming an indistinct cloud of pale particles.
Gearmaw Centipede
Preserve these mechanics:
- Damage is concentrated on its weak points.
- As it loses sections and becomes smaller, it moves increasingly fast.
Create a coherent segmented body system with readable joints and consistent attachment points.
Weak points should be recognizable through shape, movement, exposure, or contrast. Support any existing open, protected, damaged, and destroyed states.
Animate shortening and segment destruction cleanly. Do not leave floating fragments attached to an invisible body.
Its movement should communicate increasing aggression as its remaining body becomes shorter.
Bloom Tyrant
Preserve these mechanics:
- It creates flowers beneath the player.
- Remaining in their area too long can trap the player.
- It throws multiple flower projectiles.
- It also uses physical attacks.
Create visually distinct stages for flower emergence, warning, growth, activation, trapping, and disappearance.
The player should be able to recognize a developing trap before it fully activates.
Differentiate decorative petals, damaging projectiles, and trapping plants through their silhouettes and movement.
Give physical attacks convincing plant-like weight, bending, recoil, and follow-through.
Crown of the Deep
Preserve these mechanics:
- It reduces the effectiveness of torches and other light.
- It obscures part of the player’s vision.
- It creates spider-like traps around the player.
- Touching a trap can immobilize the player.
- It charges when the player becomes trapped.
Generate separate visuals for the boss, trap placement, active traps, capture, charge anticipation, charge movement, impact, and release or trap destruction.
Darkness should feel threatening while retaining enough information to understand immediate attacks.
Do not make the encounter unreadable by covering everything with opaque black effects.
Bell Colossus
This boss is so enormous that its complete body should not need to fit on screen.
Use separate body parts and attack components where appropriate, especially its enormous feet and legs.
Preserve its implemented mechanics after inspecting the project. The known scale requirement must remain central to its presentation.
Its attacks should communicate:
- A huge mass moving above or outside the camera.
- A readable warning.
- A forceful downward impact.
- Ground contact.
- Shockwaves or other implemented impact effects.
- A convincing recovery or withdrawal.
The boss also needs a signature dropped spell that summons a spectral version of its enormous foot to smash the ground. This spell is a required part of the new spell collection.
Remaining bosses
For Briarback Behemoth, Star-Eating Roc, Mire Devourer, and Rimehorn Matriarch, inspect the project or supplied references before defining their exact attack animations.
Their names are not sufficient evidence of their existing mechanics.
Preserve established behaviors and design supporting animations around them. If information is unavailable, identify the missing behavior and label new mechanics as proposals.
Boss progression
Boss summoning is biome-specific.
Progression bosses use summoning items that require drops from the preceding boss. The two independent nest/lair bosses are exceptions.
Verify the current progression order and which bosses are the exceptions in the project before assigning drops or unlocks.
Regenerating artwork must not silently change summoning rules, progression, encounter cleanup, or boss behavior.
4. Playable character animation
Regenerate the playable character in the same visual language as the bosses and effects.
Cover the states actually used by the game, including:
- Idle.
- Walking and running if distinct.
- Jump takeoff.
- Rising.
- Falling.
- Landing.
- Aiming.
- Casting.
- Mining or tool use.
- Taking damage.
- Death.
- Any existing weapon or interaction states.
Support simultaneous movement and aiming where the game allows it.
If the engine uses layered animation, retain suitable separation between legs, torso, arms, tools, weapons, and equipment.
Check that feet contact the ground consistently. Avoid sliding, sinking, inconsistent body size, or unexplained changes in the character’s center of mass.
Do not add a dodge, dash, or other player ability merely because an animation set commonly contains one.
5. Create approximately 600 genuinely new spells
The goal is a broad magic system with substantial variety.
Do not create hundreds of recolors of the same projectile.
The collection should vary across:
- Summoned object or creature.
- Casting origin.
- Targeting method.
- Flight path.
- Timing.
- Attack shape.
- Number of stages.
- Enemy interaction.
- Terrain interaction.
- Persistence.
- Combat purpose.
- Risk and reward.
- Progression tier.
A fireball and an iceball with identical movement and behavior do not provide enough variety on their own.
Elemental variants are useful when they also change meaningful behavior.
Treat these as 600 additions. Inventory existing spells so the new collection does not accidentally count old spells toward the target.
Use the following planning allocation, adjusting individual concepts if necessary while keeping the total near 600:
Primary family| Target count
Conjured weapons and weapon formations| 150
Dark, shadow, curse, and void magic| 90
Skull, bone, and spirit magic| 50
Bees, insects, and swarm magic| 60
Phantom versions of monsters| 90
Elemental, natural, and arcane phenomena| 60
Defensive, mobility, control, and utility magic| 40
Boss-derived and hybrid signature magic| 60
Total| 600
Each spell gets one primary family so the totals do not double-count hybrid spells.
6. Conjured weapons: a major priority
I specifically want spells that summon weapons and throw, swing, launch, position, or command them in many different ways.
Prioritize:
- Scythes.
- Swords.
- Spears.
Expand with compatible weapons such as axes, hammers, daggers, lances, bows, arrows, chains, shields, and floating blades when they add meaningful variety.
Explore behaviors such as:
- A single scythe spinning forward.
- A scythe sweeping a wide arc around the player.
- A thrown scythe returning along a curved path.
- A stationary scythe rotating as an area hazard.
- Scythes rising from ground runes in a staggered fan.
- A giant spectral scythe executing one heavy strike.
- Swords orbiting the player before launching individually.
- Swords raining onto selected ground positions.
- A sword appearing behind an enemy and thrusting toward it.
- A formation of blades firing in sequence.
- A spear piercing through several enemies.
- Spears emerging from the ground.
- A spear suspended in the air before a delayed launch.
- A fan of spears converging on one target.
- A weapon ricocheting between valid targets.
- A blade splitting after its first impact.
- A weapon leaving a lingering trail that becomes a second attack.
- A shield intercepting an attack and then launching forward.
These examples establish the desired breadth. Expand beyond them.
Pay attention to orientation. A spear should travel with an understandable point-first trajectory. A scythe’s rotating blade should trace a coherent arc.
A conjured weapon should visibly materialize, act, and disappear or resolve. Do not make every spell an object that simply appears and fades.
7. Dark, shadow, curse, and void magic
Include substantial dark magic with varied mechanical identities.
Explore:
- Shadow hands.
- Grasping tendrils.
- Dark lances.
- Crawling ground shadows.
- Curse marks.
- Delayed detonations.
- Chains connecting targets.
- Pulling vortices.
- Shadow clones.
- Portals that redirect attacks.
- Rifts that release creatures or weapons.
- Areas of weakening or control.
- Attacks that grow through successive hits.
- Marks consumed by another spell.
- Dark constructs with short independent behaviors.
Dark magic should have readable boundaries and distinctive silhouettes.
Avoid making the entire family identical purple smoke.
Vary its visual materials: ink-like shadow, fractured void, spectral fabric, sharp obsidian forms, runic chains, and other coherent treatments.
Any lifesteal, weakening, damage-over-time, or resource interaction must fit the game’s actual systems or be clearly identified as a proposed addition.
8. Skulls, bones, and spirits
I specifically want spells that summon skulls.
Create meaningful variation in their behavior:
- A skull pursuing a target.
- Several skulls orbiting before launching.
- A large skull releasing a cone attack.
- Skulls travelling along a wave.
- A skull leaving spectral fire.
- A skull emerging from a portal.
- A skull that breaks into smaller spirits.
- A circle of skulls closing inward.
- Bone spears.
- Skeletal hands.
- Bone cages.
- Spirit processions.
- A skeletal jaw snapping at a selected position.
Give summoned skulls personality through their motion, jaw movement, gaze, and anticipation.
Differentiate tracking spirits from straight projectiles and persistent summons.
9. Bees, insects, and swarms
I specifically want bee summons and related swarm spells.
Explore:
- A single large bee.
- Several small bees emerging in sequence.
- A swarm that follows a target.
- Bees orbiting defensively.
- A spectral hive producing a limited number of bees.
- Bees diving one after another.
- A queen directing a formation.
- Stingers firing from a hovering summon.
- A swarm gathering before a concentrated rush.
- A swarm spreading between nearby enemies.
Expand into other insects when useful: moths, beetles, hornets, mantises, or spiders.
Make their flight patterns and attack roles distinct.
For mobile performance, represent large swarms efficiently rather than requiring hundreds of independent animated entities.
10. Phantom versions of monsters
I want magic that summons phantom versions of monsters.
Use the actual game’s monsters as source material when available.
Examples of suitable identities include phantom:
- Slimes.
- Wolves.
- Ravens.
- Serpents.
- Spiders.
- Mantises.
- Knights.
- Other biome creatures already present in Runebound.
A phantom should retain recognizable anatomy and behavior from its source creature while clearly reading as a player-created summon.
Do not make all phantom spells identical homing missiles.
Possible behaviors include:
- A wolf rushing across the ground and lunging.
- A raven diving from above.
- A serpent travelling in an undulating path.
- A slime bouncing toward a target.
- A spider establishing a temporary web.
- A mantis executing a rapid sequence of slashes.
- A knight performing a thrust or defensive intercept.
- Several phantoms attacking in a timed procession.
Distinguish a brief attack manifestation from a persistent companion. Define lifetime, targeting, and cleanup for each.
11. Boss-derived spells and hybrids
Boss rewards should feel connected to the creature defeated.
The required Bell Colossus reward summons its spectral foot to stomp the ground.
Its animation needs:
1. A readable summoning cue.
2. The enormous foot materializing above the target area.
3. A forceful downward stomp.
4. Visible ground contact.
5. An impact or shockwave.
6. Withdrawal or dissolution.
Do not replace this concept with an ordinary small projectile.
Develop additional boss-derived spells from verified mechanics, such as rolling turtle summons, flower traps, spectral segments, or glass charges.
Use hybrids to create new interactions:
- A scythe releasing skulls after completing its arc.
- A phantom raven carrying a curse.
- A spear opening a portal on impact.
- A summoned flower launching spectral bees.
- A sword formation responding to a marked target.
A hybrid must have a coherent visual sequence and combat purpose. Simply combining two particle colors is insufficient.
12. Spell versatility and progression
Organize the collection across early, middle, and late progression.
Early spells should be understandable and useful. Later spells can introduce more stages, targeting decisions, combinations, and specialized roles.
Higher-tier magic does not always need more projectiles or larger explosions.
A powerful spell can gain strength through precision, timing, control, protection, efficient targeting, or interaction with another spell.
Provide roles such as:
- Single-target damage.
- Crowd clearing.
- Piercing.
- Anti-air.
- Ground control.
- Defensive interception.
- Knockback.
- Trapping.
- Delayed burst.
- Sustained pressure.
- Persistent summons.
- Close-range protection.
- Long-range precision.
- Exploration utility where supported.
Keep damage and resource values relative until the existing combat formulas are known.
Do not introduce cooldowns, mana costs, invulnerability, terrain destruction, or other systems without checking whether the game already supports them.
For the math component, recommend a compatible problem family and relative difficulty. Keep the animation and attack behavior separate from the problem generator so changing coefficients does not require new artwork.
Preserve existing problem-selection and repeated-cast rules.
13. Specification required for every spell
Create a structured record containing:
- Unique ID.
- Name.
- Primary family and secondary tags.
- Short concept.
- Combat role.
- Progression tier.
- Acquisition source.
- Summoned object or creature.
- Targeting method.
- Spawn position.
- Movement path.
- Attack stages and their timing.
- Hit behavior.
- Terrain interaction.
- Lifetime and disappearance.
- Animation states.
- Required sprite sheets and effects.
- Frame dimensions, frame counts, and playback rates.
- Pivot and attachment points.
- Loop and transition rules.
- Relative balance notes.
- Suggested math problem family and difficulty.
- Performance considerations.
- Asset paths and implementation status.
Also write an asset-generation prompt for each spell or reusable component.
Describe motion concretely. “Epic magical animation” is insufficient. Specify what appears, how it moves, what changes on contact, and how it ends.
14. Animation production requirements
Choose frame counts according to the motion. Do not force everything into eight frames.
For every animation:
- Preserve character proportions.
- Maintain consistent pivots.
- Keep important movement inside the canvas.
- Include enough padding for weapons and effects.
- Use intentional timing.
- Make anticipation and recovery readable.
- Preserve continuity between frames.
- Make loops close cleanly.
- Avoid accidental flickering.
- Avoid unexplained changes in anatomy or weapon shape.
- Avoid frame-to-frame scale changes unless intentional.
- Keep contact points consistent.
Use translation, rotation, skeletal motion, and particles in the engine where appropriate. Do not bake every possible projectile direction into a separate sheet.
Separate reusable projectiles, trails, impacts, and casting effects when that improves quality and performance.
Reuse supporting components without making the final spells mechanically interchangeable.
15. Build and use an animation quality-control system
Judge animations in motion, not only as contact sheets.
Provide a visualizer that supports:
- Intended-speed playback.
- Slow playback.
- Pause and frame stepping.
- Several background colors.
- Pixel-perfect zoom.
- In-game scale.
- Pivot and frame-boundary overlays.
- Original versus regenerated comparison.
- Full spell sequences with movement and impacts.
Evaluate:
- Silhouette readability.
- Anatomy and shape consistency.
- Motion continuity.
- Weight and impact.
- Anticipation.
- Follow-through.
- Timing.
- Loop quality.
- Transparency.
- Canvas clipping.
- Ground contact.
- Gameplay readability.
- Style consistency.
- Performance cost.
Use a consistent scoring rubric and record specific defects.
A score alone does not establish quality. Save the evidence and explain what changed between revisions.
Reject animations with severe clipping, broken anatomy, unstable pivots, visible background debris, disconnected segments, or missing attack stages even if their average score appears high.
Inspect every asset technically. Visually review every distinct animation, including assembled sequences.
Iterate until the assets meet the agreed standard or clearly record the remaining limitation.
16. Preserve originals and work in batches
Keep all original assets recoverable.
Create a manifest connecting:
- Original asset.
- New version.
- Boss or spell ID.
- Generation settings when available.
- Animation configuration.
- Evaluation.
- Revisions.
- Final selected version.
- In-game references.
Work in manageable batches. Fully complete and inspect a representative initial batch before scaling production.
Start with examples that test different challenges: a segmented boss, a heavy stomp, a spinning scythe, a thrusting spear, a swarm, a phantom monster, and a persistent trap.
Then continue through the full collection with checkpoints.
Report actual counts of designed, generated, inspected, revised, and integrated assets. Do not describe a text description or placeholder as a finished animated spell.
17. Integration and delivery
If you can access the game project, integrate the approved assets using its existing architecture and verify them in gameplay.
Keep visual changes separate from unintended changes to combat rules.
Verify:
- Ground alignment.
- Sprite direction.
- Attack timing.
- Hitbox alignment.
- Boss scale.
- Segment connections.
- Phase transitions.
- Summon cleanup.
- Projectile lifetime.
- Death and encounter cleanup.
- Mobile readability.
- Performance with several simultaneous effects.
Do not add explanatory text or tutorial popups to the game unless I explicitly request them. Communicate through animation, silhouettes, and appropriate visual feedback.
Deliver:
- Complete regenerated boss packages.
- Updated playable-character assets.
- Approximately 600 new spell records.
- The generated spell sprites and effects.
- Animation metadata.
- A searchable animated gallery.
- Quality-control results.
- A manifest linking all assets to their intended uses.
- Clear installation or integration instructions.
- An honest list of anything still unfinished.
If you lack a required generation tool, project file, or reference, state the precise dependency and continue with independent work. Never claim to have generated, inspected, or integrated an asset you have only described.
Begin by inspecting the available project and references, inventorying the existing bosses and spells, and establishing the visual and technical standards. Then produce the representative batch, evaluate it in motion, improve it, and continue through the remaining production work.
Featured
Advertisement
Category
Action