How marcomanfrin/dungeonsexplorer works
Project type and purpose
• Dungeon Explorer is a standalone Java SE text-adventure game (CLI).
• It is not a web or mobile app, but a modular game engine with dynamic loading, event handling, state persistence and a command-line interface.
File structure
• Key packages:
• annotations (custom @AutoLoad)
• config (GameConfig and game.properties)
• core (engine bootstrap, Game, CommandProcessor, GameContext, Memento)
• entities (Enemy, Player, strategies, factories)
• items (Item, CompositeItem, Builder, factories)
• (rooms, loaders, composite rooms, custom rooms)
• events (EventManager, listeners, GameEvent)
• io (GameFileManager, ReflectionLoader, InputSanitizer)
• security (GameException)
• Test folder confirms module boundaries via unit tests.
README for architectural insights
• Lists all major design patterns: Factory, Composite, Iterator, Singleton (GameContext), Strategy, Observer, Template Method, Memento, Builder, Reflection + Annotations, IoC/Config, Streams, Multithreading, Logging, Java I/O.
• External resources: “maps/*.json” and “game.properties”.
Elements
• Clear labels (component names and patterns)
• Blue for core engine
• Green for domain (map, entities, items)
• Orange for infrastructure (I/O, reflection, persistence, logging)