You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 5, 2019. It is now read-only.
-I expected for these permissions, with the in-game faction permission settings being set to only allow people in the faction to access containers and doors, to prevent outsiders from accessing chests, furnaces and doors for an example. However any user can freely access what they want and when they want, this is certainly annoying because the whole premise of our server is to stop users from doing such. Furthermore this was never an issue with the previous versions of factions alongside the same plugins we use to date, However even when using the old jar we used which was quoted as being version 2.8.1, still created the same problems in version 1.13.1.
The text was updated successfully, but these errors were encountered:
Affected Plugin Name: Factions
Affected Plugin Version: 2.14.0
Server Version: 1.13.1 "Spigot: R0.1 Snapshot"
-Steps to reproduce this bug:
4.Do 3 days of troubleshooting and finally come to complain 🤣 .
Information
-Log: https://pastebin.com/y64esafN
-Config Files::
+Factions Config: https://pastebin.com/BdpiUs19
+Default Container Perms: https://pastebin.com/99B4h9qR
+Default Door Perms: https://pastebin.com/Zx2GLsU3
+Plugins we use: https://pastebin.com/A5P42WwA
-I expected for these permissions, with the in-game faction permission settings being set to only allow people in the faction to access containers and doors, to prevent outsiders from accessing chests, furnaces and doors for an example. However any user can freely access what they want and when they want, this is certainly annoying because the whole premise of our server is to stop users from doing such. Furthermore this was never an issue with the previous versions of factions alongside the same plugins we use to date, However even when using the old jar we used which was quoted as being version 2.8.1, still created the same problems in version 1.13.1.
The text was updated successfully, but these errors were encountered: