Not working after update
Not working after updateFixed
Please provide details when reporting issues.
Players can't lock giant.
When players start Giant, they can't access the mining selecter.
Merged post
No chat message get sent eather
Are you sure the permission to use it is granted?
ExcavatorLock.useAre gone 😅
Merged post
We have been using this plugin for 6 months
I'd suggest trying to grant it using lowercase. Ex. excavatorlock.use
I mean, its gone from permission manager
https://gyazo.com/07be7a60177e95b11bedddce44498d4e
I'm not familiar with that, but there are commands native to Oxide for Permissions.
Group 'default' already has permission 'excavatorlock.use'
If you're able to test an Oxide build, I made some changes related to permissions:
Windows:
https://ci.appveyor.com/api/projects/oxidemod/oxide-rust/artifacts/Oxide.Rust-develop.zip?pr=false&branch=develop
Linux:
https://ci.appveyor.com/api/projects/oxidemod/oxide-rust/artifacts/Oxide.Rust-linux-develop.zip?pr=false&branch=develop
Setting up testserver, give me 5 mins
Merged post
Seem to be working!
hello for me there seems to be another problem for me the error message comes already in use of say he says it would already use the thing with admin command clear nothing changes even reinstalling the plugin changes nothing
Just to add more details.
Due to the permissions being jacked (seeing that now) the plugin is creating null entries into the data file that it reads to recognize and track who the excavator is locked to. The ID is coming up as 0 and the name as "" so this is leading to the errors any of us are seeing.
Can confirm the permission seems to have disappeared, and I see other issues like 2 default groups, one with a capital D, and I am sure there will be more to come.
Just wanted to add more details though as a player who tried to run the monument was unable to even start the excavator while this plugin was running.
Jbird
Just to add more details.
Due to the permissions being jacked (seeing that now) the plugin is creating null entries into the data file that it reads to recognize and track who the excavator is locked to. The ID is coming up as 0 and the name as "" so this is leading to the errors any of us are seeing.
Can confirm the permission seems to have disappeared, and I see other issues like 2 default groups, one with a capital D, and I am sure there will be more to come.
Just wanted to add more details though as a player who tried to run the monument was unable to even start the excavator while this plugin was running.
Do you still have the Oxide .data files with those issues? I didn't come across that when testing.
The problem is the changes to the OnDieselEngineToggle hook. Fix that and it works.
Locked automatically
- 1
- 2