Submissions from 2022-05-24 to 2022-05-25 (1 total)

i still pretty much just want to sit down and watch a bunch of videos about other people making rpg features because i don't feel like i know what i'm doing, but as long as i get any motivation to implement something i'm trying to act on it.

i went and grabbed a quick sword swinging animation from mixamo so i could at least make it possible to perform the attack as an action (to later strap into some kind of complicated weapon system).

everything since working on slopes has reminded me that the player is probably going to need some kind of state machine soon. but is that the right solution? should there be one single state machine for the entire player, or maybe two to divide between locomotion (lower half of body) and action (upper half of body)? implementing something wrong is kind of exciting, but getting a good idea from a person who has made these mistakes before, and then working on a naive implementation of that myself might feel even better.