Jump to content

Projectile Rendering Post gone wrong (not really)


crazyjackel

Recommended Posts

yo, i am pretty sure the experienced guys on this forum hear this alot, "oh no rendering isnt working". i myself have read at least 10 posts on that, but for some reason none of them seem to work in my situation. everything about my projectile is running smooth, except that my registerEntityRenderingHandler is deprecated, and i know i am supposed to add either a new renderer or IrenderFactory, its probably a few lines of code fix, so just help me out and move on with your day

 

 

Client proxy; named just pure Client: http://pastebin.com/KN1eGBvy

- note in actual code registerEntityRenderingHandler is crossed out

 

oh btw if you want more code bits, let me know, but im pretty sure the error is just here

Link to comment
Share on other sites

okay i ran it how it was with RenderingRegistry.registerEntityRenderingHandler(EssenceSplashEffect.class, RenderSnowball::new);

 

which had an error that the thing couldnt figure out on the left side

 

 

heres the report:

http://pastebin.com/gaaG681j

 

 

 

what i think i am supposed to do is copy RenderSnowball and just rename everything into RenderEssenceSplash

 

my idea came from this post which basically stated that they were trying to do the same thing:

http://www.minecraftforge.net/forum/index.php?topic=8064.0

Link to comment
Share on other sites

RenderSnowball

doesn't have a constructor with a single

RenderManager

argument, so you can't use

RenderSnowball::new

as an

IRenderFactory

. Use a lambda or subclass of

RenderSnowball

(anonymous or named) instead.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Link to comment
Share on other sites

so i should make a renderer that extends render snowball and make a method that returns the rendermanager?

 

note: trust me, i am very new to program lingo

 

i am currently testing using RenderArrow as it doesnt give me the same error as render snowball

 

can someone affirm that i am moving in the correct direction by making a new class that extends rendersnowball then adding in the rendering thats like render arrow

Link to comment
Share on other sites

so i should make a renderer that extends render snowball

That was one of the options I presented, yes.

 

and make a method that returns the rendermanager?

No.

 

Create a class that extends

RenderSnowball

and has a constructor that takes a single

RenderManager

argument. Call the super constructor with this argument, the

Item

to render and the

RenderItem

instance. Use a method reference to this constructor (i.e.

RenderFooBar::new

) as the

IRenderFactory

implementation.

 

Alternatively, use a lambda as the

IRenderFactory

implementation. In this lambda, create an instance of

RenderSnowball

with the appropriate arguments. You could also use an anonymous class instead of a lambda.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Link to comment
Share on other sites

java.lang.NoSuchMethodException: net.minecraft.src.EssenceSplashEffect.<init>(net.minecraft.world.World)

    at java.lang.Class.getConstructor0(Class.java:3082) ~[?:1.8.0_91]

    at java.lang.Class.getConstructor(Class.java:1825) ~[?:1.8.0_91]

    at net.minecraftforge.fml.common.network.internal.EntitySpawnHandler.spawnEntity(EntitySpawnHandler.java:96) [EntitySpawnHandler.class:?]

    at net.minecraftforge.fml.common.network.internal.EntitySpawnHandler.process(EntitySpawnHandler.java:54) [EntitySpawnHandler.class:?]

    at net.minecraftforge.fml.common.network.internal.EntitySpawnHandler.access$000(EntitySpawnHandler.java:29) [EntitySpawnHandler.class:?]

    at net.minecraftforge.fml.common.network.internal.EntitySpawnHandler$1.run(EntitySpawnHandler.java:44) [EntitySpawnHandler$1.class:?]

 

Every

Entity

class must have a constructor that takes a single

World

argument. This is used to create the entity on the client.

 

Side note: Why are you creating classes in the

net.minecraft.src

package? Use a package unique to your mod, e.g.

com.<yourname>.<yourmod>

.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Link to comment
Share on other sites

choonster, hopefully this is the final time, man i really appreciate what you have done for me, without you this wouldve taken at least 2 days to get right. man i am so happy that im getting 1 step closer to doing something cool and developing this mod im working on, so just plz help me figure out what this all means one last time

 

http://pastebin.com/vYrfQMTp

Link to comment
Share on other sites

