SetHome [Unmaintained]

@Stels-510, going to go wild here and just start making assumptions based on that error you are posting, in your plugins folder, is there a file named oxidecore.lua present? Because the only reference I can find to the field 'takenodamage' in Reneb's plugin, Oxmin and Oxidecore is in the core file.

Code:

local GetTakeNoDamage, SetTakeNoDamage = typesystem.GetField( Rust.TakeDamage, "takenodamage", bf.private_instance )

And another really wild assumption, are you using a cracked server or are you using an official GSP?

 

Is this oxide:http://rustoxide.ru/resources/oxide-server-mod.59/
Pirate Server, version 02.09.14 [1069] worth 25+ plugins, all work fine, and this creates such bugs even on the server without plugins, it's not the server, and the plugin or oxide ...

 

Reneb updated R-SetHome with a new update entry:

fix

 

Thank you very much for your effort, but the error persists:

ArgumentException: Field 'takenodamage' defined on type 'TakeDamage' is not a field on the target object which is of type 'DamageBeing'.
"SetDestination" can only be called on an active agent that has been placed on a NavMesh.
"Stop" can only be called on an active agent that has been placed on a NavMesh.
"SetDestination" can only be called on an active agent that has been placed on a NavMesh.
"Stop" can only be called on an active agent that has been placed on a NavMesh.

 

The NavMesh errors sometimes pop up and I do not know what exactly causes these and the only thing I've found out to get rid of those is to restart the server. And regarding that ArgumentException, maybe it's because you're running Oxide 1.17, I'm not sure. You could always try to install the official legacy Rust Dedicated Server with Oxide 1.18 that was made available earlier today.

 

Thanks, did not know that it made available, try Wait[DOUBLEPOST=1410210389][/DOUBLEPOST]Thank you so much for your help and your work done, with the oxide 1.18 everything works fine!

 

5:51 PM: ERROR: r-sethome: Lua error handling chat command 'home'!
5:51 PM: ERROR: r-sethome: [string "r-sethome.lua"]:264: attempt to compare nil with number
5:52 PM: ERROR: r-sethome: Lua error handling chat command 'home'!
5:52 PM: ERROR: r-sethome: [string "r-sethome.lua"]:264: attempt to compare nil with number

 

if it does this permanently then reload the cfg, you might have a corrupted cfg.
it it doesn't, then you don't care, probably a noob trying to do /sethome FLDGMFDLGM

 

Keep getting "Set Home Deactivated"

Works fine for admins not players,

 

yes i have NO ideas why it does that, jsut deactivate the reset_on_damage or whatever the name is

 

probable from the radiaton

 

my friends using door share but i still cant sethome on his base ??
but apart from this m8 excellent plugin

 

Have you set the "Use_Doorshare" value in the config to true and reloaded the plugin/restarted the server?

 

yes m8 i downloaded doorshare from your link in the description too[DOUBLEPOST=1411254101,1411207892][/DOUBLEPOST]everyone complaining on server will have to remove thanks anyway nice try

 

home help not avial?
/home help or /homehelp cor commands.
[Oxide] r-sethome: Lua error handling chat command 'home'!
[Oxide] r-sethome: [string "r-sethome.lua"]:280: attempt to compare nil with number

 

/help

 

Can you add a setting to block home use in an arena or area location ie.. x=3000-3100 and z=6000-6100?

 

when i put this addon on my server and restart the addon deletes its self?

 

tell it to multiplay, it's an issue on their side.

 

ok thank you my friend sorry for all the newb crap today lol