Solved Can't spawn items from F1 item list

so do you have to load the DirectX 12 Experimental to use those features? or just the "Play Rust" option?

 

Interesting. I wonder why its still not spawning items in my server. I even went in and just reinstalled the whole thing. I used these in the server console.(ownerid 76561197736539 "Tim" "Owner")

(moderatorid 76561197736539 "Tim" "Owner")

(server.writecfg)

and when i join server, I hit F1, item list, stones "BP" and nothing.

 

I don't share any kind of account. I used my homepage url from steam and pasted it into steamid. It gave me all of my stats and my steam id. I copy pasted that into the "steamid" section. Should i just try the rusty route?

 

This is interesting. I just ran into this same problem.
Server has been up since fall of last year. Upon initial setup, I setup my ownerid and never had an issue.
The only thing that has changed has been this most recent wipe.
I attempted to spawn myself some wood via the F1 menu, as normal, and it basically said I lacked the required permission to use this.
Keep in mind, my name is green in the chat console. I thought, maybe the last wipe erased the users.cfg. So I attempted to setup my ownerid again, and it said I was already an owner.
Strangggggge!

EDIT: Saw another post of someone else having this problem. With Wulf's help, they realized it was a plugin. Thanks Wulf!

EDIT2: I just removed RemoveAAA and all is well, aside from it broadcasting what I got.

 

Was RemoveAAA the problem, then? I'm having the same issue on a new installation, and I'm trying to avoid removing all my plugins

 

You must not of added the permissions to your admin group this is why you could not get items from the f1 menu. Remember always read the overview of every plugin you install

 

I've gone back and uninstalled all plugins and deleted all their files, and am now reinstalling one by one and setting them up as I go. So far, it would appear that RemoveAAA was indeed the issue Thanks so much for the swift reply!

 

Actually, this all stemmed from the release of the rust version of Oxide that moved the oxide folder.
When I removed REMOVEAAA, yeah that fixed it, but I wanted RemoveAAA, so I put it back in and started checking permissions. All my permissions were stored in the old oxide folder. I really didn't want to risk over writing anything once I had figured it out so just went into redoing all the permissions.

 

Ah, yes I'm still doing that right now. I've been confused as to why my Oxide folder isn't where every post i've ever read said it should be, but the plugins run so I just kinda went with it Situations like this make the absence of a .yaml or .json file for perms wholly inconvenient. :/ It'd be great to just look at the list and be able to pick out discrepancies or run it through a parser to see if there are syntax mistakes. lol

 

Ah, I bought and set up my server the night before last, so that explains much! Thanks so much for your reply, Wulf! I've been able to grab out the perms file and have a look-see with notepad++, where I can also make notes about nodes to remove, add or otherwise edit so i know what to do when I get back to the console. MOST helpful!!! <3