ORR - OKRealmRestrictby Kalman OlahLatest version: 1.3.2 ( Download )Would you like to buy me a drink? some useless stuff from Amazon? a car?What is OKRealmRestrict?OKRealmRestrict is a lightweight little Bukkit plugin that allows you to restrict access to certain worlds on your server, using Permissions, GroupManager, PermissionsEx or Bukkit's permissions. And if that wasn't enough, it also allows you to ban certain players from entering specific worlds!Where can I get OKRealmRestrict?You can always download the latest version of OKRealmRestrict right here.The full URL is http://kalmanolah.net/files/dl.php?id=OKRealmRestrict&ver=latest .It also comes with a handy auto-updater that will download updates to the /plugins/OKRealmRestrict/update folder. How do I set up OKRealmRestrict?Setting up OKRealmRestrict is pretty easy. It can all be summed up into a couple of easy steps. You download the latest version of OKRealmRestrict(here). You extract OKRealmRestrict.jar to your /plugins/ folder. You start your server so OKRealmRestrict can generate a configuration file. You fill in your configuration file like this: Code: global: main-world-name: Worldname nopermission-message: You don't have access to this world. where 'main-world-name' is the name of your main world, and 'nopermission-message' is the message a user will see if they don't have the permission node required to access a world. You give your users the permission nodes needed to access the worlds you want them to be able to access: If you would like a user to be able to access a world called "Terra", you should give them the permission node "okrealmrestrict.world.Terra" in both the world they will be entering Terra from, and Terra itself. Note: If you don't give them the permission node "okrealmrestrict.world.Terra" in the world "Terra", but only in the world they enter the world "Terra" from, they will be teleported to the main world's spawn upon their next login. e.g.: World is called "TestWorld" -> Permission node: "okrealmrestrict.world.TestWorld". You restart your server. How do I use OKRealmRestrict? Next to restricting world access based on Permissions groups, OKRealmRestrict also allows moderators to ban players from certain worlds, even if they have the permission nodes to access those worlds. Aside from this, a moderator's permission node can override any need for world-specific permission nodes and world-specific bans.Commands: Permission nodes: Changelog: Version 1.3.2 Added anonymous stat tracking. Can be turned off in config. Updated auto-updater. Cleaned code. Uses new bukkit configuration API. Version 1.3.0 Renamed to OKRealmRestrict. Changed all permissions nodes to okrealmrestrict.<node>. Added support for GroupManager, Bukkit's permissions, PermissionsEx, Permissions. Added to OK Suite. Older versions (Move your mouse to reveal the content) Older versions (open) Older versions (close) Version 1.2.5 Auto-updater bugfix. Version 1.2.4 Minor bugfix to fix issues when the auto-updater can't connect to the update server. Version 1.2.3 Minor bugfix. Version 1.2.2 Made final changes to the auto-updater. Version 1.2.1 Updated the auto-updater. Version 1.2.0 RealmRestrict now automatically downloads new versions to the /plugins/RealmRestrict/update/ folder. Version 1.1.0 Fixed some bugs with teleports getting cancelled. If a player doesn't have the required permission node for a world in the world itself, but does have it in a world he can enter from, RealmRestrict will let that player access the world, but will teleport him to the main world's spawn upon logging in. e.g.: Player1 has permission node "rr.world.TestWorld1" in TestWorld2, but not in TestWorld1 -> RealmRestrict lets that player in to TestWorld1 from TestWorld2, but teleports him back to the main world's spawn upon his next login. Version 1.0.0 Initial release.