Jump to content

[SOLVED] Problems with entity sizes


vilu

Recommended Posts

Does any one else have a problem with entity sizes or am I the only one?

It seems like the function this.setSize(float par1, float par2) has no effect anymore, it doesn't make mob bigger or smaller like it used to.

 

 

 

  public class EntityButterfly extends EntityAnimal {

  public int butterfly_type = 0;

  private boolean powered = false;

  private ChunkCoordinates currentFlightTarget = null;

  private GenericTargetSorter TargetSorter = null;

   

public EntityButterfly(World par1World) {

super(par1World);

this.setEntityHealth(2);

this.worldObj = par1World;

this.butterfly_type = rand.nextInt(4);

              this.setSize(0.45F, 0.45F);

              this.experienceValue = 0;

              this.getNavigator().setAvoidsWater(true);

              TargetSorter = new GenericTargetSorter(this);

}

 

//and so on...

 

 

 

I would also want to know is it ok to register renders at void init() in client proxy (like RenderingRegistry.registerEntityRenderingHandler(EntityButterfly.class, new RenderButterfly(new ModelButterfly(1.0F), 0.2F, 0.45F)); ) or is the problem maybe there?

Link to comment
Share on other sites

I believe setSize only sets the size of the hitbox, the part that's used for collision detection, and not how it's actually rendered. To change the render size, you probably need your own render class, and to set the size I would use the code from RenderCaveSpider.

    protected void preRenderCallback(EntityLivingBase par1EntityLivingBase, float par2)
    {
        this.scaleSpider((EntityCaveSpider)par1EntityLivingBase, par2);
    }
    protected void scaleSpider(EntityCaveSpider par1EntityCaveSpider, float par2)
    {
        GL11.glScalef(0.7F, 0.7F, 0.7F);
    }

Post that into your entity rendering class, and replace every instance of EntityCaveSpider with EntityButterfly. The floats inside the glScalef method will determine the render size.

Link to comment
Share on other sites

Just a pet peeve, but I really hate it when people have problems with a method they say" this.blahblah isn't working!". For one thing we have no idea half the time what "this" is and it would be better if you stated the class that the method originated from.

This is the creator of the Rareores mod! Be sure to check it out at

Link to comment
Share on other sites

Just a pet peeve, but I really hate it when people have problems with a method they say" this.blahblah isn't working!". For one thing we have no idea half the time what "this" is and it would be better if you stated the class that the method originated from.

 

My pet peeve is people saying "X isn't working!" without posting the error or code (or worse, neither).

 

My response is to add more cheese.

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Link to comment
Share on other sites

I believe setSize only sets the size of the hitbox, the part that's used for collision detection, and not how it's actually rendered. To change the render size, you probably need your own render class, and to set the size I would use the code from RenderCaveSpider.

    protected void preRenderCallback(EntityLivingBase par1EntityLivingBase, float par2)
    {
        this.scaleSpider((EntityCaveSpider)par1EntityLivingBase, par2);
    }
    protected void scaleSpider(EntityCaveSpider par1EntityCaveSpider, float par2)
    {
        GL11.glScalef(0.7F, 0.7F, 0.7F);
    }

Post that into your entity rendering class, and replace every instance of EntityCaveSpider with EntityButterfly. The floats inside the glScalef method will determine the render size.

 

I already have renderer, check below

 

 

public class RenderButterfly extends RenderLiving {

 

private static final ResourceLocation skin0 = new ResourceLocation("newmobs:textures/entities/butterfly1.png");

private static final ResourceLocation skin1 = new ResourceLocation("newmobs:textures/entities/butterfly2.png");

private static final ResourceLocation skin2 = new ResourceLocation("newmobs:textures/entities/butterfly3.png");

private static final ResourceLocation skin3 = new ResourceLocation("newmobs:textures/entities/butterfly4.png");

private static final ResourceLocation armoredSkin = new ResourceLocation("newmobs:textures/entities/butterfly/armor.png");

 

protected ModelButterfly model;

public float scale = 0.45F;

public World worldObj;

public Random rand = new Random();

 

public RenderButterfly(ModelButterfly par1ModelBase, float par2, float par3) {

super(par1ModelBase, par2 * par3);

model = ((ModelButterfly)mainModel);

this.scale = par3;

worldObj = Minecraft.getMinecraft().theWorld;

}

 

private ResourceLocation changingSkin() {

return null;

}

 

    public void renderButterfly(EntityButterfly par1EntityButterfly, double par2, double par4, double par6, float par8, float par9)

    {

        super.doRenderLiving(par1EntityButterfly, par2, par4, par6, par8, par9);

    }

 

    public void doRenderLiving(EntityLiving par1EntityLiving, double par2, double par4, double par6, float par8, float par9)

    {

        this.renderButterfly((EntityButterfly)par1EntityLiving, par2, par4, par6, par8, par9);

    }

 

    /**

    * Actually renders the given argument. This is a synthetic bridge method, always casting down its argument and then

    * handing it off to a worker function which does the actual work. In all probabilty, the class Render is generic

    * (Render<T extends Entity) and this method has signature public void doRender(T entity, double d, double d1,

    * double d2, float f, float f1). But JAD is pre 1.5 so doesn't do that.

    */

    public void doRender(Entity par1Entity, double par2, double par4, double par6, float par8, float par9)

    {

        this.renderButterfly((EntityButterfly)par1Entity, par2, par4, par6, par8, par9);

    }

   

    /**

    * Applies the scale to the transform matrix

    */

    protected void preRenderScale(EntityButterfly par1Entity, float par2)

    {

        GL11.glScalef(this.scale, this.scale, this.scale);

    }

 

    /**

    * Allows the render to do any OpenGL state modifications necessary before the model is rendered. Args:

    * entityLiving, partialTickTime

    */

    protected void preRenderCallback(EntityLiving par1EntityLiving, float par2)

    {

        this.preRenderScale((EntityButterfly)par1EntityLiving, par2);

    }

   

    /**

    * Queries whether should render the specified pass or not.

    * We do our own effects here.

    */

    public int shouldRenderPass(EntityLiving par1EntityLiving, int par2, float par3)

    {

    //TODO: Make this work (before that we go with normal lights and textures)

        GL11.glMatrixMode(GL11.GL_TEXTURE);

    GL11.glLoadIdentity();

    GL11.glMatrixMode(GL11.GL_MODELVIEW);

    GL11.glEnable(GL11.GL_LIGHTING);

    GL11.glDisable(GL11.GL_BLEND);

                                            return -1;

    }

 

    protected ResourceLocation func_110874_a(EntityButterfly par1EntityButterfly) {

    switch (par1EntityButterfly.getSkin()) {

case 0:

return skin0;

case 1:

return skin1;

case 2:

return skin2;

case 3:

return skin3;

default:

return skin0;

}

    }

   

@Override

protected ResourceLocation func_110775_a(Entity par1Entity) {

return this.func_110874_a((EntityButterfly)par1Entity);

}

 

 

}

 

 

 

Everything was running ok (with 1.5.2 and before) when I changed setSize in EntityButterfly and also registered renderer with same size (like RenderingRegistry.registerEntityRenderingHandler(EntityButterfly.class, new RenderButterfly(new ModelButterfly(1.0F), 0.2F, 0.45F)); ) but now it just doesn't so I think the problem is somewhere else but thanks any way =)

 

For Noah_Beech, I said this.setSize because I have this same problem with every entity when the size is anything else than normal..

Link to comment
Share on other sites

All I had to do with mine is change:

protected void preRenderCallback(EntityLiving par1EntityLiving, float par2)

To:

protected void preRenderCallback(EntityLivingBase par1EntityLiving, float par2)

 

Thank you so much! I've been so blind... (/me feels stupid)

When the 1.6.1 came out I fixed those EntityLiving parts that didn't work anymore and somehow missed these...It seems like I got source blindness =D

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • I'm developing a dimension, but it's kinda resource intensive so some times during player teleporting it lags behind making the player phase down into the void, so im trying to implement some kind of pregeneration to force the game loading a small set of chunks in the are the player will teleport to. Some of the things i've tried like using ServerLevel and ServerChunkCache methods like getChunk() dont actually trigger chunk generation if the chunk isn't already on persistent storage (already generated) or placing tickets, but that doesn't work either. Ideally i should be able to check when the task has ended too. I've peeked around some pregen engines, but they're too complex for my current understanding of the system of which I have just a basic understanding (how ServerLevel ,ServerChunkCache  and ChunkMap work) of. Any tips or other classes I should be looking into to understand how to do this correctly?
    • https://mclo.gs/4UC49Ao
    • Way back in the Forge 1.17 days, work started for adding JPMS (Java Platform Module Support) to ModLauncher and ForgeModLoader. This has been used internally by Forge and some libraries for a while now, but mods (those with mods.toml specifically) have not been able to take advantage of it. As of Forge 1.21.1 and 1.21.3, this is now possible!   What is JPMS and what does it mean for modders? JPMS is the Java Platform Module System, introduced in Java 9. It allows you to define modules, which are collections of packages and resources that can be exported or hidden from other modules. This allows for much more fine-tuned control over visibility, cleaner syntax for service declarations and support for sealed types across packages. For example, you might have a mod with a module called `com.example.mod` that exports `com.example.mod.api` and `com.example.mod.impl` to other mods, but hides `com.example.mod.internal` from them. This would allow you to have a clean API for other mods to use, while keeping your internal implementation details hidden from IDE hints, helping prevent accidental usage of internals that might break without prior notice. This is particularly useful if you'd like to use public records with module-private constructors or partially module-private record components, as you can create a sealed interface that only your record implements, having the interface be exported and the record hidden. It's also nice for declaring and using services, as you'll get compile-time errors from the Java compiler for typos and the like, rather than deferring to runtime errors. In more advanced cases, you can also have public methods that are only accessible to specific other modules -- handy if you want internal interactions between multiple of your own mods.   How do I bypass it? We understand there may be drama in implementing a system that prevents mods from accessing each other's internals when necessary (like when a mod is abandoned or you need to fix a compat issue) -- after all, we are already modding a game that doesn't have explicit support for Java mods yet. We have already thought of this and are offering APIs from day one to selectively bypass module restrictions. Let me be clear: Forge mods are not required to use JPMS. If you don't want to use it, you don't have to. The default behaviour is to have fully open, fully exported automatic modules. In Java, you can use the `Add-Opens` and `Add-Exports` manifest attributes to selectively bypass module restrictions of other mods at launch time, and we've added explicit support for these when loading your Forge mods. At compile-time, you can use existing solutions such as the extra-java-module-info Gradle plugin to deal with non-modular dependencies and add extra opens and exports to other modules. Here's an example on how to make the internal package `com.example.examplemod.internal` open to your mod in your build.gradle: tasks.named('jar', Jar) { manifest { attributes([ 'Add-Opens' : 'com.example.examplemod/com.example.examplemod.internal' 'Specification-Title' : mod_id, 'Specification-Vendor' : mod_authors // (...) ]) } } With the above in your mod's jar manifest, you can now reflectively access the classes inside that internal package. Multiple entries are separated with a space, as per Java's official spec. You can also use Add-Exports to directly call without reflection, however you'd need to use the Gradle plugin mentioned earlier to be able to compile. The syntax for Add-Exports is the same as Add-Opens, and instructions for the compile-time step with the Gradle plugin are detailed later in this post. Remember to prefer the opens and exports keywords inside module-info.java for sources you control. The Add-Opens/Add-Exports attributes are only intended for forcing open other mods.   What else is new with module support? Previously, the runtime module name was always forced to the first mod ID in your `mods.toml` file and all packages were forced fully open and exported. Module names are now distinguished from mod IDs, meaning the module name in your module-info.java can be different from the mod ID in your `mods.toml`. This allows you to have a more descriptive module name that doesn't have to be the same as your mod ID, however we strongly recommend including your mod ID as part of your module name to aid troubleshooting. The `Automatic-Module-Name` manifest attribute is now also honoured, allowing you to specify a module name for your mod without needing to create a `module-info.java` file. This is particularly useful for mods that don't care about JPMS features but want to have a more descriptive module name and easier integration with other mods that do use JPMS.   How do I use it? The first step is to create a `module-info.java` file in your mod's source directory. This file should be in the same package as your main mod class, and should look something like this: open module com.example.examplemod { requires net.minecraftforge.eventbus; requires net.minecraftforge.fmlcore; requires net.minecraftforge.forge; requires net.minecraftforge.javafmlmod; requires net.minecraftforge.mergetool.api; requires org.slf4j; requires logging; } For now, we're leaving the whole module open to reflection, which is a good starting point. When we know we want to close something off, we can remove the open modifier from the module and open or export individual packages instead. Remember that you need to be open to Forge (module name net.minecraftforge.forge), otherwise it can't call your mod's constructor. Next is fixing modules in Gradle. While Forge and Java support modules properly, Gradle does not put automatic modules on the module path by default, meaning that the logging module (from com.mojang:logging) is not found. To fix this, add the Gradle plugin and add a compile-time module definition for that Mojang library: plugins { // (...) id 'org.gradlex.extra-java-module-info' version "1.9" } // (...) extraJavaModuleInfo { failOnMissingModuleInfo = false automaticModule("com.mojang:logging", "logging") } The automatic module override specified in your build.gradle should match the runtime one to avoid errors. You can do the same for any library or mod dependency that is missing either a module-info or explicit Automatic-Module-Name, however be aware that you may need to update your mod once said library adds one. That's all you need to get started with module support in your mods. You can learn more about modules and how to use them at dev.java.
    • Faire la mise à jour grâce à ce lien m'a aider personnellement, merci à @Paint_Ninja. https://www.amd.com/en/support 
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.