rscPermissions is a Bukkit/Sponge/Nakkit permission management plugin with an impressive and unique features designed especially for multiserver environments.
maybe this is one problem too. Why people don´t use it. I think most people who look for a multi server permission plugin handle some give/revoke permissions via other plugins and this only works if you can edit them via the console. I would like to use this plugin but without console commands which allow me to add/remove permissions to user and group and of course with the timed feature doesn´t work for me. I would have to rebuild the whole servers permission system. I have no problem to import the thousend permissions for every server and to optimize them with the .? feature. But I use buycraft so permissions have to be given via commands. I use my own class plugin which only allows the use of certaint items which is handled via player permissions....
Could you say that you have some time and add the commands system soon ? If yes about how long will it take ?
Sorry, currently you have to edit database by your own with 3rd party tool. My task is to implement all commands before release state v1.0. I'm lazy a little :)
one more question about the commands. If I would like to give permissions via commands, like on a buycraft pruches; I would like to give a player a special permission (no group promotion) how do I do this. Seems like this isn´t possible yet..:(
sounds awesome. I´m looking since 4 months for an alternative for pex which has a clear mysql structure, caches inheritances, allows per server permissions, is downwards compatible (at least 1.4.7) and handles * not that dump as pex does (vanishnopacket, herochat issues).
Hello! Yes, it is new and is not used widely. I think the main problems are bad promotion from my side and targetting for middle or high quality server personal. Yes, it seems to be hard to understand all of this features like abstract permissions and ladders.
But it is totally stable at last for my several servers that I run for about half of a year.
I have no tickets or any reports about problems so I think I can decide that it totally stable.
It is marked as beta just because not 100% of Vault sopport done inside and not all ingame commands are implemented.
If you do not need to edit perm lists with commands like in pex's style (/rscp user Notch add permission worldedit.wand d="world" l=100 t="1 week 2 days") and able just open MySQL Workbench or phpMyAdmin — this plugin for you. All general things are working 100% stable.
mhh, the mcstats show that it is not realy used. Are the basic features stable, as I coudln´t find any other perm plugin with per-server-perm support ?
Yes, it was done in 1.2.27 :) Currently rscp have support for a some Vault functions but not all. I should implement all of them before rscp v1.0 release.
lifetime column is exactly that you need. User will have this permission until timestamp expires. After that, rscp automatically delete this record from database. In general, rscp always drop all rows with elapsed timestamps on connecting to database:
Logging out/in/out/in/etc don't affect the permission. rscp doesn't support such permissions that are existing only until logout. It is always in sync with database.
For several permissions if their number is great it is logically simplier to create group containing this permission set and add timed inheritance.
The issue we have is, we are currently using Pex and their timed permission system cannot do what we need. Is there any way to give players a specific permission node for a set duration? Also, would they lose the permission upon logging out?
Timed group inheritance is the base possibility of this plugin and was implemented already at alpha builds. Just use `lifetime` column for inheritance rows.
All subjects like permissions for groups (p2g), permissions for users (p2u), user's parent groups (g2u) and group's parent groups (g2g) are conditional and can depend on destination (region:world@serverId), expirience (number of xp levels of a target player) and/or lifetime (be timed).
Hey there, seems like the perfect permissions plugin for Multiserver usage, I really need the timed group inheritance, though, before I can use this. Please add this feature as soon as possible! :D
Try development build #70, it brings working importing of PermissionsEx (but from SQL version). Just migrate pex from yaml to sql (tutorial can be found on it's page).
After that you should have three pex's tables in the same database as rscp: permissions, permissions_entities and permissions_inheritance. Start server with rscp and enter command /rscp import pex-sql
Please do not enter it many times because MySQL will duplicate rows (it suppose that unique key containing one or more null columns is not duplicate with any other, event with the same NULL values...). Now I'm fighting with this MySQL behavior and realizing pex-yaml converter.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
@SimSonic
maybe this is one problem too. Why people don´t use it. I think most people who look for a multi server permission plugin handle some give/revoke permissions via other plugins and this only works if you can edit them via the console. I would like to use this plugin but without console commands which allow me to add/remove permissions to user and group and of course with the timed feature doesn´t work for me. I would have to rebuild the whole servers permission system. I have no problem to import the thousend permissions for every server and to optimize them with the .? feature. But I use buycraft so permissions have to be given via commands. I use my own class plugin which only allows the use of certaint items which is handled via player permissions....
Could you say that you have some time and add the commands system soon ? If yes about how long will it take ?
@SimSonic
what ?
@Slind14
I perhap that is can be compatible with earlier versions but I can't test it :) it uses only superprems api and nothing more.
@Slind14
Sorry, currently you have to edit database by your own with 3rd party tool. My task is to implement all commands before release state v1.0. I'm lazy a little :)
@SimSonic
one more question about the commands. If I would like to give permissions via commands, like on a buycraft pruches; I would like to give a player a special permission (no group promotion) how do I do this. Seems like this isn´t possible yet..:(
@SimSonic
sounds awesome. I´m looking since 4 months for an alternative for pex which has a clear mysql structure, caches inheritances, allows per server permissions, is downwards compatible (at least 1.4.7) and handles * not that dump as pex does (vanishnopacket, herochat issues).
@Slind14
Hello! Yes, it is new and is not used widely. I think the main problems are bad promotion from my side and targetting for middle or high quality server personal. Yes, it seems to be hard to understand all of this features like abstract permissions and ladders.
But it is totally stable at last for my several servers that I run for about half of a year.
I have no tickets or any reports about problems so I think I can decide that it totally stable.
It is marked as beta just because not 100% of Vault sopport done inside and not all ingame commands are implemented.
If you do not need to edit perm lists with commands like in pex's style (/rscp user Notch add permission worldedit.wand d="world" l=100 t="1 week 2 days") and able just open MySQL Workbench or phpMyAdmin — this plugin for you. All general things are working 100% stable.
mhh, the mcstats show that it is not realy used. Are the basic features stable, as I coudln´t find any other perm plugin with per-server-perm support ?
@tgndev
Yes, it was done in 1.2.27 :) Currently rscp have support for a some Vault functions but not all. I should implement all of them before rscp v1.0 release.
VAULT update! Compatible with rscpermissions.
@SimSonic
Thank you sir, Let me know if any jobs pop up that you would like me to do. I.E Documenting things :P
@danjb2000
Hello! Glad to see you in command!
@SimSonic
Perfect, thank you very much! Using this now :D
@Zazeca
lifetime column is exactly that you need. User will have this permission until timestamp expires. After that, rscp automatically delete this record from database. In general, rscp always drop all rows with elapsed timestamps on connecting to database:
Logging out/in/out/in/etc don't affect the permission. rscp doesn't support such permissions that are existing only until logout. It is always in sync with database.
For several permissions if their number is great it is logically simplier to create group containing this permission set and add timed inheritance.
@SimSonic
Hey, thanks for the reply.
The issue we have is, we are currently using Pex and their timed permission system cannot do what we need. Is there any way to give players a specific permission node for a set duration? Also, would they lose the permission upon logging out?
Thanks for the help :)
@Zazeca
Timed group inheritance is the base possibility of this plugin and was implemented already at alpha builds. Just use `lifetime` column for inheritance rows.
All subjects like permissions for groups (p2g), permissions for users (p2u), user's parent groups (g2u) and group's parent groups (g2g) are conditional and can depend on destination (region:world@serverId), expirience (number of xp levels of a target player) and/or lifetime (be timed).
Hey there, seems like the perfect permissions plugin for Multiserver usage, I really need the timed group inheritance, though, before I can use this. Please add this feature as soon as possible! :D
Thanks
During testing I've dropped away my own database with permissions for my two servers... shit >_<
@SimSonic
Will do! Thanks
@tgndev
Try development build #70, it brings working importing of PermissionsEx (but from SQL version). Just migrate pex from yaml to sql (tutorial can be found on it's page).
After that you should have three pex's tables in the same database as rscp: permissions, permissions_entities and permissions_inheritance. Start server with rscp and enter command
/rscp import pex-sql
Please do not enter it many times because MySQL will duplicate rows (it suppose that unique key containing one or more null columns is not duplicate with any other, event with the same NULL values...). Now I'm fighting with this MySQL behavior and realizing pex-yaml converter.