SetHome [Unmaintained]
Discussion in 'Plugin Support' started by Reneb, Aug 6, 2014.
-
Code:
[Oxide] oxidecore: A .NET exception occured in user-code (@) [Oxide] oxidecore: nil [Oxide] oxidecore: [string "r-sethome.lua"]:107: attempt to index field 'attacker' (a number 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 [Oxide] SirSmokeAlot ran the command: /remove [Oxide] User "Nobyz" disconnected with SteamID 'STEAM_0:1:55443950' User Disconnected: Nobyz [Oxide] SirSmokeAlot removed a Wood Foundation [Oxide] oxidecore: cs.callplugins failed with no traceback: NLua.Exceptions.LuaScriptException: A .NET exception occured in user-code: 405795328 [Oxide] oxidecore: A .NET exception occured in user-code (@) [Oxide] oxidecore: nil [Oxide] oxidecore: [string "r-sethome.lua"]:107: attempt to index field 'attacker' (a number 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 [Oxide] (0.0, 0.0, 0.0): 0 [Oxide] gmC Sajex (NL) removed a Large Wood Storage
-
[Oxide] oxidecore: cs.callplugins failed with no traceback: NLua.Exceptions.LuaScriptException: A .NET exception occured in user-code: -1759700480
[Oxide] oxidecore: A .NET exception occured in user-code (@)
[Oxide] oxidecore: nil
[Oxide] oxidecore: [string "r-sethome.lua"]:108: attempt to index field 'attacker' (a number 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
Hey reneb, getting this error. not sure whats causing it, but its lagging down the server when it happens. -
This error text is continually spamming the servers RCON and lagging the server, I'm going to have to disable this till its fixed
-
can you guys tell me if with the new r-remover you still get those errors? plz
-
Will do.
Is it enough for me to download new update and CTRL+C code and replace my r-remover.lua with new code and then oxide.reload r-remover ? -
ofc
-
[Oxide] oxidecore: [string "r-sethome.lua"]:107: attempt to index field 'attacker' (a number 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 -
Reneb updated R-SetHome with a new update entry:
bug fix (normally) + optional reset timer on damaged
-
Triple TP should fix most glitches since it gives the time to load in buildings, you could always TP 5 times to make sure.
If someone is crouched in a rock they will either get disconnected or be in the rock.
Either way a sleeping bag works fine, and once you've set a foundation in a rock your whole group can set it as home and TP inside the rock whenever they want.
There is no foolproof solution to stopping abusers, this however stops people from setting home on someone else's foundation and stops them from glitching through a base.[DOUBLEPOST=1409504304][/DOUBLEPOST]BTW I was using your latest version of r-remover, I had to update for the refund to work too
Would be nice if we could toggle or the group leader could toggle group remove but thanks a lot for adding that support to r-remover -
hmm i guess i could do that yes
-
So I wanted to know if you have fixed the MASSIVE exploit where if you use /home, then log off it resets timer and spits out error in console. So people can use /home without a timer. Can you PLEASE IMMEDIATELY fix this bug?
-
haha yes normally it's fixed in this version.
you are the first one to report it to me, but i saw the flaw in my code and should have fixed it
but as i don't use this plugin on my server i can't always see how people exploit it -
I can't get the set home on allied foundation to work. I have both plugins installed, doorshare and Groups. After sharing doors or forming a group it still tells us that we can't sethome on an allied foundation. Any ideas?
UPDATE: Never mind, I figured it out. Rookie mistake. -
Any idea when it may be fixed?
-
Sethome is not working
when you try to hit the floor nothing happens with latest update -
Reneb updated R-SetHome with a new update entry:
fixed the sethome not working
-
-
Spams more than ever.
-
restart the server, it's the only thing that i did and it fixed the pb.