Samuel Batista

I think we should either keep the current implementation (by passing around classes with blank constructors), or allow users to instantiate their own states and change what state is active...

In that case, I suggest we leave this alone, or adopt a robust state machine that would handle state stacking. That would eliminate the need for FlxSubStates, allowing users to...

Here are some more resources regarding state stacks: http://gamedev.stackexchange.com/questions/1783/game-state-stack http://gamedevelopment.tutsplus.com/tutorials/finite-state-machines-theory-and-implementation--gamedev-11867 (especially the part that mentions **Stack-Based FSM**) Here's a sample implementation of a game state FSM on XNA: http://xbox.create.msdn.com/en-US/education/catalog/sample/game_state_management

This is a good idea, but a lot of work. Careful testing would be required before a merge is considered.

Yeah... HaxeFlixel is definitely an inheritance based game engine. Changing that would be like changing the entire engine. Don't think this is a good idea.

Your scripting system is very interesting! I wonder if we could add a subset of it to flixel-addons repo.

Yeah, please use a pull request to address this issue: https://help.github.com/articles/using-pull-requests

I'm ok with letting this slide for a later release, unless it gets done by 02/01/16, I would be hesitant to merge this change for 4.0 release.

I also ran into this issue, please make a PR, someone will merge it!

Same, I get actions and their names, but the state doesn't reflect what's in my stores anymore. **Update:** The issue only seems to occur on the version from the Chrome...