Bukkit

I'm making newer version (0.9.x branch) with separated API/Engine, Bukkit and Sponge implementations. It has (will have) some improvements.

Look at github for details, download is available at Jenkins (links are present in description).

@ultrafastphil

Of cause. Several ways can help you reach this:

• Different default groups on servers, you can set it on config.yml. Here you should not enter user in database completely.
• Set different server-ids in your server.properties file (for example, server-id=server1 and server-id=server2). In rscp's inheritance table add two rows with user entity (entity type = 1), use user's name (1.7.x or below) or UUID (1.7.x or upper, can be '-' separated or not). Enter different parent groups for these two rows and set your server-Ids into destination column: @server1 and @server2.
• Inherit your default group from other groups based on destinations @server1 and @server2.

@thecutter13

Hi! Ok, I've published source code on GitHub. Currently making a little cleanup but feel free to learn it's internals and making pull requests if something you found wrong.

All my free time now is taken by preparing my own server to start so I won't make huge changes in code. But I will check issues and pull requests everyday two or more times :)

Hi! On prelogin event player entity is put into async query to build permission tree for him. Parallel thread gets it, calculates permissions and assigns them to player on the nearest tick. But at prelogin we have no location so player is supposed to be on concrete server but In no world and no one region. After join event we have location so I put his entity to recalculation again. This is why you can observe little delay. Also region-finder-thread config option can affect it (default 1 sec delay).

Prefixes and suffixes become known during the same process of permission tree resolution. I should think about it at morning )) Sorry, end of post Zzzz

@Edgxxar

Plugin always delete rows from table entities where prefix is null or empty AND suffix is null or empty. If any of it set then it will be kept. Plugin always delete rows from tables permissions and inheritance if their lifetime is expired.

Plugins is build in that way he internally knows about players and groups if they are present in only one any table (e/p/i/l). You have not to create rows in all or entities tables if you want just to assign permissions or inheritance. My original idea was to keep tables simplicity and sufficiency of minimum number of rows in it.

Lifetime column (MySQL's TIMESTAMP) has meaning "this row is applicable until" and the value should be entered in the form 2014-05-31 23:59:59, e.g. Also if you have separate database server look at your clock synchronization. On connect plugin drop all expired rows based on db's time but internally it has only jvm host's time. Can have some minor inconsistencies here =)

P.S. Sorry if some mistakes, my english is not good too :)

@Zack_Piper

Hi, we're thinking about advantages and disadvantages of opening source code. Decision will be made some time later.

@gwinny7

Report please if not. I have limited possibilities to testing it but nobody creates bug tickets so I always think it is working :)

@octoshrimpy

It seems to be a good idea! I should think about it i details... Thanks :)