Jump to content

Recommended Posts

Posted

Alright, thanks! Would this work?

 

@ForgeSubscribe

public void onEntityDeath(LivingDeathEvent event) {

if(event.entityLiving instanceof EntityZombie) {

 

    System.out.println("Hello!");

   

}

   

    }

Posted

I did this, and it does not seem to work. I registered it to the event bus, so it should be working. Here is my class:

 

package mymod.quests;

 

import net.minecraft.entity.player.EntityPlayer;

import net.minecraftforge.event.ForgeSubscribe;

import net.minecraftforge.event.entity.living.LivingDeathEvent;

 

public class Test {

 

@ForgeSubscribe

public void onEntityDeath(LivingDeathEvent event) {

if(event.entityLiving instanceof EntityPlayer) {

 

    System.out.println("Hello!");

   

}

   

    }

 

}

Posted

What? In my main mod class, this is where I have it:

 

public static void init1( FMLInitializationEvent event )

{

MinecraftForge.EVENT_BUS.register(new SoundHandler());

MinecraftForge.EVENT_BUS.register(new Test());

}

Posted

Now that I look at your code you are checking to see if the entity that died is an instance of EntityPlayer not entity Zombie. Sorry I read that post wrong. ANd to check if it was the player that killed it, use the damagesource object.

VANILLA MINECRAFT CLASSES ARE THE BEST RESOURCES WHEN MODDING

I will be posting 1.15.2 modding tutorials on this channel. If you want to be notified of it do the normal YouTube stuff like subscribing, ect.

Forge and vanilla BlockState generator.

Posted

Why are you still using 1.6.4? And Instead of MinecraftForge.EVENT_BUS.register(new EventHandlerClass) use FMLCommonHandler.instance().bus().register(new EventHandlerClass);

VANILLA MINECRAFT CLASSES ARE THE BEST RESOURCES WHEN MODDING

I will be posting 1.15.2 modding tutorials on this channel. If you want to be notified of it do the normal YouTube stuff like subscribing, ect.

Forge and vanilla BlockState generator.

Posted

The first version you posted should be printing to the console each time a zombie dies. To test if your event handler is working at all, you can put a println at the very beginning of it:

@ForgeSubscribe
public void onEntityDeath(LivingDeathEvent event) {
  System.out.println("Entity died: " + event.entity);
}

If you're not getting any output at all, make sure you actually call that random static init1 method you posted... it'd be simpler just to register directly during one of the FML events.

 

Edit: No, don't use FMLCommonHandler event bus - that's the wrong bus for this event. Here's a tutorial  - please read it so we don't have to repeat the same information over and over again.

Posted

Oh thank you Cool Alias I completely forgot what goes where when dealing with Events thanks for the refresher, now if you'll excuse me I've got some reading to refresh on.

VANILLA MINECRAFT CLASSES ARE THE BEST RESOURCES WHEN MODDING

I will be posting 1.15.2 modding tutorials on this channel. If you want to be notified of it do the normal YouTube stuff like subscribing, ect.

Forge and vanilla BlockState generator.

Posted

No worries - that's the reason they finally consolidated the event buses, it was a mess keeping track of them.

 

@OP As we've said, you have to check if the DamageSource#getEntity is an EntityPlayer, then cast that entity to EntityPlayer so you can call I believe #addChatMessage to send them a chat - it's been a long time since I've looked at 1.6.4 and the chat methods have changed a lot since then, so you may have to look for it yourself.

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

    • When I first heard about Bitcoin back in 2018, I was skeptical. The idea of a decentralized, digital currency seemed too good to be true. But I was intrigued as I learned more about the technology behind it and its potential. I started small, investing just a few hundred dollars, dipping my toes into the cryptocurrency waters. At first, it was exhilarating to watch the value of my investment grow exponentially. I felt like I was part of the future, an early adopter of this revolutionary new asset. But that euphoria was short-lived. One day, I logged into my digital wallet only to find it empty - my Bitcoin had vanished without a trace. It turned out that the online exchange I had trusted had been hacked, and my funds were stolen. I was devastated, both financially and emotionally. All the potential I had seen in Bitcoin was tainted by the harsh reality that with decentralization came a lack of regulation and oversight. My hard-earned money was gone, lost to the ether of the digital world. This experience taught me a painful lesson about the price of trust in the uncharted territory of cryptocurrency. While the technology holds incredible promise, the risks can be catastrophic if you don't approach it with extreme caution. My Bitcoin investment gamble had failed, and I was left to pick up the pieces, wiser but poorer for having placed my faith in the wrong hands. My sincere appreciation goes to MUYERN TRUST HACKER. You are my hero in recovering my lost funds. Send a direct m a i l ( muyerntrusted ( @ ) mail-me ( . )c o m ) or message on whats app : + 1 ( 4-4-0 ) ( 3 -3 -5 ) ( 0-2-0-5 )
    • You could try posting a log (if there is no log at all, it may be the launcher you are using, the FAQ may have info on how to enable the log) as described in the FAQ, however this will probably need to be reported to/remedied by the mod author.
    • So me and a couple of friends are playing with a shitpost mod pack and one of the mods in the pack is corail tombstone and for some reason there is a problem with it, where on death to fire the player will get kicked out of the server and the tombstone will not spawn basically deleting an entire inventory, it doesn't matter what type of fire it is, whether it's from vanilla fire/lava, or from modded fire like ice&fire/lycanites and it's common enough to where everyone on the server has experienced at least once or twice and it doesn't give any crash log. a solution to this would be much appreciated thank you!
    • It is 1.12.2 - I have no idea if there is a 1.12 pack
  • Topics

×
×
  • Create New...

Important Information

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