Adjustments, because “Tweak” is a naughty word

An astute eye probably caught that my bokken slash didn’t actually connect with the kittri in the last screenshot.  One of the longest standing bugs in the game was the overly large and mispositioned collision zone of Arashi’s attacks, which really shouldn’t have been an issue for that long, I was just lazy about fixing it.  Needless to say it’s been taken care of now 😡

There’s still a little fine tuning I want to add to the AI… when a monster is close enough it’ll sometimes hop around to Arashi’s side before biting at her.  Some might actually consider it pretty smart, especially when the Defend button is implemented (one of the additions for this week) but it’s unintended and kind of unnatural for a low level mob to be using advanced combat tactics.  Once I get home from work (yes, I do have a real job while I’m doing this!)  I will make a check to see if the monster is already close enough to melee, if so then it won’t try to move.

Some other things I need to adjust: Arashi’s base movement speed.  Thinking about it, I think she moves too fast which makes controls a little loose.  When she’s Dashing I don’t mind as much, but normal movement should be a little easier to put her in the right position to attack exact areas, especially for the design of the later bosses.

I’ve added invisible collisions to the MapObject class, which will help in shaping collisions for oddly shaped objects.  This will also come into play when I add what I call ‘usecode’, or basically RPG scripting for searching, collecting, and general interaction.  I already have a very robust usecode routine from the OpenGL game I tried to make, so I can just copy all that over (it was very easy to use and powerful too).

Also, mental note: I need to add a weather layer.  Nothing sets an atmosphere better than weather, especially since a majority of the game is outdoors.  Unfortunately, the Foxfire Empire isn’t known for its snow, which is what I would have liked to add the most 🙁