aaa
Prompt
# PROJECT IRONBOUND — ULTIMATE 3D PHYSICS COMBAT ADVENTURE ## YOUR ROLE Act as an elite AAA game development studio combining expert gameplay programmers, physics engineers, combat designers, 3D artists, animators, level designers and sound designers. Create a complete, polished, highly addictive 3D action-adventure fighting game inspired by the best elements of: - Stick Rangers: RPG progression, equipment, builds and enemy variety. - Stick It to the Stickman: chaotic physics, brutal impacts, hilarious ragdolls and satisfying combat. - Gladihoppers: arenas, weapons, progression and entertaining battles. - Half Sword: realistic weapon weight, momentum, collisions, physical combat and unpredictable ragdolls. Do not copy their assets or designs. Create an original game with its own identity, characters, world and mechanics. **The objective is to make a genuinely entertaining, finished game, not a basic prototype or visual demo.** # 1. CORE GAMEPLAY VISION Create a third-person, fully 3D medieval fantasy action game featuring a huge world map with 100 campaign stages across 10 unique regions. The entire experience revolves around extremely satisfying physics-based melee combat. Combat should combine realistic physical interactions with exaggerated arcade-style impact satisfaction. The player should be able to: - Swing swords, axes, hammers, spears and other weapons. - Block, parry, dodge, counterattack and stagger enemies. - Knock opponents off balance and send them flying. - Attack different body parts with different physical consequences. - Break enemy guards and knock weapons out of their hands. - Fight multiple opponents simultaneously. - Use walls, obstacles, platforms and environmental hazards to gain advantages. - Get knocked down, physically recover and return to combat. - Perform spectacular finishing attacks. Every encounter should create memorable, unpredictable moments. # 2. GRAPHICS AND 3D WORLD Use Three.js/WebGL or equivalent browser-compatible technology. This must be a genuine 3D game, not a 2D game with simulated depth. Create a distinctive premium medieval fantasy visual style featuring: - Fully articulated 3D humanoid characters. - Detailed weapons, armour and equipment. - Forests, castles, villages, ruins, fortresses, mountains, dungeons and battlefields. - High-quality lighting, shadows, fog and atmospheric effects. - Detailed materials for metal, leather, wood, stone and cloth. - Weapon trails, sparks, dust, impact effects and environmental particles. - Atmospheric weather and lighting variations. - Beautiful environments with distinct visual identities. Use procedural modelling and generated geometry when external assets are unavailable. Maintain consistent proportions, materials and art direction. The camera should be third-person, smooth, responsive and intelligently follow the player while keeping combat visible. # 3. ADVANCED PHYSICS — HIGHEST PRIORITY Use Rapier.js, Cannon-es or another suitable physics engine. Physics must be central to gameplay, not just decorative. ### Character physics Implement articulated humanoid characters with physical body parts: - Head and torso. - Upper and lower arms. - Hands. - Thighs and lower legs. - Feet. Implement: - Rigid-body simulation. - Joint constraints and realistic movement limits. - Mass, inertia, momentum and damping. - Balance and centre-of-mass calculations. - Collision detection. - Knockback based on actual impact force. - Physical stumbling and recovery. - Different reactions depending on which body part is struck. ### Active ragdolls This is critical. Characters must combine animation-driven movement with physical reactions. They should attempt to maintain balance, brace against impacts and recover their posture. Strong impacts should overcome their ability to remain standing. Implement transitions between: - Normal movement. - Combat animations. - Staggering. - Loss of balance. - Knockdown. - Full ragdoll. - Recovery. Ragdolls should fall, roll, stumble, slide and collide naturally with their surroundings. Avoid stiff canned knockback animations. Prevent physics instability, jitter, stretching, uncontrolled spinning, broken joints and permanently stuck characters using appropriate constraints, damping, collision filtering and simulation substeps. ### Weapon physics Every weapon needs individual physical properties: - Mass and length. - Centre of mass and balance. - Swing velocity. - Momentum. - Reach. - Impact force. - Recovery time. - Handling difficulty. Weapon collisions must consider velocity, direction, contact position and relative momentum. A heavy hammer must feel substantially different from a dagger or sword. A successful hit should depend on physical contact, not simply an animation reaching a damage frame. ### Impact and damage Calculate damage using: - Weapon type. - Impact velocity. - Collision angle. - Contact location. - Relative momentum. - Armour protection. - Body part struck. - Character stability. A strike to the legs should affect movement and balance differently from a strike to the head or torso. Implement physical stagger, knockback, loss of balance, armour resistance and weapon disarming. # 4. COMBAT SYSTEM Create responsive, skill-based combat with: - Light and heavy attacks. - Charged attacks. - Directional swings. - Overhead attacks. - Sweeping attacks. - Thrusts. - Blocking. - Timed parries. - Counterattacks. - Dodges and rolls. - Shield bashes. - Stamina management. - Stagger and knockdown states. - Finishing attacks. - Special abilities. Attacks should have clear anticipation, acceleration, impact and recovery phases. Make combat weighty but responsive. Avoid excessively slow or frustrating controls. Add hit-stop, camera shake, impact particles, weapon trails and layered sound effects to make every successful attack feel powerful. Combat should reward timing, positioning, weapon choice and physical skill, not simply button mashing. # 5. WEAPONS, ARMOUR AND EQUIPMENT Create at least 25 distinct weapons: Sword, longsword, greatsword, dagger, dual blades, battle axe, greataxe, mace, morning star, warhammer, maul, spear, halberd, poleaxe, lance, flail, scimitar, cleaver and additional original weapons. Each weapon must have different handling, reach, damage, momentum, animations and combat advantages. Create equipment slots for: - Helmet. - Chest armour. - Gloves. - Leg armour. - Boots. - Shield. - Main weapon. - Secondary weapon. - Accessories. Include different armour sets, visual changes, rarity tiers, upgrades and meaningful statistics. Equipment must visibly change the player character. # 6. RPG PROGRESSION Implement a complete player progression system featuring: - Experience and character levels. - Health and stamina. - Strength, agility and endurance. - Weapon mastery. - Defence. - Skill points. - Gold and loot. - Equipment upgrades. - Unlockable abilities. - Character customisation. Create five skill specialisations: 1. Warrior: strength, heavy attacks and staggering. 2. Duelist: speed, precision, parries and counters. 3. Guardian: shields, armour and defence. 4. Berserker: aggressive attacks and high-risk abilities. 5. Weapon Master: versatility and weapon-specific bonuses. Create meaningful skill trees with upgrades that noticeably change gameplay. # 7. WORLD MAP — EXACTLY 100 STAGES Create a beautiful, interactive fantasy world map containing exactly 100 campaign stages. Divide it into 10 regions with 10 stages each: 1. Fallen Frontier — ruined villages and training grounds. 2. Ironwood Forest — woodland bandits and ambushes. 3. Bloodstone Highlands — mountain forts and mercenaries. 4. Ashen Kingdom — burning settlements and corrupted knights. 5. Drowned Coast — coastal fortresses and pirates. 6. Frozen Marches — icy battlefields and northern warriors. 7. Sunken Empire — ancient ruins and underground arenas. 8. Crimson Wastes — deserts and gladiatorial battles. 9. Black Citadel — elite guards and powerful champions. 10. Throne of Ruin — legendary enemies and final bosses. Each stage must have: - Unique name and number. - Position on the world map. - Environment and arena. - Enemy composition. - Difficulty. - Objective. - Rewards. - Completion status. World map features: - Clickable stage markers. - Animated travel between locations. - Region artwork and names. - Locked and unlocked stages. - Completion indicators. - Boss markers. - Optional challenges. - Rewards previews. - Region completion bonuses. Make progression visually clear and satisfying. Every stage must represent an actual playable encounter. Avoid empty markers or fake content. Use reusable level systems where appropriate, but vary environments, layouts, objectives, enemies, difficulty and encounter composition to make all 100 stages feel worthwhile. # 8. LEVEL DESIGN AND ENEMY VARIETY Include at least 20 enemy archetypes with different weapons, armour, statistics and combat behaviours. Create: - Basic soldiers. - Bandits. - Shield warriors. - Heavy knights. - Agile duelists. - Spearmen. - Berserkers. - Archers where appropriate. - Elite champions. - Mini-bosses. - Major bosses. Create varied mission types: - Eliminate all enemies. - Survive enemy waves. - One-on-one duels. - Outnumbered encounters. - Arena tournaments. - Protect an NPC. - Survive ambushes. - Defeat elite champions. - Weapon challenges. - Environmental battles. - Time trials. - Boss encounters. Each region should introduce new enemy combinations, challenges and mechanics. Bosses need distinctive appearances, equipment, combat styles, attack patterns and multiple phases. # 9. ENEMY AI Enemies must actively participate in combat. Implement: - Target tracking. - Movement and distance management. - Attack selection. - Blocking and parrying. - Dodging. - Stamina management. - Tactical aggression. - Retreating when disadvantaged. - Group coordination. - Different AI personalities and skill levels. Enemies should react to physical impacts, falling, staggering and environmental collisions. Avoid repetitive AI that simply approaches and attacks continuously. # 10. INTERACTIVE ENVIRONMENTS Make the environment physically participate in combat. Include: - Breakable barrels and crates. - Knockable obstacles. - Loose weapons. - Physical objects. - Pillars and walls. - Bridges and platforms. - Ledges and stairs. - Environmental hazards. - Objects that can be knocked over. Allow enemies to collide with environmental objects and suffer appropriate physical consequences. Ensure character movement and collision work reliably across different terrain. # 11. GAME MODES Include: **Campaign:** Full 100-stage adventure. **Arena:** Increasingly difficult enemy waves. **Survival:** Last as long as possible. **Duel:** One-on-one combat challenges. **Boss Rush:** Consecutive boss encounters. **Training Ground:** Test combat, weapons and physics. Unlock additional challenges through progression. # 12. AUDIO AND GAME FEEL Create layered audio for: - Sword clashes. - Metal impacts. - Armour collisions. - Heavy body impacts. - Wooden collisions. - Weapon swings. - Footsteps. - Character grunts. - Enemy reactions. - Environment ambience. - Region-specific music. - Boss music. - Menus and interface. Impact audio should change according to weapon type, material and impact strength. Heavy weapons must sound heavy. # 13. INTERFACE AND CONTROLS Create a polished medieval fantasy interface with: - Main menu. - New game and continue. - World map. - Inventory. - Equipment. - Character screen. - Skill tree. - Quest log. - Settings. - Pause menu. - Victory and defeat screens. - Rewards screen. Combat HUD: - Health and stamina. - Enemy health or condition. - Current weapon. - Special ability cooldowns. - Objectives. Default controls: - WASD: Movement. - Mouse: Camera. - Left mouse: Light attack. - Right mouse: Heavy attack or block. - Space: Dodge or jump. - Shift: Sprint. - Q: Parry. - E: Interact or pick up weapon. - R: Special ability. - F: Lock onto target. - Tab: Inventory. - Escape: Pause. Support responsive keyboard and mouse gameplay and provide an on-screen control guide. # 14. TECHNICAL REQUIREMENTS Deliver the entire game as ONE standalone HTML file named **IRONBOUND.html**. Requirements: - HTML, CSS and JavaScript in one file. - 3D rendering through Three.js or equivalent. - Browser-compatible physics engine. - No server-side code. - No build process or installation. - No separate project files. - No missing assets. - No pseudocode or disconnected snippets. External libraries can use reliable CDN links. Explain that CDN-dependent versions require internet access. Embed libraries when practical for offline operation. Use clean, modular internal JavaScript architecture with separate systems for: - Rendering. - Physics. - Player control. - Combat. - Enemy AI. - World map. - Stage management. - Inventory. - Progression. - Audio. - UI. - Saving. Implement localStorage saving and loading for campaign progress, completed stages, equipment, currency, statistics, skills and settings. Include autosaving, restart, pause, resume and graphics/performance settings. Optimise physics and rendering for ordinary desktop computers. Use efficient collision detection, object pooling, appropriate physics substeps and level-of-detail techniques when useful. # 15. TESTING AND COMPLETION Before delivery, test the actual implementation. Verify: - Game loads and renders. - Player movement and camera work. - Combat attacks register correctly. - Weapons collide properly. - Enemies fight back. - Active ragdolls function. - Characters can recover after knockdowns. - Environmental collisions work. - All 100 stages exist and progression works. - Weapons and equipment function. - Rewards and progression work. - Saving and loading work. - All menus and buttons function. - No major console errors or game-breaking bugs. Prioritise functional, polished gameplay over visual features that do not work. Never claim a feature has been implemented when it is only represented by a placeholder. # 16. FINAL DELIVERABLE Create the actual playable HTML file and provide it for download as **IRONBOUND.html**. Do not deliver a design document, tutorial, pseudocode, project proposal or incomplete prototype. The game must include a loading screen, attractive title screen, playable introduction and immediate access to satisfying combat. If necessary, build complex systems using reusable components, but ensure the final experience is coherent, functional and genuinely playable.
A system prompt was added to support web rendering