When someone dies ingame it doesnt say what part of the body and yes I have that set to true.
It just says for everything, So killed so with a body shot!
Anyway to fix this =p
Death API [Unmaintained]
Discussion in 'Plugin Support' started by Hatemail, Jan 20, 2014.
-
I just loaded this addon but the messages aren't working. When I do /death in game, it says No Config Found. This is the first time i've ever loaded this addon. My server is hosted through Multiplay.
-
its /death configOptions value
All the config options are found on the overview screen.[DOUBLEPOST=1393548501][/DOUBLEPOST]
Also you need to be clearer, what you meant was c4,nades,spike walls, and bows don't show correctlyLast edited by a moderator: Feb 28, 2014 -
Works great no errors for me
-
How to disable broadcast chat for players, but at the same time leave for admins?
-
Anyone know how to get ⊕ to work in the config file? I tried copy and past, and it shows up with a ?.
-
you would of seen the command..
/death deathMessage ⊕ -
I read the overview page, I haven't tried the /command, but I assumed it would be the same as pasting that symbol into the Death Message field in the config file. I will try it out, thanks.
*edit* Guess it isn't the same as the config, copy/paste worked. Thanks! -
-
-
Can the plugin be wrong about the distance? Someone just killed a guy on my server with a mp5a4 , 308m.
Last time i seen that, the guy was vac ban two days after i banned him from the server.. -
Is it only me or is there a bug with the logging to a file?
The logging itself works fine but the times and dates are wrong. For example in the file 'Death Handler (03-1-2014).txt' are events up until 03-2-2014 1:52:11 while in the file of the next day the logging starts with 03-2-2014 2:03:24.
Thats the case with every file. It always logs some hours of the next day and then starts the next file so in the files are events from more than the actual day.
There's also a bug with the time display. 12:00 and 24:00 are switched so at 12:00 it says 24:00 and at 24:00 it says 12:00. -
-
Possible that Death Handler doesn't like ShowDamage?
Code:[Oxide] oxidecore: cs.callplugins failed with no traceback: NLua.Exceptions.LuaScriptException: A .NET exception occured in user-code: -2037664768 [Oxide] oxidecore: A .NET exception occured in user-code (@) [Oxide] oxidecore: nil [Oxide] oxidecore: [string "DeathHandler.lua"]:161: attempt to index local 'damage' (a boolean value) (@) [Oxide] 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
-
-
Any plugin that uses the modify damage will cause my plugin to break sometimes. This is because of a bug in nlua/unity mono 2.0, because the datatypes are being cached.
-
Hatemail updated Death Handler with a new update entry:
Code rewrite
-
Hatemail updated Death Handler with a new update entry:
File uploded failed re upload
-
Wulf Community Admin
-
updated to latest version, command for scope symbol for kill message no longer works. Says no config file found.