Death Messages [Abandoned]

yes only way is to restart the server.

 

Love the plugIn! Great work.

I do see some errors in my logs from time to time, any ideas:

Code:

1:07 AM [Error] r-deathmessages: A .NET exception occured in user-code
  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

 

doesn't matter, everything seems to work anyway.
will fix that later on, but atm it doesn't bug the plugin

 

Code:

[Oxide] 10:16 PM [Error] r-deathmessages: [string "r-deathmessages.lua"]:195: In
put string was not in a correct format.
  at System.String.ParseFormatSpecifier (System.String str, System.Int32& ptr, S
ystem.Int32& n, System.Int32& width, System.Boolean& left_align, System.String&
format) [0x00000] in <filename unknown>:0
  at System.String.FormatHelper (System.Text.StringBuilder result, IFormatProvid
er provider, System.String format, System.Object[] args) [0x00000] in <filename
unknown>:0
  at System.String.Format (IFormatProvider provider, System.String format, Syste
m.Object[] args) [0x00000] in <filename unknown>:0
  at System.String.Format (System.String format, System.Object[] args) [0x00000]
in <filename unknown>:0
  at Oxide.Core.Logging.Logger.CreateLogMessage (LogType type, System.String for
mat, System.Object[] args) [0x00000] in <filename unknown>:0
  at Oxide.Core.Logging.Logger.Write (LogType type, System.String format, System
.Object[] args) [0x00000] in <filename unknown>:0
  at Oxide.Core.Logging.CompoundLogger.Write (LogType type, System.String format
, System.Object[] args) [0x00000] in <filename unknown>:0
  at Oxide.Lua.Libraries.LuaGlobal.Print (System.Object obj) [0x00000] in <filen
ame unknown>:0
  at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (ob
ject,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invoke
Attr, System.Reflection.Binder binder, System.Object[] parameters, System.Global

maybe it will help you

 

you just need to deactivate mysql.

 

I way to run stats.zip
DB connection is established and i'm petty sure everything is configured in the right way but there are no entries in the DB.

I use a dedicated root Server (Windows 2008), so there should be no restriction regarding "web request".
Any othre idea?

-------------------------------------
Solved it!
My API Key had some special characters. Now i used just normal letters and i seems to be fine!

 

self.Config.Settings.mysql = false

this will be properly ? TY!

 

you need to edit it inside the configs, not inside the plugin itself.

 

Ok! Many thanks for your help

 

[Oxide] 10:48 PM [Error] r-deathmessages: [string "r-deathmessages.lua"]:200: Input string was not in a correct format.
[DOUBLEPOST=1420688889][/DOUBLEPOST]Oxide] 10:48 PM [Error] r-deathmessages: [string "r-deathmessages.lua"]:200: Input string was not in a correct format.
at System.String.ParseFormatSpecifier (System.String str, System.Int32& ptr, System.Int32& n, System.Int32& width, System.Boolean& left_align, System.String& format)

 

Code:

[Oxide] 7:07 PM [Error] r-deathmessages: [string "r-deathmessages.lua"]:195: Input string was not in a correct format.
  at System.String.ParseFormatSpecifier (System.String str, System.Int32& ptr, System.Int32& n, System.Int32& width, System.Boolean& left_align, System.String& format) [0x00000] in <filename unknown>:0
  at System.String.FormatHelper (System.Text.StringBuilder result, IFormatProvider provider, System.String format, System.Object[] args) [0x00000] in <filename unknown>:0
  at System.String.Format (IFormatProvider provider, System.String format, System.Object[] args) [0x00000] in <filename unknown>:0
  at System.String.Format (System.String format, System.Object[] args) [0x00000] in <filename unknown>:0
  at Oxide.Core.Logging.Logger.CreateLogMessage (LogType type, System.String format, System.Object[] args) [0x00000] in <filename unknown>:0
  at Oxide.Core.Logging.Logger.Write (LogType type, System.String format, System.Object[] args) [0x00000] in <filename unknown>:0
  at Oxide.Core.Logging.CompoundLogger.Write (LogType type, System.String format, System.Object[] args) [0x00000] in <filename unknown>:0
  at Oxide.Lua.Libraries.LuaGlobal.Print (System.Object obj) [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

 

i'm stopping to answer to those error messages ...

 

Might be a { in the debug print of a nice playername that causes it to throw the error though as it's throwing it on "print(customMessage)" in BuildDeathMessage(), perhaps just run a gsub for { on it and replace it with 2 of them as you can't do print("{}") but you can do print("{{}}")

 

i think it's just that they keep mysql = true, when there is no keys nor links or stuff like that.
so it just tries to send a webrequest with wrong formats like:
"?key=&type=pvp"
etc

 

It's the print

Code:

at Oxide.Lua.Libraries.LuaGlobal.Print (System.Object obj) [0x00000] in <filename unknown>:0 

 

My MySQL setting is set to false. The error started, that I posted, after the update yesterday. Not sure why there won't be any replies to errors? Not supported anymore?

 

Reneb updated Death Messages with a new update entry:

fix for new version

 

PLEASE FIX "self.Config.naturalcausesdeathmessages"!
I have it off, but it still shows. I already wrote about it, but never fixed ...

 

@Mughisi is correct it is the print causing the error, so I went and fixed it.
https://github.com/OxideMod/Oxide/pull/32

 

Haha I'm an idiot xD I had altered my print() a few weeks ago and I forgot to push the changes :x
Thanks for putting the fix out there @Hatemail