Made with Nano Banana 2 Lite · CC0 · 3 Oct 2026

Flat colour

Generated from: a scene from a small video game about: MORP — MASTER GAME DEVELOPMENT PROMPT Create a complete playable vertical slice for an original 2D mobile-first cooperative fantasy RPG currently code-named MORP. This must feel like a real game prototype that could later grow into a commercial product, not like a tech demo, template, idle game, generic AI RPG, or visual mockup. The player must immediately be able to: Create a character → enter a living town → receive a quest → travel on the world map → enter a local area → encounter enemies → fight → gain XP → obtain loot → equip visible gear → become stronger → return to town → sell/craft/manage equipment → unlock a harder encounter or dungeon. Prioritize polished gameplay, coherent art direction, progression and player identity over raw feature count. --- 1. HIGH-LEVEL GAME CONCEPT MORP is a Western fantasy adventure RPG designed primarily for mobile, with eventual PC support. The game supports solo play as a first-class experience. Each human player controls one persistent hero. Up to four heroes can form a party for difficult content: - Tank - Healer/Support - DPS - DPS For the prototype, AI-controlled party members must be available so every mechanic can be tested without real online players. The game should feel accessible when exploring alone but strongly reward cooperative dungeon play later. Do NOT design the game as an MMO where random players constantly appear around the player. Towns can act as social hubs, but the player's adventure spaces are personal or party-based. --- 2. CORE GAMEPLAY LOOP The primary progression loop is: Character creation → town → accept quests → travel → local exploration → random encounters → combat → XP and loot → equipment upgrades → stronger enemies → elite encounters → dungeons → unique boss loot → return to town → prepare for increasingly difficult regions and dungeons. The core emotional reward is: “I found something powerful, equipped it, I can visibly see it on my character, and now I am strong enough to attempt harder content.” Loot and character progression are the heart of MORP. --- 3. CHARACTER CREATION Start the game with a simple but polished character creation screen. Only human characters are needed initially. Allow: - male/female body presentation - multiple hairstyles - hair color - skin tone - several faces or facial details - name entry The player should feel that this is their personal persistent hero. Initial classes: Warrior Tank / melee damage. Priest Healing / support / holy damage. Rogue Fast physical DPS, critical attacks and utility. Mage Ranged magical DPS and area damage. Each class must have clearly distinct gameplay. Do not overload the prototype with dozens of abilities. Start each class with: - basic attack - two active class abilities - one defensive/support ability - one resource system - one unlockable ability gained through leveling --- 4. CHARACTER PROGRESSION Characters gain XP from enemies, quests, elites and bosses. Implement real level progression. Level-up should feel rewarding with: - animation - sound - visible stat improvements - occasional new ability unlocks Character specialization should eventually become meaningful and persistent, although respec may be possible later. For this vertical slice, create enough progression to demonstrate at least several meaningful levels. Core character resources: - Health - Mana where appropriate - Stamina/Vigor where appropriate Resources persist between encounters instead of automatically resetting after every battle. Players recover through: - abilities - potions - town - rest points - selected exploration events --- 5. EQUIPMENT SYSTEM Equipment is essential. Create equipment slots appropriate for the game, such as: - weapon - off-hand/shield - head - chest - hands - legs - boots - accessory Armor progression includes: - leather - mail - plate depending on class. Gear must change character statistics. Most importantly: equipment must also visibly appear on the hero. Build player characters using visual layers so weapons, shields, armor and helmets can be displayed on top of the base character. Fix visual alignment carefully. A shield must look physically held by the arm rather than floating behind the character. Helmets must align with the head correctly. --- 6. LOOT SYSTEM Loot is one of the most important systems. Enemies can drop: - gold - consumables - crafting materials - equipment Create item rarity tiers with clearly readable but tasteful visual feedback. Avoid excessive neon effects. Equipment should have meaningful stats such as: - armor - damage - strength - intellect - agility - vitality - critical chance - healing power - secondary class-relevant stats Items can also have occasional modifiers. Do not make every item useful to every class. Loot should often be class-oriented. Important equipment must remain exciting and relatively uncommon. During the early prototype, approximate equipment drop chances may be relatively generous, around 25–40% for selected encounters, so the loot loop can be tested. However, stronger equipment and later tiers should become progressively rarer. Normal mobs should mostly provide basic resources and occasional equipment. Elite enemies should have noticeably increased chances of valuable loot. Bosses and dungeon bosses should have unique loot tables. Create several recognizable unique items tied specifically to particular enemies or bosses. Players should eventually remember things such as: “That boss can drop the weapon I want.” --- 7. PARTY LOOT For multiplayer-oriented loot testing, implement a visible classic party loot roll system for rare equipment. When relevant equipment drops: A large animated d20 appears. Eligible players can choose NEED or PASS. Need rolls are visible to the party. The winner is clearly shown. For the current prototype with bots, bots should make believable automated decisions according to whether the item is appropriate for their class. --- 8. COMBAT PRESENTATION Combat must use a highly readable staged composition. The player's party is positioned in the lower portion of the screen, facing upward toward the enemies. Enemies are positioned in the upper portion of the screen, facing downward toward the player party. Do not reverse this staging. The visual composition should evoke a handcrafted tabletop/adventure RPG battle screen while remaining completely original. Support encounters containing: - one enemy - small enemy groups - up to approximately five standard enemies - large central bosses - bosses accompanied by adds or summoned creatures Characters and enemies should occupy physical positions rather than merely appearing as icons in an interface. --- 9. TURN-BASED COMBAT Combat is turn-based at the individual-character level. Characters and enemies act according to an initiative/order system. The UI must clearly communicate: - whose turn it is - available abilities - valid targets - health - resources - buffs/debuffs - upcoming turns where useful Combat should be fast and satisfying rather than slow and overly tactical. Actions need animation, impact, sound and visual feedback. Examples: Warrior: - sword strike - shield guard - heavy strike - taunt Priest: - healing spell - protective blessing - holy attack Rogue: - quick strike - poison/bleed attack - high critical attack - evasion Mage: - magic bolt - area spell - defensive magic - elemental attack Do not make every class simply deal damage with different particle colors. Each class must fulfill its role. --- 10. COMBAT POLISH Combat should feel fluid despite being turn-based. Include: - short anticipation animations - weapon swings - hit reactions - small knockback where appropriate - particles - impact flashes - readable damage numbers - healing numbers - buffs/debuff visual indicators - critical hit feedback - death animations - polished sound effects Do not make e, as an in-game screenshot in flat colour 2D shapes with a bright limited palette. Palette: sky blue #8ecae6, grass #3a7d44, player sunflower #ffb703, threat red #d62828, accent white #fdfcdc. Everything is original: never draw or resemble characters, places or logos from existing games, films or brands (no red-capped plumbers, no famous mascots), even when the idea names one. Keep the pictures honest: they promise what a small first version of this game, made in a game engine in a few days, can look like. Simple readable shapes, clear silhouettes, few flat materials, the in-game camera view. Never film stills, photoreal renders, AAA key art, detailed textures, cinematic lighting, or anything that looks like a big-studio game. No text, UI, HUD, logos or editor screens inside any image.