flame
flame copied to clipboard
flame-engine
A Flutter based game engine.
# What could be improved The following is valuable feedback that we got from Google: **Feedback for Flame documentation** 1. It needs an introduction. - [x] It lacks an explanation...
# Current bug behavior `ScaleDetector` doesn't work when a Component with `DragCallbacks` is added. # Expected behavior Scale gesture (pinch-to-zoom) should work regardless if a Component with `DragCallbacks` is registered....
# What could be improved I was wondering if it is possible to allow `RiverpodComponentMixin` and `RiverpodGameMixin` to be a mixin on the same class. Currently this is not possible...
# What could be improved Flame Jenny is pretty good framework for dialogues, thank you for create this framework, I need this. But I cost too much time to learn...
# What could be improved Add tests for `flame_texturepacker`. # Why should this be improved Because we should have a well tested codebase. # Any risks? No. # More information...
# Current bug behavior Removed childrent are re-added into component whish moved from one parent to another at same update cycle. # Expected behavior Removed components are removed. They should...
# Current bug behavior After a particular sequence of adding and removing component children with different priority values, the children will become ordered incorrectly resulting in incorrect rendering. # Expected...
# Current bug behavior I noticed that states are being emitted twice in the flame_bloc game demo here: https://github.com/flame-engine/flame/blob/main/packages/flame_bloc/example/lib/src/game/game.dart seems to be the result of these children getting added twice;...
# Current bug behavior When using a `CircleComponent` with `ComponentParticle`, an exceptions gets raised for `CircleComponent._centerOffset` not being initialized. This happens because components added to `ComponentParticle` are not really part...
# Problem to solve With `Row` and `Column` classes children `Component`s could be placed and layouted correctly without overlapping and without having to care about repeating size and position calculations....