java.lang.NullPointerException: Rendering entity in world

    at net.minecraft.item.ItemStack.getMetadata(ItemStack.java:286)

    at net.minecraft.client.renderer.ItemModelMesher.getMetadata(ItemModelMesher.java:68)

    at net.minecraft.client.renderer.ItemModelMesher.getItemModel(ItemModelMesher.java:41)

    at net.minecraft.client.renderer.entity.RenderItem.renderItem(RenderItem.java:262)

    at net.minecraft.client.renderer.entity.RenderSnowball.doRender(RenderSnowball.java:41)

    at net.minecraft.client.renderer.entity.RenderManager.doRenderEntity(RenderManager.java:380)

    at net.minecraft.client.renderer.entity.RenderManager.renderEntityStatic(RenderManager.java:337)

    at net.minecraft.client.renderer.entity.RenderManager.renderEntitySimple(RenderManager.java:304)

    at net.minecraft.client.renderer.RenderGlobal.renderEntities(RenderGlobal.java:672)

    at net.minecraft.client.renderer.EntityRenderer.renderWorldPass(EntityRenderer.java:1368)

    at net.minecraft.client.renderer.EntityRenderer.renderWorld(EntityRenderer.java:1282)

    at net.minecraft.client.renderer.EntityRenderer.updateCameraAndRender(EntityRenderer.java:1110)

    at net.minecraft.client.Minecraft.runGameLoop(Minecraft.java:1107)

    at net.minecraft.client.Minecraft.run(Minecraft.java:380)

    at net.minecraft.client.main.Main.main(Main.java:116)

 

Minecraft is trying to render an

ItemStack

with a

null

Item

. This is because you passed

null

as the

Item

argument of the

RenderSnowball

constructor.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Link to comment
Share on other sites

public class RenderEssenceSplash extends RenderSnowball

{

 

public RenderEssenceSplash(RenderManager renderManagerIn) {

super(renderManagerIn, Main.EssenceSplash, Minecraft.getMinecraft().getRenderItem());

 

}

 

 

}

 

 

im not sure which on is the item render constructor, but can you plz quickly explain how to make it alright, come on, i almost got it

Link to comment
Share on other sites

public class RenderEssenceSplash extends RenderSnowball

{

 

public RenderEssenceSplash(RenderManager renderManagerIn) {

super(renderManagerIn, Main.EssenceSplash, Minecraft.getMinecraft().getRenderItem());

}

}

 

 

im not sure which on is the item render constructor, but can you plz quickly explain how to make it alright

 

Main.EssenceSplash

is the

Item

argument, so it was

null

when the constructor was called. Either you're assigning the field a value at some point after the constructor is called or you're never assigning it a value.

 

In future, use [nobbc]

 

[/nobbc] tags when posting code.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Link to comment
Share on other sites

Let me be a bit more specific: Post the class where you call

EntityRegistry.registerModEntity

, the class where you call

RenderingRegistry.registerEntityRenderingHandler

, the class that calls those classes and your

Render

class. Also post your FML log.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Link to comment
Share on other sites

The FML log is saved to logs/fml-client-latest.log in the game directory.

 

Things you need to fix:

  • RenderingRegistry.registerEntityRenderingHandler

    must be called in preInit.

  • Block

    s,

    Item

    s and other

    IForgeRegistryEntry

    implementations should be registered in preInit. The same goes for entities.

  • Item models should be registered in preInit from your client proxy (not your
    @Mod

    class, you'll crash the dedicated server) with

    ModelLoader.setCustomModelResourceLocation

    /

    setCustomMeshDefinition

    rather than in init with

    ItemModelMesher#register

    .

  • GameRegistry.registerItem

    and

    GameRegistry.findItem

    are deprecated, look at their doc comments for the replacements.

 

Event handler registration can be done in any phase, so that can stay where it is.

 

I did notice the

MormonBook

item.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Link to comment
Share on other sites

okay did some research, gameregistry is not deprecated in 1.8.9 but has some deprecated commands which im not using

 

Ah, I didn't notice that you were using 1.8.9. I'd recommend updating to 1.9.4.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Link to comment
Share on other sites

this mod is mostly in development for mainly me and my friends, i am not really confident in my skill to update it as such, btw i defined modelloaders in the preinit of client-my client proxy. how would i load those onto an item

 

 

Item CowEssenceItem = GameRegistry.findItem("essence", "CowEssence");
	ModelResourceLocation CowEssenceModel = new ModelResourceLocation("essence:CowEssence", "Inventory");
	ModelLoader.setCustomModelResourceLocation(CowEssenceItem, 0, CowEssenceModel);

 

these dont auto-attach to the item

 

 

wow second page already for a 'simple fix'

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

  • Who's Online (See full list)

    • There are no registered users currently online
×
×
  • Create New...

Important Information

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