PlayerController/AIController Pattern

[kaluluosi]

Allow custom actor on the BeehaveRoot node #9

Discussion for a good pattern for decoupled from the character logic and Input handle.
Purpose to implement character possess like Super Mario Odyssey.

This discussion is not about Beehave, but is a good way to switch ai proxy and player controll.

@Donorhan

[plandem]

it would be great, since rn you will probably have FSM for player and BT for npc, while logic can be pretty much the same

[Shadowblitz16]

I would like to know how to do this also.
I am still trying to wrap my head around behavior trees and I'm not sure how to go about checking input and applying it

[kaluluosi]

Unreal Engine has this pattern，but I don't know how to implement in Godot .

[lostptr]

Based on what I understand of Godots principles, I think this would be the approach:

• Goomba.gd would have all the code for walking, jumping and attacking but would not call any of those methods by itself.
• EnemyAI would be the beehave tree for the enemy to decide when to walk, jump, attack, etc... and then would call its parents methods for doing so.
• Player.gd would be then one to listen to the players input and call the parents methods when necessary.

[kaluluosi]

Yeb! That the point. You see, all the tutorial and official demo put the player input logic in process / physic_process . In your idea, Character don't handle player input, the PlayerController handle it and controls the "puppy" charactor. And AIController is inherit by PlayerController.

[lostptr]

Actually, the Player and EnemyAI dont even need to inherit from one another. All of the shared code will be in the Character script (ie Goomba.gd). This way, the EnemyAI can be a beehave tree and the player can simply be a script.

[kaluluosi]

Hey guys. I make it myself. It look good.

2d-platform.DEBUG.2024-01-14.05-02-53.mp4

Easy to create a Local Multiplayer Game.

2d-platform.DEBUG.2024-01-14.05-14-52.mp4