Mmorpg game test

Prompt

SILKROAD-INSPIRED OFFLINE MMORPG DEVELOPMENT CHALLENGE 1. OBJECTIVE Independently develop a complete, playable 3D MMORPG prototype inspired by Silkroad Online. Build everything from scratch using Node.js, TypeScript and Babylon.js. This is an offline single-player game. No backend, multiplayer server, external AI API or online account system is required. This is a serious game development challenge, not a simple visual demo. Prioritize functional, interconnected gameplay systems, polished presentation and maintainable architecture. Make implementation decisions independently. Do not stop to ask for approval. 2. TECHNOLOGY Required: - Node.js - TypeScript - Babylon.js - Vite - HTML5 and CSS - IndexedDB or equivalent local storage Use modular architecture. Keep game logic, rendering, UI, AI and persistence separated. The finished application must work on desktop and mobile browsers. 3. ART AND ASSETS The visual direction should resemble the ancient Chinese-inspired world of Silkroad Online. Use existing, legally usable 3D models, textures, environments and animations. Do not manually model or draw game assets. UI elements may be created using HTML/CSS/SVG. Potential sources: - https://quaternius.com/ - https://sketchfab.com/ - https://polyhaven.com/ - https://kenney.nl/assets - https://opengameart.org/ - https://www.mixamo.com/ - https://github.com/ Check individual asset licenses. Do not use copyrighted Silkroad assets without permission. Asset download restrictions Before development, test: - Internet and HTTPS access. - curl/wget or equivalent downloads. - Binary file downloads. - ZIP extraction. - npm installation. - Whether downloaded files can be included in the final ZIP. The environment may block certain asset downloads. If a source fails: 1. Try another official source. 2. Check official GitHub repositories/releases. 3. Try permitted public CDNs. 4. Stop retrying sources that are clearly blocked. Never bypass authentication, paywalls or access restrictions. Never save HTML error pages as model files. Verify actual file formats and test assets in Babylon.js. Bundle all required assets locally. The game must not require external asset downloads at runtime. Primitive geometry is allowed for collision, hitboxes and debugging, but must not replace final character or environment artwork. If real assets cannot be obtained, disclose the limitation honestly. 4. GAME WORLD Create a coherent 3D world inspired by Silkroad Online. Include: - Starting town. - Wilderness and hunting areas. - Roads and paths. - Buildings and environmental objects. - Trees and vegetation. - NPCs. - Monster spawn locations. - Loot locations. - At least two visually distinct areas. Implement collision detection, world boundaries, third-person camera, camera rotation and zoom, NPC interaction and monster spawning. 5. LOGIN AND CHARACTER SELECTION Create a polished login-style intro, even though the game is offline. After entering, show a regional character selection screen. Features: - Character creation and deletion. - Character name and class. - 3D character preview. - Character level and basic information. - Local character persistence. 6. CHARACTER SYSTEM Implement: - Level and experience. - HP and MP. - Strength and intelligence. - Physical and magical attack. - Physical and magical defense. - Critical rate. - Attack speed. - Movement speed. - Attribute allocation. - Level-up progression. - Health and mana regeneration. - Death and respawn. All statistics must affect actual gameplay. 7. SKILLS AND MASTERY Build a functional skill and mastery system inspired by Silkroad Online. Skills must support: - Active and passive abilities. - Skill levels and requirements. - Mana costs. - Cooldowns. - Damage and healing. - Buff effects. - Range and target restrictions. Masteries must have separate progression, mastery points, unlockable skills and level requirements. Provide skill icons, descriptions, cooldown indicators and keyboard shortcuts. 8. COMBAT Implement real-time combat with: - Target selection. - Basic attacks. - Skill usage. - Attack animations. - Damage calculation. - Critical hits and misses. - Damage numbers. - Target health bars. - Attack range and cooldowns. - Death and loot handling. Combat must use the character, skill, equipment and monster statistics. Do not fake combat with disconnected UI buttons. 9. MONSTER AI Create several monster types with different statistics and behavior. Each monster needs: - Level, HP, attack and defense. - Movement and attack speed. - Aggression and attack range. - Experience rewards. - Loot table. Implement a state machine: - Idle - Patrol - Detect player - Chase - Attack - Return to spawn - Dead Monsters must independently detect, pursue and attack the player, and return to their spawn area when appropriate. 10. AUTONOMOUS AI CHARACTERS This is a major feature. Create a separate, independent AI module that generates and controls autonomous characters inside the game world. Do not use external LLM APIs. All AI behavior must run locally. Use behavior trees, utility-based decision-making and finite state machines. Each AI character should have: - Randomized name and appearance. - Class, level and attributes. - Equipment and skills. - Individual personality and behavior parameters. - Independent goals and decision-making. They must be able to: - Explore the world. - Travel between locations. - Find and fight monsters. - Select targets. - Use skills. - Collect loot. - Change equipment. - Recover HP and MP. - Avoid dangerous enemies. - Return to safe locations. - Interact with NPCs. AI characters must behave like independent players, not follow the user or repeat a fixed animation loop. The AI module must support spawning, removing, configuring and monitoring multiple characters. AI behavior should be visible and understandable in gameplay. 11. INVENTORY AND ITEMS Implement a functional grid-based inventory. Features: - Item icons and descriptions. - Item categories and rarity. - Stacking and quantities. - Moving, using and deleting items. - Item drops and loot collection. - Gold and consumables. Item categories: - Weapons. - Shields. - Armor. - Accessories. - Potions. - Consumables. - Quest items. Inventory changes must persist locally. 12. EQUIPMENT Implement equipment slots: - Weapon. - Shield. - Head. - Chest. - Legs. - Hands. - Feet. - Necklace. - Earrings. - Rings. Support swords, spears, blades and bows. Equipment must affect character statistics. Where compatible models exist, changing equipment must also change the character's appearance. 13. BUFFS AND STATUS EFFECTS Create a reusable status effect system. Include attack, defense, movement speed and attack speed increases, regeneration, poison, stun and slow. Each effect must support duration, strength, stacking rules, expiration, visual feedback and stat modification. 14. PROGRESSION AND LOOT Implement randomized monster loot tables with: - Gold. - Weapons and armor. - Potions. - Different rarity levels. - Experience rewards. Balance monster difficulty, item statistics and player progression. 15. UI AND CONTROLS Create a polished traditional MMORPG interface. Required windows and elements: - Main HUD. - HP, MP and experience bars. - Level display. - Target information. - Skill hotbar. - Inventory. - Character information. - Equipment. - Skills and masteries. - Buff indicators. - Event/chat log. - Mini-map or world map. - NPC interaction. - Settings. Desktop: - WASD movement. - Mouse camera control. - Mouse target selection. - Number keys for skills. - Keyboard shortcuts. Mobile: - Virtual joystick. - Touch target selection. - Touch-friendly skill buttons. - Responsive windows and inventory. Avoid overlapping controls and unreadable layouts. The UI should look like an MMORPG, not a generic administration dashboard. 16. CAMERA AND ANIMATION Implement smooth third-person camera movement, zoom and rotation. Use existing animations wherever possible: - Idle. - Walking. - Running. - Basic attack. - Skill attack. - Hit reaction. - Death. Use animation blending where supported. Never claim an animation works if the model does not contain it. 17. SAVE AND LOAD Persist all important data locally: - Characters and statistics. - Position and progression. - Inventory and equipment. - Skills and masteries. - Settings. Implement automatic saving, manual saving, loading and basic save corruption handling. Progress must survive browser refresh and application restart. 18. ARCHITECTURE Separate the application into logical modules: - Game engine and world. - Character management. - Combat. - Skills and masteries. - Inventory and equipment. - Monster management and AI. - Autonomous character AI. - Buffs and loot. - UI and input. - Camera and animation. - Save/load. Use TypeScript interfaces and types consistently. Avoid monolithic files and unnecessary dependencies. 19. DEVELOPMENT PROCESS Work in these stages: 1. Initialize the project and verify the development environment. 2. Test asset download capabilities and acquire assets. 3. Build the world, character movement and camera. 4. Implement character statistics and progression. 5. Implement combat, monsters and monster AI. 6. Implement skills, masteries and buffs. 7. Implement inventory, equipment and loot. 8. Implement autonomous AI characters. 9. Build login, character selection and gameplay UI. 10. Implement persistence. 11. Test, debug and optimize. 12. Prepare the final deliverables. Do not stop after creating a project skeleton. Continue until a playable game exists. 20. TESTING Actually run the application and verify: - npm installation. - TypeScript compilation. - Production build. - Application startup. - Babylon.js initialization. - Asset loading. - Character movement. - Camera and collisions. - Combat and damage. - Monster AI. - Skills and masteries. - Inventory and equipment. - Autonomous AI behavior. - Save/load. - Desktop and mobile UI. Fix discovered errors. Use browser automation or screenshots if available. Distinguish honestly between implemented and tested, implemented but untested, partially implemented and not implemented. Do not claim a feature is complete simply because source code exists. 21. FINAL DELIVERY Deliver: - Complete source code. - All legally distributable local assets. - package.json and dependency configuration. - README with installation instructions and controls. - Architecture overview. - Asset source and license list. - Feature completion report. - Known limitations. - Production build. - A ZIP archive containing the complete project. - A working download link to the ZIP. - A playable preview if the environment supports it. The project must run independently after extraction and installation. FINAL INSTRUCTION Build the best possible playable offline MMORPG prototype within the available execution environment. Prioritize functional gameplay, real interconnected systems, visual quality and stable implementation. Make decisions independently. Do not ask for approval at every stage. Do not replace difficult features with superficial placeholders. If something is impossible because of environment restrictions, document it and continue with the remaining requirements. Build it. Run it. Test it. Fix it. Deliver it.

A system prompt was added to support web rendering