You'd be better off posting it in the Death Handler discussion that way the author could assist you.
Death API [Unmaintained]
Discussion in 'Plugin Support' started by Hatemail, Jan 20, 2014.
-
Ok, thank you ^^
But the problem has been solved, it had a conflict with the Bounty plugin, so we have deleted it
Have a good day.
-
Looking forward to the next update, good luck finding the time -
Code:
8:15 PM: ERROR: oxidecore: [string "DeathHandler.lua"]:242: attempt to index local 'damage' (a boolean value) (@) 8: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
-
Ozi said: ↑Code:
8:15 PM: ERROR: oxidecore: [string "DeathHandler.lua"]:242: attempt to index local 'damage' (a boolean value) (@) 8: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
Click to expand...
My off-the-cuff guess would be that another plugin is incorrectly modifying the damage value by returning a boolean instead of damage - which DH doesn't expect. Either that or Hatemail flubbed something, but either way I'm sure it'd be a lot easier to fix if you give adequate information. -
Does Hatemail come back online once in a while?
cause i would like to suggest my update for his plugin
to add: /deathmsg (to remove death messages for players who wants)
and an anti aimbot script made from it (that checks max range distances of every kill and if one of them is out of range of the weapon => Ban)
i use that on my server and works like a charm, reduces by 90% numbers of hackers on my serv ...
(Between Rick Anti Cheat and this, i have 150 bans in my ban list, in 2 weeks, and with maybe 100bans made by the scripts ^^, all verified hackers (or at least when an admin was on to see the bans be made)) -
I'm on every single day just don't reply to everyone
-
ah ok, well if you didnt reply it means you were not interested ?
-
Gliktch said: ↑You really need to give some context, mate.. When does this error happen, can you make it happen (reproducible), what other mods are you running, are you using the latest version of DH, who is your host, etc?
My off-the-cuff guess would be that another plugin is incorrectly modifying the damage value by returning a boolean instead of damage - which DH doesn't expect. Either that or Hatemail flubbed something, but either way I'm sure it'd be a lot easier to fix if you give adequate information.Click to expand...
Mods are listed.
Yes, im using latest Version.
my host is deinserverhost.deAttached Files:
-
-
Might be nice to add an automatic msg send to admins and logs when a player exceeds the range of a weapon and/or when they kill multiple players in rapid succession. Could even tie into the warnings and strike mod, etc...
-
Oh_G said: ↑Might be nice to add an automatic msg send to admins and logs when a player exceeds the range of a weapon and/or when they kill multiple players in rapid succession. Could even tie into the warnings and strike mod, etc...Click to expand...
-
Reneb said: ↑as i said i made it so if > range => warn admins and if > range+20 meters => autobanClick to expand...
-
no because players that bleed to death die from "Unknown"
-
Reneb said: ↑no because players that bleed to death die from "Unknown"Click to expand...
-
Bow doesn't have range ^^
-
Reneb said: ↑Bow doesn't have range ^^Click to expand...
-
yes but it doesn't mater in this case, Unknown kills are just ignored
-
Oxide 1.17, plugin not work! Only animal kills. Not players
-
xBUTCHERx said: ↑Oxide 1.17, plugin not work! Only animal kills. Not playersClick to expand...
-
Gliktch said: ↑False. There are easily five hundred servers using this plugin right now, on 1.17, without the problems you describe. Check your config, and if you can't find the problem, delete it (delete the config file) and let the mod re-create it. Are you also using FixYourName? Stupid characters in player names can mess with a lot of mods, not to mention making several exploits possible or easier, so if you're not blocking odd names you should rule that out first, before reporting any mod 'issues'.Click to expand...
Code:function PLUGIN:LoadDefaultConfig() self.Config.configVersion = "1.6" self.Config.logToConsole = true self.Config.logToAdmin = true self.Config.logToAdminChat = true self.Config.logToAdminConsole = true self.Config.logToFile = true self.Config.broadCastChat = true self.Config.deathByEntity = true self.Config.player = true self.Config.bear = false self.Config.wolf = false self.Config.stag = false self.Config.chicken = false self.Config.rabbit = false self.Config.boar = false self.Config.suicide = true self.Config.notifyKiller = true
About killing other players does not show anything in the log file writes.