dungeon-system

Dungeon map generation for a card battle game uses domain models for DungeonNodeType and DungeonNode interfaces to create deterministic layouts with battle, elite, boss, rest, event, shop, treasure, and mystery nodes for varied run experiences.

Depth progression in dungeon exploration governs player advancement, risk, and loot retention across multiple depths. It works with a persistent DungeonRunProvider to track progression and manage return systems during a dungeon run.

Adding dungeon node types involves implementing the DungeonNodeType domain model to categorize encounters. Supported types include battle, elite, boss, rest, event, shop, treasure, and mystery nodes, which structure the exploration and combat flow.

Yes, dungeon run state and player progression are tracked persistently using a DungeonRunProvider. This component maintains progression data and manages the return system logic across multiple depths throughout the dungeon exploration session.

No external dependencies are required to modify dungeon exploration logic. The system operates independently using internal domain models, interfaces, and a persistent provider, allowing direct integration into existing card battle game architectures.