Timeline for Managing Discrete Character Animation States
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 28, 2016 at 7:21 | answer | added | Giora Guttsait | timeline score: 1 | |
| Aug 28, 2016 at 7:15 | comment | added | Nikolai97 | @GioraGuttsait your first idea is very interesting, i would like to see that expanded as an answer. But as for your second comment, i could definitely move it to a new file, however the states are more about functionality than data. | |
| Aug 28, 2016 at 7:12 | comment | added | Giora Guttsait | Also, by the look of it, you can definitely load the StateComponent from a file, since it all looks template-y. So why not throw it in a configuration file? that way your code contains the logic of loading, and is not dealing with the data itself | |
| Aug 28, 2016 at 7:11 | comment | added | Giora Guttsait |
First of all, if you're able to further sort them, to stats = { walking = { left, right ...}, attacking = { left, right .. } ... }, It'd be a small change, but it's more organized than simply throwing it in a big table.
|
|
| Aug 28, 2016 at 4:23 | history | edited | Nikolai97 | CC BY-SA 3.0 |
edited title
|
| Aug 27, 2016 at 8:07 | history | asked | Nikolai97 | CC BY-SA 3.0 |