Recently a user on my platform informed me that I was able to modify the maximum number of slots even though the b_virtualserver_modify_maxclients permission is set to 100 modifier power, and my server's maximum power is 75.
I then tried unsuccessfully to prevent jobs from actually modifying the maximum number of users on one or more servers.
So I was able to note that any permission even though the configuration of skew, deny, or even with power needed 100 any of the posts that have permissions over 60 of modifying power can do absolutely what they want within teaspeak environments.
I have tried the new and customized jobs, none of the permissions that should be locked remain, with a simple click for example the user can enable or disable login as serverquery on my server.
Is this frustrating, is there a bug in the permissions system?
Additional Information
1. The test was based on versions 1.2.31, 1.2.32, 1.2.34 and 1.3.0
All learn the same behavior.
I then tried unsuccessfully to prevent jobs from actually modifying the maximum number of users on one or more servers.
So I was able to note that any permission even though the configuration of skew, deny, or even with power needed 100 any of the posts that have permissions over 60 of modifying power can do absolutely what they want within teaspeak environments.
I have tried the new and customized jobs, none of the permissions that should be locked remain, with a simple click for example the user can enable or disable login as serverquery on my server.
Is this frustrating, is there a bug in the permissions system?
Additional Information
1. The test was based on versions 1.2.31, 1.2.32, 1.2.34 and 1.3.0
All learn the same behavior.