Jump to content

[SOLVED] [1.11] Creating custom particles (java.lang.RuntimeException: Invalid call to Particle.setMiscTex)


Recommended Posts

Posted (edited)

Hey everyone,

So, for the passed hour or so, I've been trying to make a custom particle. I feel like I am on the absolute brink of getting it to work, after 100s upon 100s of crashes later! And boy... I have no clue where to go from here. So, let me right a numbered list of what's happening, and what is calling what.

 

"Chain of events":

  1. ModBlock calls  genMagicParticle() method in Common Proxy Class
  2. Client Proxy Class overrides Common Proxy Class' - genMagicParticle() method
  3. genMagicParticle() method creates a new instance of a ParticleMagic object, which extends ParticleCloud
    • Also adds this new  ParticleMagic instance to the effectRenderer --- Minecraft.getMinecraft().effectRenderer.addEffect()
  4. ParticleMagic sets particle colours through  particleRed, particleGreen, particleBlue and sets  particleMaxAge
  5. TextureStitchEvent.Pre gets a texture map and registers a new sprite pointing to my mod's particle PNG sheet
  6. ParticleMagic returns 1 in getFXLayer()
  7. ParticleMagic sets the particle texture (setParticleTexture()) to the registered sprite using the TextureStitchEvent.Pre.

 

And that's about everything. Here is the  relevant code  from each class:

 

InfusedLog ("ModBlock"):

public class BlockInfusedLog extends BlockWoodBase implements ITileEntityProvider {
    @SideOnly(Side.CLIENT)
    @Override
    public void randomDisplayTick(IBlockState stateIn, World worldIn, BlockPos pos, Random rand) {
        MonsterTotems.proxy.genMagicParticle(this, pos);
        super.randomDisplayTick(stateIn, worldIn, pos, rand);
    }
}

 

Common Proxy:

public class CommonProxy {
	public void genMagicParticle(Block block, BlockPos pos) {

	}
}

 

Client Proxy:

public class ClientProxy extends CommonProxy {	
	@Override
	public void genMagicParticle(Block block, BlockPos pos) {
	     World world = Minecraft.getMinecraft().world;

	     double rand = world.rand.nextDouble();
 	     double d1 = pos.getX() + rand;
	     double d2 = pos.getY() + 1;
 	     double d3 = pos.getZ() + rand;
 	     ParticleMagic particleMagic = new ParticleMagic(world, d1, d2, d3, rand * 0.4D, 0.7D, rand * 0.4D);
  
   	     Minecraft.getMinecraft().effectRenderer.addEffect(particleMagic);
	}
}

 

RegistryEventHandler:

@Mod.EventBusSubscriber
public class RegistryEventHandler {
	public static TextureAtlasSprite textureAtlasSprite;

	@SubscribeEvent
	public static void registerParticleMap(TextureStitchEvent.Pre event) {
        	TextureMap map = event.getMap();
        	textureAtlasSprite = map.registerSprite(new ResourceLocation(Reference.MODID, "particle/particles")); // Points to 'monstertotems:textures/particle/particles.png'
	}
}

 

ParticleMagic:

public class ParticleMagic extends ParticleCloud {
    public ParticleMagic(World worldIn, double xCoordIn, double yCoordIn, double zCoordIn, double xSpeedIn, double ySpeedIn, double zSpeedIn) {
        super(worldIn, xCoordIn, yCoordIn, zCoordIn, xSpeedIn, ySpeedIn, zSpeedIn);
        this.particleRed = 1;
        this.particleGreen = 0;
        this.particleBlue = 1;
        this.particleMaxAge = 1000000;
        this.setParticleTexture(RegistryEventHandler.textureAtlasSprite);
    }

    @Override
    public int getFXLayer() {
        return 1;
    }
}

 

Phew... that should be everything. Oh, one more thing, here is the crash report.

 

Crash Report:

Spoiler

[00:42:05] [Client thread/INFO]: [net.minecraft.init.Bootstrap:printToSYSOUT:600]: ---- Minecraft Crash Report ----
// You should try our sister game, Minceraft!

Time: 12/23/17 12:42 AM
Description: Ticking Particle

