magic game test
Prompt
PROJECT: REALITY FORGE — Interactive 2D Magic Laboratory YOUR ROLE You are an expert HTML5 game developer, JavaScript systems architect, technical VFX artist, physics programmer, UI/UX designer and quality assurance engineer. Your task is to build a complete, playable, visually impressive 2D spell-design and spell-testing sandbox for a future Unity game titled Reality Forge. This is an implementation assignment, not a design document. Create the actual application, run it, test it, fix errors and deliver the finished project files. You have creative freedom to improve the presentation, controls, effects and architecture, provided you preserve the magic system and the project's constraints. 1. PROJECT OBJECTIVE Build an interactive magical testing laboratory where the player can: Construct custom spells using a modular magic system. Select spell forms, elements, casting methods and modifiers. Configure spell properties such as size, power, quantity and duration. Immediately test the completed spells in a 2D environment. Observe beautiful, responsive visual effects and genuine physical interactions. Deal damage to a single target dummy and inspect detailed results. Test movement and utility spells. Save, load, duplicate, rename, export and import spell designs. Compare different configurations and understand their resource costs. The central priority is spell creation and experimentation. Do not spend development effort creating an RPG, campaign, enemies, quests, inventory, dialogue, world map or story. This project is exclusively a magic-system prototype. Essential constraints Exactly one target dummy. No enemy AI or hostile creatures. No enemy waves, bosses or combat encounters. No character progression or skill-tree requirements. No locked spells: all forms, elements and compatible modifiers must be accessible for testing. No multiplayer. No backend, accounts, paid APIs or external services. No required internet connection. The application should ideally run by opening index.html. Use HTML5, CSS3 and vanilla JavaScript. Canvas 2D is preferred for the game world; WebGL is optional only if justified by a major visual benefit. Target 60 FPS on a laptop with RTX 4050 graphics and 24 GB RAM. Do not substitute a collection of predefined spell animations for a genuinely customizable magic system. The same underlying spell engine must generate different outcomes based on the player's configuration. 2. VISUAL DIRECTION The prototype should feel like a high-quality independent fantasy game's spell-design laboratory. Create a polished magical interface with: Dark navy, charcoal and subdued violet surfaces. Elegant gold and cyan accents. Element-specific colors for magic. Smooth transitions, hover effects and readable typography. Attractive spell icons using original vector artwork or procedural graphics. Soft glow, layered particle systems and expressive animations. Visually distinct elements and forms. Carefully designed magical impact effects. Avoid generic placeholder UI, oversized neon rectangles, excessive bloom or unrelated decorative elements. Game environment Use a 2D side-view testing arena. Include: A controllable mage/player character on the left. One stationary target dummy that can receive damage and status effects. A ground surface and a few static platforms for traversal testing. At least one vertical surface for grappling and wall traversal. Enough space to test projectile trajectories and long-range attacks. Subtle environmental decoration and magical ambience. The dummy should be clearly visible and easy to aim at. Additional environmental fixtures may be used only when necessary to test utility mechanics, such as a movable block, repairable ward or dispellable barrier. These are laboratory props, not enemies or additional damageable dummies. The arena should support a movable camera or a sufficiently large stage for demonstrating high launches, flight and long-distance movement. 3. SPELL CONSTRUCTION SYSTEM Every spell must follow this core model: Spell = Form + Optional Element + Compatible Casting Method + Compatible Modifiers + Configurable Parameters Only the form is mandatory. A spell may use neutral magic without an element. The system must not require the player to add Fire merely to make a damaging spell, or a separate Burn modifier to give fire its natural burning behavior. Modifiers and casting methods must follow meaningful compatibility rules. For example: Ricochet works with suitable projectiles. Duration applies meaningfully to persistent effects. Quantity can increase the number of summoned blades. Expansion can enlarge a field or wave. Dash can carry elemental contact effects. A stationary wall should not automatically behave like a homing projectile. Invalid combinations must be visibly disabled or rejected with clear explanations. Build the underlying system using structured spell definitions, not hundreds of manually hard-coded individual spell recipes. 4. ELEMENTS Implement all eight elemental categories: Element Core behavior Fire Heat, burning, ignition and explosive combustion Ice Freezing, chilling and frozen structures Lightning Electrical damage, conduction and discharges Water Flow, wetness, pressure and liquid interaction Wind Air pressure, movement and directional force Earth Physical mass, impact and durable structures Light Illumination, radiance and light-based effects Dark Obscuration, shadow and darkness-related effects Also support Neutral / No Element. Each element should change more than the spell's color. Where applicable, it should influence appearance, contact effects, environmental interaction and the target dummy's status. For example, Fire Dash can burn the dummy on physical collision. Lightning Launch can produce an electrical shockwave. An Ice Wall should look and behave like a solid frozen barrier. Not every combination needs a completely unique effect asset. Use procedural effect composition to generate consistent variations. 5. REQUIRED SPELL FORMS Support the full current candidate catalogue of 32 spell forms. Some may receive more elaborate visual polish than others, but every listed form must have a working, visibly distinct baseline behavior. A. Offensive and physical forms Spear — A narrow, concentrated magical projectile or thrust. Sphere — A spherical projectile or magical orb. Beam — A continuous or timed directional energy beam. Blade — A magical cutting object, slash or summoned blade. Wave — An expanding directional or radial wave. Net — A spread-out restraint or entangling effect. Chain — Linked magical segments or an extending chained attack. Spike — A sharp protrusion or spike summoned from a surface or position. Vortex — A swirling effect that applies rotational or inward forces. B. Defensive and area forms Shield — A protective barrier attached to the player or a selected target. Wall — A stationary defensive or obstructive barrier. Dome — A stationary enclosed protective structure. Field — A persistent area that modifies local conditions or applies elemental effects. Cloud — A volumetric region with lingering magical properties. Distinguish these forms mechanically. A Shield follows its protected target. A Wall is placed in the world. A Dome encloses a region. A Field modifies an area. A Cloud occupies space and can obscure or affect targets within it. Defensive effects need to do more than play animations. Add an optional non-enemy test projectile emitter or a manual test-bolt action to demonstrate blocking, absorption and deflection. C. Mobility forms Dash — Rapid directional displacement. Launch — Apply a strong directional impulse to the caster. Glide — Control aerial movement and reduce descent. Air Step — Briefly redirect or propel the caster while airborne. Grapple — Attach to a valid surface and pull or swing the caster. Surface Traverse — Allow temporary movement along suitable walls or other surfaces. Levitate — Maintain altitude and move slowly without ground contact. Surf — Travel on a generated or sustained moving magical surface. Blink — Instantly relocate to a valid nearby position. Flight — Sustain controlled three-dimensional-style movement within the 2D plane. These must use meaningful player movement, not merely teleporting an animation across the screen. Make elemental contact properties functional wherever they apply. For example: Fire Dash burns on collision. Earth Dash can have strong physical impact. Lightning Launch may create an electrical shockwave. Wind Glide can alter descent and horizontal control. Ice Surf may generate a temporary frozen trail. D. Utility forms Detect — Reveal nearby magical objects, fixtures or properties. Manipulate — Push, pull or move suitable physical objects. Tether — Create and maintain a magical connection between two points. Dispel — Remove or suppress a compatible active magical effect. Conceal — Create a visibility-obscuring or concealment effect. Restore — Recover health or repair a suitable target or fixture. Mark — Place a persistent magical marker or reference point. Stabilize — Maintain or stabilize a designated unstable magical effect. Utility effects should be demonstrated with the laboratory environment when possible. Avoid pretending a mechanic exists when it doesn't. For example, Conceal may visibly apply an obscured status, but with no enemy AI it should not falsely claim to be demonstrating stealth detection behavior. Derived behaviors Include these through existing forms or modifiers rather than adding unnecessary forms: Featherfall — a simplified controlled descent. Recoil — propulsion caused by an opposing magical impulse. Platform — a horizontal solid magical structure. Bridge — an extended traversable structure. Illuminate — light emitted by an appropriate spell.
A system prompt was added to support web rendering
Response not available
Response not available