DeathNotes

Yeah. That has nothing to do with this plugin. Your oxide is outdated.

 

Install Oxide version 2.0.1330 or newer.

 

I just upgraded, I still see the same error .. I must also update the plugin config?

https://i.gyazo.com/4de49b1c08e61d4a16b98cf7d68884ad.png

 

Still has nothing to do with this plugin. If you got problems with it, post it into Experimental Discussion section, not here. That error has nothing to do with this plugin.

 

Sorry, I have mistaken the gyazo .. but I still spending the same error, I must also update the config?

https://i.gyazo.com/a4a6f1b380308fe23dd40da4f9b4308b.png

 

Mate. THAT is an error in Oxide NOT this plugin. You have to update your OXIDE not this plugin. This plugin has NOTHING to do with that error.

 

@LaserHydra
I've got:

Code:

[Oxide] 11:31 PM [Error] Failed to call hook 'OnEntityDeath' on plugin 'DeathNotes v3.1.23' (NullReferenceException: Object reference not set to an instance of an object)
[Oxide] 11:31 PM [Debug]   at Oxide.Plugins.DeathNotes.OnEntityDeath (.BaseCombatEntity vic, .HitInfo hitInfo) [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 

several times a day. it does not interfere, but the error is still there somewhere
[DOUBLEPOST=1440794248][/DOUBLEPOST]In errorLog only one error :

Code:

[8/28/2015 5:52:15 PM] Failed at getting victim: Object reference not set to an instance of an object

 

ok. Do you know when that error appears? Are you able to reproduce it?

 

I can't I will ask players to assist

 

snaptrap and landmine deaths show up as "A. Killed" and even with show animal kills set to true they dont show

 

Okey dokey..

 

getting this error
[Oxide] 6:29 PM [Debug] at Oxide.Plugins.DeathNotes.OnEntityDeath (.BaseCombatEntity vic, .HitInfo hitInfo) [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

 

these are things that worked before you took over the plugin. do you plan on fixing this?

 

Sure I am.
[DOUBLEPOST=1440813933][/DOUBLEPOST]

The update with these name changes should be the reason for that.

 

@LaserHydra I took a look at you at your most common errors here, and I see you're struggling to fix one of the most weird errors I had before. So I thought to come here and give some advice I guess.

Code:

NullReferenceException: Object reference not set to an instance of an object

This error have always been there since ever, and to be honest even today I don't have a fucking clue of what it could be, until the day I thought "I may not be able to fix it, but I'm able to hide it", it's lame I know, but just like you I got tired of people spamming out the same freaking error all the time, and no matter how much "fixes" I'd try, the fucker would still come up anyway.
So I thought I'd tell you what I did to hide this error and it's basically to use exceptions whenever this error comes up, I figured that somehow this error would come up while gathering the information of the death in hand, the victim, the attacker, distance, etc, even before of knowing the death type message.
(The image below shows the part of my code that does all this)

And so if you take a look at the image below, in line 308 there is the 'try' statement, which in case you don't know, Python will execute the code below the 'try' statement and in case any exception comes up while running that code then Python will execute the code below the 'except' statement (line 322 in the image), which in my code and in this case it returns nothing, stopping any code from being executed, so the plugin does nothing and no errors will be shown in the console ignoring whatever happen in that moment.
The truth is that this method reduced a LOT of the people reporting the error, it actually became so rare that I would simply ignore anyone reporting it. This method may not have solved the problem, but helped me "solve the problem", if you know what I mean.

I'm just trying to help you out on avoiding people spamming you with all these repetitive posts telling you the same old thing, all they want is you to fix the issue, they don't give a damn on how much work you have or do for this thing. (At least most of them don't, there are still cool people around sometimes, I don't wanna sound like a complete asshole)
Anyway, I hope this helps you anyway, I believe I left the DN in good hands so I still wanna help out anyway I can. So keep up the good work buddy.

 

Is there any hope that Deathnotes will be simple as old one (where anyone was able to create a lot of variants of messages for each type of deaths and they was in separate line each)?

 

I like the new version much better. Thanks.

Metal barricade deaths are coming up blank for the {attacker} however.

 

Yo SkinN. If you look at the current code, ive already done that. Just what I did more than hiding it, is saving it to a an other .txt file. But the latest error is a new one that just popped up. Also the debug message does not seem to give any info where it is.
- Laser
[DOUBLEPOST=1440836239][/DOUBLEPOST]

Yes. I gonna add some features I temporarely removed for simplicity when rewriting, once again step by step.
[DOUBLEPOST=1440836281][/DOUBLEPOST]

I appreciate it. Yes need to fix the name of that.

 

Just a question with this last version. It seems we don t get the message from a mine anymore ? when we blow up on it ?

 

LaserHydra updated Death Notes with a new update entry:

3.1.3