How paveiii/plantilla-2025-grupo-a works
Project type and purpose
• This is an open-source, single-process, Python-based 2D RPG game built on the Arcade and Pyglet engines, using Tiled maps (via pytiled_parser).
• It provides multiple “views” (main menu, game, battle, inventory, settings, etc.), a turn-based battle system, a world map loader, sprite managers, and JSON-driven data dictionaries for items, effects, characters, and world tiles.
File structure
• Top-level directories & files:
• rpg/ ← core Python game package
• resources/ ← all external assets (tilesets, maps, sounds, sprites, data JSON)
• docs/ ← design documents
• setup.py, pyproject.toml, setup.cfg ← build/config
• Within rpg/:
• __main__.py launches the game via Arcade’s Window/View system
• views/ holds all UI/state classes (MainMenuView, GameView, BattleView, etc.)
• sprites/ holds entity classes derived from Arcade.Sprite
• Action.py, Effect.py, EnemyIA.py, BattleAlly.py, BattleEnemy.py, etc. implement game logic and turn-based mechanics
• load_game_map.py handles parsing Tiled maps through pytiled_parser
• save/load is JSON-based via saveGame*.json files
• External libs: Arcade (rendering & windowing), Pyglet (sound), pytiled_parser (map loading).
Key insights from README
• It’s an early-stage open-source RPG.
• Uses Arcade/Pyglet/pytiled_parser.
• Scenes & game states are managed as Arcade Views.
• Assets are managed outside the code in JSON and Tiled formats.
Detail without overthinking
• Break the game into as many logical pieces as you see in the file tree (each View, each major logic module, resource directories).
• Essential flows: user input → view → logic → model updates → rendering.
• External libraries as separate nodes to show dependencies.
• Static resource folder feeding into the loader classes.