Jump to content

Non-Living Entity Tracking Method: EntityRegistry.registerModEntity


Vertice

Recommended Posts

Heya, this is my first post! :)

 

I am finishing migrating my 1.2.5 modloader mod to the latest Forge because risugami posted this image: http://tiny.cc/PAIN and I am having problems registering my NON-living entities. I use the method called registerModEntity as well as the method registerGlobalEntityID, and my problem is that when I set SendsVelocityUpdates parameter in registerModEntity to true, my non-living entity does not render in server or in singleplayer. it only temporarily appears sometimes, then disappears. If I set it to false, it renders, but it sort of sidewinds then faces downward and keeps flying. I am using an entity with almost replicated behavior to that of an arrow, but with modified physics and different actions and reactions. The pitch and yaw handling is untouched. The code for registering my entity is right here:

    EntityRegistry.registerModEntity(EntityRocket.class, "RPGRocket", rpgrocketID, this, 250, 1, false);
    EntityRegistry.registerGlobalEntityID(EntityRocket.class, "RPGRocket", rpgrocketID);

The IDs are variables because they are written in the config file. For the rocket ID I am using 26 as a default. I believe it is not occupied, and other of my entities are using different IDs. None of my entities work as they used to, but if you help me fix one I can fix them all easily. I am also registering the renderers in my proxy by calling it in the load method like this:

if (event.getSide().isClient()) {
      ClientProxy.registerRenderInformation();
}

I use an if statement, then the class ClientProxy, because if I use proxy (a variable declared earlier with the @SidedProxy stuff) without the if statement, all my entities render as white boxes. The method in the ClientProxy contains:

RenderingRegistry.registerEntityRenderingHandler(EntityRocket.class, new RenderRocket());

as-well as my block  textures and my other entity renderers.

My render file is the arrow render file with my texture in it, the imports, and the name changes (including EntityRocket instead of EntityArrow as the parameters).

Please do not come here and call me a noob, because I actually am not. I know my java :)

 

Thanks in advance, ~Rodol

Link to comment
Share on other sites

I'll show you how I did mine. This is probably the best way to use proxies. Note: Common proxy's DayZload method is empty. Hope this helps :D

 

 

The mod file:



      @SidedProxy(clientSide = "dayz.common.ClientProxy", serverSide = "dayz.common.CommonProxy")
    public static CommonProxy proxy;
     @Init
    public void DayZload(FMLInitializationEvent event)
    {
        EntityRegistry.registerModEntity(EntityBullet.class, "Bullet", 1, this, 250, 5, true);
         proxy.DayZload();
    }

ClientProxy:

 



@Override
   public void DayZload() 
   {
        RenderingRegistry.registerEntityRenderingHandler(EntityBullet.class, new RenderBullet());
   }

 

 

 

Link to comment
Share on other sites

I have changed my code so that it is like yours. I removed

EntityRegistry.registerGlobalEntityID(EntityRocket.class, "Rocket", rpgrocketID);

and changed my

if (event.getSide().isClient())
{
      ClientProxy.registerRenderInformation();
}

to

proxy.registerRenderInformation();

with "proxy" declared like yours with the package changes. Here is how i declared mine:

@SidedProxy(clientSide = "RivalRebels.common.ClientProxy", serverSide = "RivalRebels.common.CommonProxy")
public static CommonProxy proxy;

I also have the method in the CommonProxy as well as the ClientProxy, with the ClientProxy having the render registries.

Thanks for replying, but my problem remains, and now instead of the old problem, there are white boxes that dissapear instantly. It appears that they may be colliding with the person shooting, but the if statement that prevents the entity from colliding with the shooter within the first five seconds is still left untouched. I fiddled around with it but to no prevail.

Thanks in advance, ~Rodol

Link to comment
Share on other sites

Hmm I'm not too sure about this white box problem but it seems to be a render issue. I had some problems getting my bullets to render when they extended EntityArrow/RenderArrow so I changed them to extend EntityThrowable/RenderThrowable which simplified a lot of things, especially textures. I can also suggest making sure in your EntityRocket class that the rocket spawn position is correct.

Link to comment
Share on other sites

Thanks for the help!

The problem was where I was spawning it. For some reason it was falsely colliding (which it never did this before, and it shouldn't) and it was hitting the player and not rendering any more, but still there, because it would keep flying and hit the ground and make the rocket explosion. What I did to workaround this odd glitch was I made it so that on the first tick that the rocket is spawned, I set the position to the current position, plus the object's motion*2, plus the shooter's motion if there is any. I add the shooters motion because if you are running and shoot, it will stop rendering because of a temporary collision with the shooter. I did this instead of multiplying the motion of the rocket times 3 instead of 2 because it would pass through walls if I did. Here is the code:

if (ticksInAir == 0 && shootingEntity instanceof EntityPlayer)
{
    this.setPosition(posX + motionX * 2 + shootingEntity.motionX, posY + motionY * 2 + shootingEntity.motionY, posZ + motionZ * 2 + shootingEntity.motionZ);
}

Something odd is that only the render breaks, but not the entity. It still makes the explosion, but doesn't render while it flies. Maybe the entitytracker isnt tracking it after it sort of "collides" falsely? I have no idea.

Sorry for the late post too, ~Rodol

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

    • rp.crazyheal.xyz mods  
    • 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.