I know Kung Fu

And when I say Kung Fu I mean making a basic Behaviour Tree in Godot 4. This past week I have been quite busy wrapping my head around it, as I struggled quite a bit understanding how to organise and separate the different bits of enemy logic in the project.

I made a simple AI (of the good variety) that consist of the different behaviours:
- Wander inside an area
- Detect Targets
- Chase
- Attack
- Flee
- Center the move area

Some sketches I made on my Nomad for the hammer game. Some of them are ideas for enemies and boss battles, the monkey is a draft of the player character.

New update: I have programmed some objects that have physics and can interact with the player attacks .

You can even aim an object towards another one, or an enemy (for now, I call enemy to the green sphere ) before hitting it with the hammer to make it fly towards it and cause some damage.

I finished working on the "aim assist" feature of the game. I recorded a short video using the keyboard to play so that you can see it in action, in the worst case scenario, when only moving in 8 directions.

As long as players are loosely looking at a target, the attack will aim automatically and land even while dolphin diving!

Loading #Godot 4 shaders as custom effects is now possible. In the future (maybe v1.2? ), we plan to create a custom effect graph which will let users create effects directly within Pixelorama itself.

The shader in the video is from https://godotshaders.com/shader/protean-clouds/

Alright, since the last update a couple of things have happened:
First, I added some hit boxes to the player character. Then I wrote a system that checks for collisions when using attacks. Lastly, I have been working on some "enemies" and some feedback effects to check whether hitting stuff with the hammer feels fun and rewarding.

It looks quite promising so far, but I have noticed that aiming at enemies can be tricky at times, so I am going to focus on fixing that next.

I updated the character controller to use a state machine as well, and I cleaned up the animation tree a little bit following advice from the replies.

Using the state machine for this controller has eased A LOT the development process. Less bugs, easier to scale and maintain. I can't wait to keep adding new stuff!

So far, since the last update, I added:
- Aerial attacks
- Hammer Throws
- Dolphin dives
- Momentum to certain player moves

This is my first time using the 'AnimationTree' node, and let me tell you, it was a mess as each new animation complicated my state machine more and more. Hopefully once every mechanic is implemented I will find a way to clean it up, as I am sure I won't be able to maintain this the moment I start working on some other part of the project.

Any suggestions or learning resources is welcome