flame-docs

Flame component lifecycle manages initialization and cleanup through onLoad, onMount, update, render, and onRemove methods. onLoad runs before the component is added to the game tree, onMount runs after, update handles frame logic, render draws to screen, and onRemove cleans up resources when the component is removed.

Flame collision detection uses hitbox types and collision callbacks to detect interactions between components. You define hitboxes on PositionComponent objects and implement collision handlers to respond when hitboxes overlap, supporting both shape-based and custom collision schemas for game mechanics.

Flame's CameraComponent and viewport APIs control what portion of your game world renders on screen. You configure camera position, zoom, and rotation, or choose from built-in viewport patterns to handle screen resolution scaling and follow-camera behavior for dynamic gameplay.

Yes. Flame integrates with flame_riverpod for reactive state management, flame_forge2d for 2D physics, and flame_audio for sound playback. These bridging packages extend Flame's core functionality for complex game logic, physics simulation, and audio control within the same Dart ecosystem.

Flame's effects system and controllers enable animations, transformations, and timed behaviors on components. You apply effects to control position, rotation, scale, and opacity, or build custom controllers to manage complex sequences and timing for game state changes.

Flame targets Dart and Flutter developers with component-based architecture that mirrors common game engine patterns. Understanding PositionComponent hierarchy, the update-render loop, and basic collision concepts helps, but the quick-reference covers core APIs to start building 2D games quickly.