java.lang.RuntimeException: Invalid call to Particle.setMiscTex
	at net.minecraft.client.particle.Particle.setParticleTextureIndex(Particle.java:261)
	at net.minecraft.client.particle.ParticleCloud.onUpdate(ParticleCloud.java:60)
	at net.minecraft.client.particle.ParticleManager.tickParticle(ParticleManager.java:243)
	at net.minecraft.client.particle.ParticleManager.tickParticleList(ParticleManager.java:229)
	at net.minecraft.client.particle.ParticleManager.updateEffectLayer(ParticleManager.java:213)
	at net.minecraft.client.particle.ParticleManager.updateEffects(ParticleManager.java:169)
	at net.minecraft.client.Minecraft.runTick(Minecraft.java:1934)
	at net.minecraft.client.Minecraft.runGameLoop(Minecraft.java:1119)
	at net.minecraft.client.Minecraft.run(Minecraft.java:407)
	at net.minecraft.client.main.Main.main(Main.java:118)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
	at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at net.minecraftforge.gradle.GradleStartCommon.launch(GradleStartCommon.java:97)
	at GradleStart.main(GradleStart.java:26)

 

Thanks!

Edited by MSpace-Dev
Solved the problem
Posted

Oh, Hmm, I saw another thread where a guy extended one of the particle classes. Anways, it seems to be working perfectly now. Haha, was so close =p

 

One more question, how do I select what UV the particle uses as the texture? I have a 128x128 image, like MC does, and I want to select the top most 8x8 pixels as this particle's texture. Couldn't find a 'setUV()' type method in Particle.

 

Posted
1 hour ago, Differentiation said:

The solution is simply not to extend ParticleCloud and remove the overrided method.

Really?  The ParticleMagic class shown above was nothing but overriding that method; take that out, and it has no data and no methods.  How does that make a custom particle?  (Unless there was more code to it that wasn't considered relevant in the original post.)

 

Instead of repeating what to not do, it'd be great if somebody could show or say what one should do.

 

@MSpace-Dev, can you share your working solution?

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.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Back then there was a number which determined the tier of an item and block. If the block tier is lower or equal to the item number, the block would be mined. this however, has changed and now it goes by "needs_netherite_tool" which is fine, until you realized that some mods had items and blocks that exceeded these values. You can make you own "needs_mod_tool" but I feel that this is more limiting(and just more work) than before. So is there anyway to use something similar to the old tier system while also still being compatible with a lot of other mod tools?
    • Well, when I log in to the server, sometimes within an hour, sometimes within a minute, the server closes and informs me that there was a Ticking entity error. Below is the crash report
    • Try switching to Windowed or Borderless Window mode in Minecraft. These modes make it easier for the recorder to capture gameplay, as it still has access to the display without the game taking up all of the graphics resources.
    • This forum is for Forge, not NeoForge. Please go to them for support.
    • Forge version: 55.0.0 Minecraft version: 1.21.5 Downloads: As this is the start of a new version, it is recommended that you check the downloads page and use the latest version to receive any bug fixes. Downloads page Intro: Good evening! Today, we have released our initial build of Forge 55.0 for Minecraft 1.21.5. 1.21.5 is the newest member of the 1.21 family of versions, which was released yesterday on March 25, 2025. As a reminder, the first minor (X.0) of a Forge version is a beta. Forge betas are marked as such on the bottom left of the title screen and are candidates for any breaking changes. Additionally, there are a couple of important things to note about this update, which I've made sure to mention in this post as well. Feel free to chat with us about bugs or these implementation changes on GitHub and in our Discord server. As always, we will continue to keep all versions of 1.21 and 1.20 in active support as covered by our tiered support policy. Cheers, happy modding, and good luck porting! Rendering Refactor For those who tuned in to Minecraft Live on March 22, 2025, you may already know that Mojang have announced their intention to bring their new Vibrant Visuals overhaul to Java in the future. They've taken the first steps toward this by refactoring how rendering pipelines and render types are handled internally. This has, in turn, made many of Forge's rendering APIs that have existed for years obsolete, as they (for the most part) can be done directly in vanilla. If there was a rendering API that was provided by Forge which you believe should be re-implemented, we're happy to discuss on GitHub through an issue or a pull request. Deprecation of weapon-like ToolActions In 1.21.5, Minecraft added new data components for defining the characteristics of weapons in data. This includes attack speed, block tags which define efficient blocks, and more. As such, we will begin marking our ToolActions solution for this as deprecated. ToolActions were originally added to address the problem of creating modded tools that needed to perform the same actions as vanilla tools. There are still a few tool actions that will continue to be used, such as the shears tool action for example. There are some existing Forge tool actions that are currently obsolete and have no effect given the way the new data components are implemented. We will continue to work on these deprecations and invite you to chat with us on GitHub or Discord if you have any questions.
  • Topics

×
×
  • Create New...

Important Information

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