Edit of asset "Kane-FSM (Finite State Machine)" Accepted
Warning: Using Git tags or branches is no longer supported. Please give a full Git commit hash instead, or use the Custom download provider for GitHub Releases downloads.
If you think that this warning is incorrect, you can always open an issue.
If you think that this warning is incorrect, you can always open an issue.
Old/Current | New/Edit | |
---|---|---|
Title | Kane-FSM (Finite State Machine) | Kane-FSM (Finite State Machine) |
Description |
Flyweight, Easy Implementation, Code over UI, Brevity over Features Finite State Machine. ## Features - simple setup: inheritance for everything - documented: everything is commented, and delivered with working example - "auto-magic": few small helpers here and there ## Workflow 1. Download and Install from the Asset Store OR git clone this repo in your project OR download and unzip in your project OR do whatever to get your hands on the kane-FSM folder 2. Check the example folder code 3. Do your job, by creating your own FSM inheriting from the StateMachine and your states by inheriting the State provided, following the example 4. … 5. PROFIT! ## Philosophy There is already at least 2 FSM implementations in the asset store, why adding another one ? Because they are heavy weighted and complex. Technically this one is really close to the brandonlamb one, except simplier. I started to work on it between the first and the second video from Game Endeavor about FSM, so it's kinda like a fork. |
Flyweight, Easy Implementation, Code over UI, Brevity over Features Finite State Machine. ## Features - simple setup: inheritance for everything - documented: everything is commented, and delivered with working example - "auto-magic": few small helpers here and there ## Workflow 1. Download and Install from the Asset Store OR git clone this repo in your project OR download and unzip in your project OR do whatever to get your hands on the kane-FSM folder 2. Check the example folder code 3. Do your job, by creating your own FSM inheriting from the StateMachine and your states by inheriting the State provided, following the example 4. … 5. PROFIT! ## Philosophy There is already at least 2 FSM implementations in the asset store, why adding another one ? Because they are heavy weighted and complex. Technically this one is really close to the brandonlamb one, except simplier. I started to work on it between the first and the second video from Game Endeavor about FSM, so it's kinda like a fork. |
Category | Scripts | Scripts |
License | MIT | MIT |
Repository Provider | GitHub | GitHub |
Repository Url | https://github.com/kane-thornwyrd/kane-fsm | https://github.com/kane-thornwyrd/kane-fsm |
Issues Url | https://github.com/kane-thornwyrd/kane-fsm/issues | https://github.com/kane-thornwyrd/kane-fsm/issues |
Godot version | Godot 3.1 | Godot 3.1 |
Version String | 0.1 | 0.1 |
Download Commit | 0.1 | 0.1 |
Download Url (Computed) | https://github.com/kane-thornwyrd/kane-fsm/archive/0.1.zip | https://github.com/kane-thornwyrd/kane-fsm/archive/0.1.zip |
Icon Url |
https://raw.githubusercontent.com/kane-thornwyrd/kane-fsm/master/icon.big.png
|
https://raw.githubusercontent.com/kane-thornwyrd/kane-fsm/master/icon.big.png
|
Preview Insert | ||
---|---|---|
Type | video | |
Image/Video URL |
https://youtu.be/aUK89FnQDiI
|
|
Thumbnail |
https://img.youtube.com/vi/aUK89FnQDiI/0.jpg
|