How rafaelbarbosatec/bonfire works
Project type and purpose
• This is an open-source Flutter plugin/library (“Bonfire”) built on top of the Flame game engine.
• Its goal is to provide a modular RPG game framework (tile maps, input, behaviors, collisions, lighting, UI) and an example/demo app.
File structure
• Top-level: GitHub config (workflows, ISSUE_TEMPLATE), pubspec, README, CHANGELOG.
• lib/: the core Bonfire engine, subdivided into modules (base game loop, camera, input, map readers/builders, collision, lighting, behaviors, NPCs, mixins, utilities, widgets).
• example/: a Flutter application exercising Bonfire’s API, with its own assets, pages, shaders, tests, and pubspec.
• awesome/: showcase games built with Bonfire.
• media/, docs, CI/CD workflows for publishing and testing.
README
• Confirms it’s a Flutter/Flame-powered RPG game framework.
• Points to demos, docs site, and an “awesome” gallery.
• Emphasizes extensibility via packages (bonfire_bloc, bonfire_spine).
Elements
• Platform & external (gray)
• Library modules (green)
• Example App (orange)
• Rounded rectangles for controllers/providers
• Solid rectangles for core modules
Detailed call-outs (don’t overthink – break into as many components as possible)
• Drill into lib/map: show TiledReader, SpritefusionReader, world builders, cache providers.
• Lib/scene_builder actions as plugin points.
• How mixins slot into GameComponent to add behaviors.
• CI/CD block with steps: unit tests (unit.yml) → publish.yml → pub.dev.