Is it possible to have a multiple well animated hitbox for large entities

[Kiljaeden053]

Please bear with me for  I have not started yet and would discuss the concept and the idea properly before I start coding to prevent further complications. Just like ModelParts can hitboxes have child hitboxes and I have an idea that you can copy the position of the model when animated then send it to the server so that the hitboxes' position will be animated. Has anyone done this before? Is it even possible?

[Animefan8888]

8 hours ago, Kiljaeden053 said:

I have an idea that you can copy the position of the model when animated then send it to the server

This is not how client-server architecture works. The server determines where the hitbox is then sends that to the client. So you are going to need to control the animation on the server and update the hitboxes accordingly.

[Kiljaeden053]

But aren't animations supposed to be client only? Or just the model rendering.

[Animefan8888]

15 minutes ago, Kiljaeden053 said:

But aren't animations supposed to be client only? Or just the model rendering.

Just the rendering has to be client side only. Many things you want to animate in sync for players right? The only way to do that is by using the server to control the animation.

[Kiljaeden053]

22 minutes ago, Animefan8888 said:

Just the rendering has to be client side only. Many things you want to animate in sync for players right? The only way to do that is by using the server to control the animation.

Ahh ok. How about hitboxes having child hitboxes? 

[Alpvax]

13 hours ago, Kiljaeden053 said:

Ahh ok. How about hitboxes having child hitboxes?

Try looking at the ender dragon code. I havent looked in a long time (so it could well have changed) but it used to be made up of multiple parts.

[Animefan8888]

14 hours ago, Kiljaeden053 said:

Ahh ok. How about hitboxes having child hitboxes? 

Minecraft uses a single AABB as collision boxes for a single Entity. I suppose you could do a calculation inside Entity::getCollisionBox based on the entity it is asking about. Like return the closest AABB to the entity passed in.

 

Or definitely do what Alpvax said and check out the EnderDragon code.