UPDATE:
- Reworked the player state machine so it's clean and consistent.
It wasn't 'terrible' before, but it definitely needed reworking to ensure I'll avoid future headaches and lost time.
- Reworked the game state machine and added a lot of new game states.
For e.g. a state for scenes where the character is controlled by a sort of timeline, movies (planning to do a little rotoscoping for key moments of the game, like when you get your sword), menu, etc. - even some dev stuff, like a world editing state.
- Converted an "impact freeze" effect to a game state.
- Improved on some fluidity and game feel in player mechanics by allowing some jump and attack buffering in certain states.
- Various code and asset cleanup, mostly to give more sensible grouping and organization to remain manageable as the project grows.
The huge thing this weekend was not the basic textboxes, actually (that took very little time), but it was properly reworking the player state machine without totally ruining it (I honestly lost all of Friday and nearly half of Saturday because my first attempt did totally ruin it...), and it also took a bit of time planning the game states to allow for complex scenes, for properly pausing in each state, and setting up for everything the game will need in the future.
Next weekend, the plan is to continue work on the text engine, implementing "item get" stuff and to add a possibility for some textboxes to show an image above it, which would be used for showing pictures of the item that the text below says you've obtained. I may also use the picture for character busts later, though I only really have a shopkeeper and a secret Easter egg character, so it's not like this game will have many characters. It's largely a story about a lone character and his spirit sword. Any other characters wouldn't play much of a role.
