Package detailsv1.4.0

flame_behaviors

Flame Behaviors applies separation of concerns to game logic in the form of Entities and Behaviors, originally built by Very Good Ventures.

AndroidiOSWebmacOSWindowsLinux

pub.dev API documentation Source code

30-day downloads: 3.1K
Likes: 34
Pub points: 160

Install package

flutter pub add flame_behaviors

Package Overview

Package selection guidance compiled from public package information, community data, and project usage.

Flame Behaviors is a Flutter/Dart package that promotes clean game architecture by separating game logic into reusable, modular components called Behaviors. It enables developers to attach behaviors to entities, allowing for flexible and maintainable game development. Originally created by Very Good Ventures, it integrates seamlessly with the Flame game engine, supporting multiple platforms including Android, iOS, Web, macOS, Windows, and Linux. This approach enhances code reusability and simplifies complex interactions within games.

Use cases

Modular game component design
Reusing logic across entities
Separating concerns in game systems
Building scalable game architectures
Managing entity interactions
Creating dynamic gameplay mechanics

Key features

Attach behaviors to entities
Supports composition over inheritance
Encourages reusable logic
Integrates with Flame engine
Platform-agnostic
Clean separation of concerns

Suitable for

Game developers using Flame engine
Teams prioritizing maintainable code
Projects requiring modular game logic
Developers building complex interactive systems
Those adopting clean architecture patterns

Considerations

Requires familiarity with Flame engine
Best used in larger projects
May add complexity for simple games
Dependent on proper behavior lifecycle management

Original README

Original README snapshot from the linked source repository. Visit the repository for the latest content.

A Flutter-based game engine.

Documentation

The full documentation for Flame can be found on docs.flame-engine.org.

To change the version of the documentation, use the version selector noted with version: in the top of the page.

Note: The documentation that resides in the main branch is newer than the released documentation on the docs website.

Help

There is a Flame community on Blue Fire's Discord server where you can ask any of your Flame related questions.

If you are more comfortable with StackOverflow, you can also create a question there. Add the Flame tag, to make sure that anyone following the tag can help out.

Features

The goal of the Flame Engine is to provide a complete set of out-of-the-way solutions for common problems that games developed with Flutter might share.

Some of the key features provided are:

A game loop.
A component/object system (FCS).
Effects and particles.
Collision detection.
Gesture and input handling.
Images, animations, sprites, and sprite sheets.
General utilities to make development easier.

On top of those features, you can augment Flame with bridge packages. Through these libraries, you will be able to access bindings to other packages, including custom Flame components and helpers, in order to make integrations seamless.

Flame officially provides bridge libraries to the following packages:

flame_audio for AudioPlayers: Play multiple audio files simultaneously.
flame_bloc for Bloc: A predictable state management library.
flame_fire_atlas for FireAtlas: Create texture atlases for games.
flame_forge2d for Forge2D: A Box2D physics engine.
flame_gamepads - Support gamepad input in your game (bridge package for gamepads)
flame_isolate - Makes it easy to use Flutter Isolates in a Flame game.
flame_lint - Our set of linting (analysis_options.yaml) rules.
flame_lottie - Support for Lottie animation in Flame.
flame_network_assets - Helpers to load game assets from network.
flame_rive for Rive: Create interactive animations.
flame_svg for flutter_svg: Draw SVG files in Flutter.
flame_texturepacker: Load and use sprite sheets generated with TexturePacker
flame_tiled for Tiled: 2D tile map level editor.

Support

The simplest way to show us your support is by giving the project a star! :star:

You can also support us monetarily by donating through OpenCollective:

Through GitHub Sponsors:

Or by becoming a patron on Patreon:

You can also show on your repository that your game is made with Flame by using one of the following badges:

[![Powered by Flame](https://img.shields.io/badge/Powered%20by-%F0%9F%94%A5-272727.svg)](https://flame-engine.org)
[![Powered by Flame](https://img.shields.io/badge/Powered%20by-%F0%9F%94%A5-272727.svg?style=flat-square)](https://flame-engine.org)
[![Powered by Flame](https://img.shields.io/badge/Powered%20by-%F0%9F%94%A5-272727.svg?style=for-the-badge)](https://flame-engine.org)

Contributing

Have you found a bug or have a suggestion of how to enhance Flame? Open an issue and we will take a look at it as soon as possible.

Do you want to contribute with a PR? PRs are always welcome, just make sure to create it from the correct branch (main) and follow the checklist which will appear when you open the PR.

Also, before you start, make sure to read our Contributing Guide.

For bigger changes, or if in doubt, make sure to talk about your contribution to the team. Either via an issue, GitHub discussion, or reach out to the team either using the Discord server.

Credits

The Blue Fire team, who are continuously working on maintaining and improving Flame and its ecosystem.
All the friendly contributors and people who are helping out in the community.