Sounds like someone should write a simple script so people can select what they want in their kits and and then it generates the json file for you![]()
Rust-Kits
Moved
Total Downloads: 70,144 - First Release: Oct 21, 2014 - Last Update: Jun 7, 2018
- 4.96216/5, 185 likes
-
Still getting this error non-stop...
[Oxide] 9:00 PM [Error] kits: [string "kits.lua"]:217: attempt to index field 'AutoKits' (a nil value)
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] 9:00 PM [Error] kits: [string "kits.lua"]:217: attempt to index field 'AutoKits' (a nil value)
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 -
I'm getting tired of this error ... Just reset your kits and remake them ... This error pops up if you fucked with the config ...
-
Isn't that what everyone does? Nobody will use that default kit. Am I missing something here?
-
you just have to leave AutoKits {}
with nothing inside, not totally change it ... i guess i'll change that cause everybody fucks with it --' -
I did that and the error still occurs.
[DOUBLEPOST=1422558334][/DOUBLEPOST]{
"Kits": {
"starter": {
"main": [
{
"amount": 1,
"name": "x"
},
{
"amount": 1,
"name": "x"
},
{
"amount": 1,
"name": "x"
},
{
"amount": 1,
"name": "x"
},
{
"amount": 1,
"name": "x"
},
{
"amount": 1,
"name": "x"
},
{
"amount": 1,
"name": "x"
},
{
"amount": 1,
"name": "x"
},
{
"amount": 1,
"name": "x"
},
{
"amount": 1,
"name": "x"
},
{
"amount": 1,
"name": "x"
},
{
"amount": 1,
"name": "lx"
},
{
"amount": 1,
"name": "x"
},
{
"amount": 1,
"name": "x"
}
],
"description": ""
},
"Messages": {
"NoPermissionKit": "You don't have enough permissions to use this kit",
"CoolDown": "This kit is still in cooldown",
"KitList": "Avaible Kits",
"HelpMessage": "/kit - to get the list of kits",
"NoKitAvaible": "You have no avaible kits",
"ErrorKit": "This kit doesn't exist",
"NoKitLeft": "You don't have any kits left for this kit"
},
"AuthLevel": 1,
"AutoKits":{}
} -
you probably need to restart the server for it to stop happening
keep me posted. -
That doesn't help. I've done everything.
-
"AutoKits":{"allowed":false}
[DOUBLEPOST=1422576435][/DOUBLEPOST]i'm actually not going to edit the plugin as this is an option that people shouldn't remove and if you do it's your fault --' i can't do checks everywhere in the plugin to be sure that people don't remove part of the config :x
[DOUBLEPOST=1422576681][/DOUBLEPOST]I know that json are no that easy to configure.
But go train yourself on the legacy plugin: loot spawns ^^ took me couple hours to figure it the First time i used it ^^ -
Auto kits dosen't work after last rust update!
-
Thx for noticing i'll look into it
-
Same, no autokits, fix please
-
Reneb updated Kits with a new update entry:
fix for new version
-
Thanks! But... How can I restart (after updating files) this plugin without server switching off? -
just update the file in server/identity/oxide/plugins/
and the server will auto update the plugin. -
Hmm I am still running the previous one and it is working fine enough. What did it change? I am scared to change and get all messed up again haha
-
autokits dont work with the old version.
if you don't use it you dont need it -
Ah I see
(got them disabled due abuse). Thanks Reneb
-
Kit starter and other kits like daily, doesn't work... Oxide give me an error: Unknown Command: "kit"
-
If it doesnt work it's not related to my plugin then.