Death API [Unmaintained]

Hatemail updated Death Handler with a new update entry:

last bug fix wasn't even a fix...uploaded old file.

 

Hatemail updated Death Handler with a new update entry:

3rd times a charm?

[DOUBLEPOST=1390577185][/DOUBLEPOST]

My fault or the servers fault dunno, just downloaded the new lua file and everything is now correct. I'm sorry to everyone who has experience problems with update v1.4

 

Seems it made the config file now, so guess it will work Cheers!

 

Enjoy it, Also If you can't get /death config value to work its caused by oxmin loading second. You will just need to type "oxide.reload DeathHandler" in console. I will add a timer to fix this later.

 

Good to know, Cheers.

 

I've heard about these possible loading order errors before and I'm sure you'll be able to code a workaround, but isn't this something which should be addressed on a larger scale (e.g. that plugins load correctly regardless of filenames and/or load orders)?

 

I think I'm going to just watch this for awhile and try it once confirmed stable.

 

These were the problems that were introduced after testing last night and they have all been fixed.
Failed to load plugin 'C:\TCAFiles\Users\User1\952\save\oxide\plugins\DeathHandler.lua'! ([string "C:\TCAFiles\Users\User1\952\save\oxide\plugins..."]:301: ')' expected near '=')

Was because I added the config for bodyParts and missed an Equals sign and did no testing as it was just one line..

malformed number near '1.4.1'
Was because I updated the version number quickly.

So if you think 2 errors means its unstable go and download the alternative.

 

My server world data was wiped 3 seperate times since last night only updating this single plugin, each time. No other changes. Fortunately I save/backup a lot so the players didn't revolt on me.

If you think my choice to be patient and wait is being offensive I appologize. However after having to restore 3 times... I figure I better wait until you confirmed it was working.

Appreciate the effort.

 

I've seen someone mention here that restarting your server before it's completely loaded might cause the data to get wiped. I see no reason why this particular plugin would cause your server to get wiped.

 

Ive installed enough seperate Oxide plugins that never interfered with any world data. Each one of these attempts in particular basically caused the most current "live" save to go to 0 bytes.

No idea why but it happened on each try of the updated plugin code.

Im going to try again tonight.

 

Hi i'm not sure if this is the right place to say. But since there has been an update i cannot log into my rust server. This is what it says. "Rejecting client (invalid protocol (1065)". if its due to not updating yet, how do it do it? plz help as im new to this stuff . loving the mod though!

 

it is due to not updating your rust server which GSP do you have as it effects how you update your server

 

i go through streamline.

 

Hatemail updated Death Handler with a new update entry:

Updating config version

 

Sorry, but what do i do now? gnsc4 said i have to update something... for some reason i can now load into the server, but nothing works... not even /help, no mods load what so ever...

 

Me and few other people use a testing server that gets restarted atleast once every 10 minutes. We have yet to have a server wipe happen, I would say it is because you are not properly stopping your server before restarting or another plugin is causing issues.

 

I don't actually know how to do it with this one maybe someone else can help you

 

Hey man if you updated your server you will need to re-install oxide if you have a mod manager that allows you to install it please do so.
If you are still getting errors go to your file manager and send me your oxidelog file

 

If it is online then your provided updated it for you

but all plugins are broken until the new Oxide is released