Hey folks.
I am working on a custom "Mecha" entity (extended from LivingEntity) that the player builds up from blocks that should get modular stats depending on the used blocks.
e.g. depending on what will be used for the legs, the entity will have a different jump strength.
However, something unexpected is happening when trying to override a few of LivingEntity's functions and using my new own "Mecha" specific fields: instead of their actual instance-specific value, the default value is used (0f for a float, null for an object...)
This is especially strange as when executing with the same entity from a point in the code specific to the mecha entity, the correct value is used.
Here are some code snippets to better illustrate what I mean:
/*
The main Mecha class, cut down for brevity
*/
public class Mecha extends LivingEntity {
protected float jumpMultiplier;
//somewhere later during the code when spawning the entity, jumpMultiplier is set to something like 1.5f
//changing the access to public didn't help
@Override //Overridden from LivingEntity, this function is only used in the jumpFromGround() function, used in the aiStep() function, used in the LivingEntity tick() function
protected float getJumpPower() {
//something is wrong with this function
//for some reason I can't correctly access the fields and methods from the instanciated entity when I am in one of those overridden protected functions. this is very annoying
LogUtils.getLogger().info(String.valueOf(this.jumpMultiplier))) //will print 0f
return this.jumpMultiplier * super.getJumpPower();
}
//The code above does not operate properly. Written as is, the entity will not jump, and adding debug logs shows that when executing the code, the value of this.jumpMultiplier is 0f
//in contrast, it will be the correct value when done here:
@Override
public void tick() {
super.tick(); //inherited LivingEntity logic
//Custom logic
LogUtils.getLogger().info(String.valueOf(this.jumpMultiplier))) //will print 1.5f
}
}
My actual code is slightly different, as the jumpMuliplier is stored in another object (so I am calling "this.legModule.getJumpPower()" instead of the float), but even using a simple float exactly like in the code above didn't help.
When running my usual code, the object I try to use is found to be null instead, leading to a crash from a nullPointerException. Here is the stacktrace of said crash:
The full code can be viewed here.
I have found a workaround in the case of jump strength, but have already found the same problem for another parameter I want to do, and I do not understand why the code is behaving as such, and I would very much like to be able to override those methods as intended - they seemed to work just fine like that for vanilla mobs...
Any clues as to what may be happening here?