New AI for Mobs

[tigerw]

How's stuff going? Cannot wait for AI!

[SamJBarney]

Its going good. I haven't pushed anything recently just because I am busy with work, but look for a good chunk of code coming up in the next two weeks.

[SamJBarney]

So I've worked out how I think the restructuring of the mob classes should work:


I'm using cUndead and cBaby as mixins to alter how the mobs act. cUndead will handle daylight burning and seeking shade during the day. cBaby will handle the logic for growing up and following the closest adult of that type.

[NiLSPACE]

Baby zombies don't grow up as far as I know. I could be wrong though.

[SamJBarney]

True, but that is why they do not inherit from cBaby

[xoft]

Is it wise to have separate classes for grownups and babies? When a baby grows up, does it need to be destroyed and recreated as a different class? Wouldn't a flag in the class be enough? (Mojang does that - they have a cAgeable, from which the respective classes inherit.

---

Also, why have different classes for the different horses, when all they differ in is the color flag? You don't have a cBlueSheep either

[SamJBarney]

Xombie and Skeleton horses have to burn. That's the only difference. And yeah, the baby code could probably be moved into the main class...

[xoft]

Loading will be tough for separate horse classes.

[SamJBarney]

Loading?

[xoft]

In the MCA files, you will get a "horse" tag, but you'll have to decide which class to use, then have at least 2 separate functions for loading horses - the normal ones and the undead ones - because they won't have a common horse ancestor. It's not impossible, just... impractical.

---

Do the undead horses even burn in vanilla? I've never seen one, as far as I know, they aren't obtainable without editors.

---

I've watched a few videos, the horses don't burn. No point in making them a separate class, then.