Death API [Unmaintained]

Hi, Error time !

Code:

10:15 PM: ERROR: oxidecore: cs.callplugins failed with no traceback: NLua.Exceptions.LuaScriptException: A .NET exception occured in user-code: -1806565376
10:15 PM: ERROR: oxidecore: A .NET exception occured in user-code (@)
10:15 PM: ERROR: oxidecore: nil
10:15 PM: ERROR: oxidecore: [string "DeathHandler.lua"]:265: attempt to index field 'networkView' (a nil value) (@)
10:15 PM: ERROR: oxidecore:   at NLua.Lua.ThrowExceptionFromError (Int32 oldTop) [0x00000] in <filename unknown>:0
  at NLua.Lua.CallFunction (System.Object function, System.Object[] args, System.Type[] returnTypes) [0x00000] in <filename unknown>:0
  at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0

 

Hatemail updated Death Handler with a new update entry:

Bug fix's

 

I really enjoyed having this and other mods on my server. The weekly Oxide updates killed it for me. Every week I find myself fixing more issues with .lua script errors than playing the game. Unfortunately a lot of servers are going Vanilla due to all the hassle. I think it's great what you guy's are doing, but the dev's seem to be neglecting the real issues on this game and "fixing" things that don't matter. They were off to a great start until they started doing things because they couldn't take all the negative comments. Now I see you guys going crazy putting more development into this game than the dev's. Their actions are having an adverse effect on your awesome mods. You guy's should do what the DayZ dev's did and break off the modding and make a standalone of this alpha, lol. I bet you'd have it finished before they do.

 

Thx for the update.
Do we need to let the plugin recreate cfg files?

 

Hello ,

I have a little problem : when a bear kill a player , it show on the Chat , but no death message by players anymore

Don't know where is the problem.

 

make sure the player config options is set to true. If you think it's a problem with this update you can still dl the old version, under the Verison tab

 

I don't shoot unless I'm going to hit (I've played too much Dayz), would that make me an aimbotter?

 

No I don't think so but it would make it easier to analyze potential hackers.

 

Thx for the update

 

Just wondering is this a hacker notification or just a bug. "Zensored killed Zensored (Unknown) with a hit to their chest at 418m"

 

2 players with the same names may be.

 

xD I just removed their names im talking about unknown weapon and 418m

 

It's a bug, Unknown is the Hunting Bow, 418 meters is the distance is the distance at which the player was killed. (418m oO )

 

Could be Hunting Bow / C4 / F1 Grenade.
Also if the target bleeds from any of the above and then travels away from the bleed location it will still count the original spot the person began bleeding.

For example I did a test with a friend, I'll go pull it out the logs...

12:13 AM Inka Kaoru killed Krimian (Unknown) with a hit to their chest from 11,365m away!

I stood next to him, he shot me in the chest with bow and I took damage and bled, In this case I teleported to north end of the map and bled to death and that's the message.

So in theory any long range shots could be due to the fact that the person got shot and ran away whilst bleeding.

 

Ah good to know. So basically any bleeding death is source unknown. Well but since the guy was in TS an said he pretty much died instantly this seems fishy to me. Gotta keep an Eye on them.

 

Oh some will still appear to be 'fishy', but no, bleeding damage is not unknown, The unknown only comes from Bows / C4 and Grenades.

 

Well but that would be impossible you cant kill someone with 1 shot with a bow at that distance
Also C4/Grenades cant be thrown that far. And since he was in TS i know he died nearly instantly.

 

What about death from spikes? Any way to add this to the plugin?

 

Are there any plans to add the possibility to show sleeper kills? Maybe with an option to hide it as a ingame message but still log it into the logfile.

 

Just to let everyone know a little about what will be coming soon.
1) The plugin will be two separate files after the next update. One will be the api abstraction and one will be the handling of the messages. It will provide the exact same functionality but it will allow many other plugin devs to work with the framework I have made.
2) Every death from a weapon will be tracked properly. So Bows, C4, Nades, and spike walls will all be tracked correctly. I know a lot of people have been waiting for that.
3) Distance will be added for animal kills
4) Less lag
5) dunno you tell me.