wo wooo woow :D happy to see activity <3 cheked the .cs and its says :[Info("Build", "Gonzi", "2.2.2")]
An object reference is required to access non-static member `FileSystemBackend.cache'Fixed
For anyone having the same trouble, here's what i've done.
2.2.2 was uploaded on my server.
Was still getting error Build.cs(341,52): error CS0176: Static member `FileSystemBackend.cache' cannot be accessed with an instance reference, qualify it with a type name instead
I've open up Build.cs, went to line 339 and changed FileSystemBackend.cache.Keys to FileSystemBackend.Backend.cache.Keys. Saved the file then Rcon -> oxide.reload Build -> Getting the same error. went back, & rechanged the same line to what it was originally FileSystemBackend.cache.Keys
Rcon-> oxide.reload Build -> Loaded fine, problem fixed
can also confirm
Loaded plugin Build v2.2.0 by Gonzi & Spiikesan
so i didnt had the compiling error before hand.
Best
Luuxen
Abdew
For anyone having the same trouble, here's what i've done.
2.2.2 was uploaded on my server.
Was still getting error Build.cs(341,52): error CS0176: Static member `FileSystemBackend.cache' cannot be accessed with an instance reference, qualify it with a type name instead
I've open up Build.cs, went to line 339 and changed FileSystemBackend.cache.Keys to FileSystemBackend.Backend.cache.Keys. Saved the file then Rcon -> oxide.reload Build -> Getting the same error. went back, & rechanged the same line to what it was originally FileSystemBackend.cache.KeysRcon-> oxide.reload Build -> Loaded fine, problem fixed
FileSystemBackend.Backend.cache.Keys doesn't exist, the correct one is FileSystem.Backend.cache.Keys. 2.2.1 had the wrong one, 2.2.2 fixed it. This thread is about the 2.2.0 version though before the updates.
Oxide.Rust Version: 2.0.5589
either 2.2.1 or 2.2.2 compile for me
v2.2.0 still compile without no problem
Luuxen
Oxide.Rust Version: 2.0.5589
either 2.2.1 or 2.2.2 compile for me
v2.2.0 still compile without no problem
If you are using 2.2.0, your server is outdated. There's no physically way for 2.2.0 to work on any Rust updates prior to today. 2.2.2 would also compile fine on any past Rust version as well as current.
A manual fix is mentioned previously if you are having trouble with the latest version.
Protocol: 2348.226.1
Build Date: 07/08/2022 09:07:13
Unity Version: 2019.4.7f1
Changeset: 72450
Branch: release
Oxide.Rust Version: 2.0.5589
Loaded plugin Build v2.2.0 by Gonzi & Spiikesan
Luuxen
Protocol: 2348.226.1
Build Date: 07/08/2022 09:07:13
Unity Version: 2019.4.7f1
Changeset: 72450
Branch: release
Oxide.Rust Version: 2.0.5589
Loaded plugin Build v2.2.0 by Gonzi & Spiikesan
The version that shows doesn't mean your server is updated correctly. The 2.2.0 version cannot physically load on that Oxide version if you installed all of the files, because access to the field that 2.2.0 uses is not accessible anymore. We can go back and forth all you want about it, it doesn't change the facts. If you can use 2.2.0, your server is not fully updated.
im not trying to go back and forth im just trying to figure out what the problem is sir.
the commands version / build is just complete useless then.
Sorry for the report <3
The command will show which Oxide verison you have installed, but that doesn't mean all files were replaced. Oxide is a mod, which modifies multiple game files. So like I said, if 2.2.0 still loads, you are still using an older file that was patched in today's Oxide update. If you don't want to do that, then don't use any version above 2.2.0 and you'll be fine for now. To resolve the issue after your server is fully updated, you'd need to update to 2.2.2 or manually apply the change mentioned previously.Luuxen
im not trying to go back and forth im just trying to figure out what the problem is sir.
the commands version / build is just complete useless then.
Sorry for the report <3
2.2.2 works for me with no problems perfect, thanks 👍
Locked automatically
- 1
- 2