flame-systems skill

Overview

This skill bundles 14 common Flame Engine game systems into a single reference package for JavaScript projects. It provides design patterns, interaction maps, and example implementations for quest, dialogue, inventory, combat, save/load, shop, crafting and more. Use it as a practical blueprint to accelerate system integration and cross-system dependencies. It pairs concise explanations with code-oriented guidance so teams can adapt systems to their game architecture.

How this skill works

Each system is documented with its responsibilities, common data structures, event flows, and integration points with other systems. The reference index maps each system to a focused document (quest, dialogue, inventory, combat, skills, etc.) and shows dependencies so you can sequence implementation. Example code sketches demonstrate serialization, item stacking, quest state machines, combat resolution, and network sync patterns. Read a specific system file to get patterns, sample APIs, and integration notes for that area.

When to use it

• Starting a new game project on Flame Engine and needing ready-made system patterns.
• Refactoring or replacing existing game systems with clearer separation of concerns.
• Planning cross-system interactions like quests awarding inventory items or skills affecting combat.
• Prototyping features quickly using documented design patterns and code sketches.
• Preparing multiplayer or procedural content where systems must coordinate state and persistence.

Best practices

• Follow the documented dependency map to implement systems in a stable order (e.g., inventory before shop).
• Design systems as small, testable modules with clear public APIs and events for decoupling.
• Use the save/load patterns to serialize minimal authoritative state and avoid redundant data.
• Centralize item and localization data to prevent duplication across shop, crafting, and dialogue.
• Adopt the suggested patterns for deterministic combat calculations to ease testing and multiplayer sync.

Example use cases

• Implement an RPG core: quest flow, dialogue trees, inventory, equipment visuals (paper doll), and combat rules.
• Add a shop and crafting loop where players buy materials, craft items, and receive quest rewards.
• Create procedural zones that spawn enemies and drop inventory using the procedural system plus combat integration.
• Enable cloud save and load integrating achievements and persistent quest progress for cross-device play.
• Build multiplayer features by following the multiplayer reference for state synchronization of inventory, quests, and combat events.

FAQ