[1.7.10] Getting if a mob was killed by a player or not

[flamedragonX2]

So I'd like to make the chat have a death message whenever a (non-named) mob was killed by a player. This is easy for melee/ranged attack kills (I just used LivingDeathEvent), but how would I get if a mob was recently hit by a player before death (i.e. if it is thrown off a cliff or into lava)? For example, if I hit the mob and then it falls into lava, I want a death message spawned. However if it just walks into lava on its own there should be no message.

 

The value in the MC source code that keeps track of this so it can spawn XP orbs and stuff is protected so I can't get to it...

 

Is there a way to get a boolean that tells you this?

[Ernio]

Everything really depends on how much data on death you need.

 

You are quite outdated (WHY?!?!?) so I don't remember if MC had CombatTracker (good one) at that time, and even if - it might be poorer than it is now.

 

Anyway - are you referring to field that holds last attacker entity (which might be player)? If there is no getter then you have to either update or use java Reflection (google).

 

Is there a way to get a boolean that tells you this?

 

What boolean?

 

As to other ways - whenever data vanilla gives you is not sufficient you use IExtendedEntityProperties (now 1.8.9+ @Capability) to store more data. That data can be manipulated from anywhere really (so e.g you can track such actions yourself from e.g LivingHurtEvent). Currently some of such tracking is in mentioned CombatTracker, which idk if existed back then (cmon, it's been 2 years, update).

[flamedragonX2]

Everything really depends on how much data on death you need.

 

You are quite outdated (WHY?!?!?) so I don't remember if MC had CombatTracker (good one) at that time, and even if - it might be poorer than it is now.

 

Anyway - are you referring to field that holds last attacker entity (which might be player)? If there is no getter then you have to either update or use java Reflection (google).

 

Is there a way to get a boolean that tells you this?

 

What boolean?

 

As to other ways - whenever data vanilla gives you is not sufficient you use IExtendedEntityProperties (now 1.8.9+ @Capability) to store more data. That data can be manipulated from anywhere really (so e.g you can track such actions yourself from e.g LivingHurtEvent). Currently some of such tracking is in mentioned CombatTracker, which idk if existed back then (cmon, it's been 2 years, update).

 

I have to start at 1.7.10, mostly because that's the version significant numbers of the mods are. Maybe later I will update to 1.9 or so (may just skip 1.8.9 entirely).

[flamedragonX2]

Oh yeah, I found CombatTracker in 1.7.10 and got it to give me a death message, but the thing is I want to use my own custom (random from a selection in a config, the config part is done already) death messages, separate from the original ones.

[Ernio]

I have to start at 1.7.10, mostly because that's the version significant numbers of the mods are.

 

1. You don't HAVE TO.

2. If you are implying that 1.9+ (or even 1.8+ for that matter) has no mod base you are simply wrong. Most respectable mods are updated.

3. 1.7.10 is so old that you will get significantly less support here than for recent version.

4. You are making it difficult for yourself (1.7.10 is much more messed up than 1.8.9+).

5. You are missing on a LOT of new features/hooks (seriously, a lot), have fun making sneaky hacks.

 

Maybe later I will update to 1.9 or so (may just skip 1.8.9 entirely).

 

Currently writing anything for 1.7.10 can be called waste of time. Why?

1.7.10 and 1.9+ are so much different (threads, registry, blocks/items, rendering, models, tons of changes like two hands, class and mehtod names etc.) that updating in means of "fixing things" is close to not possible. You will basically have to relearn quite big chunk of API and vanilla systems and then rewrite mod from scratch. On top of that - anything you write regarding rendering will be 100% useless, because of new models/rendering.

 

"I won't update my mod because others haven't updated theirs yet" is alredy bad. "I will write new outdated mod because others haven't updated" is even worse. Seriously, don't be that guy. Waste of efforts and just bad approach.

 

Oh yeah, I found CombatTracker in 1.7.10 and got it to give me a death message, but the thing is I want to use my own custom (random from a selection in a config, the config part is done already) death messages, separate from the original ones.

 

I don't think there is anything (server-side) that would allow catching message to be sent. You can manipulate client received (pre-chat-printing), client to-be-sent and server received, but not server to-be-sent. Unless you would hook into packet pipeline (basically override network pipeline of vanilla).

 

EDIT

 

I'd look for a way to cancel sending death message (there is such thing, idk where tho, maybe even in event). And then send your own from death event (basing off CombatTracker).

[flamedragonX2]

Okay, I understand what you mean now. Gonna try it out...

 

A significant portion of the mods I play (which are still being updated) haven't yet updated to 1.8.9+, though some of them have said they will update soon. I do want them to update eventually but seeing as my entire playstyle revolves around mods like those I'm sticking with 1.7.10. TBH this mod is more of a personal thing for my own experience that I may not even plan to distribute.