Troubleshooting

This page is intended to provide help with setting up RSP or to recover from errors.

[UNDER CONSTRUCTION (always)]

Reporting Problems

In order to make a possible solution available as quickly as possible, note the following:

• Get the craftbukkit version from the logs or with the '/version' command.
• Get the version for the plugins from the logs or with the '/version <plugin>' command, typically involved are:
  • RSP
  • Your permissions plugin (PermissionsEx, bPermissions, Vault + whatever plugin is used for permissions: PermissionsBukkit, ...).
  • WorldGuard
• Send me the configuration of RSP, maybe that of the permission plugin too or the relevant parts. You need not post it publicly, but leave a note if you send it by mail, or paste it in the pm using YAML code tags (WikiCreole: <<code YAML>> ... <</code>>), for instance.
• Describe what happens and what you expected to happen. [More info to be added.]

How to test

If you use RSP for the first time, start off with the most simple configuration:

• Test it on a (local) test server first, using transient-groups or the permissions plugin of your choice.
• One permdef, one region, one group, one permission for the group.
• Permissions plugin: Use a newly created group name to hold the permission(s), to avoid complex roll-backs in case of trouble.
• Use all-lower-case names permdef, spell the world name exactly as the names are in the server directory, spell the region name exactly as WorldGuard lists it (correct case). Spell the group name exacttly. Probably also avoid special characters.
• Check out the Examples page, if they match your configuration.
• Advanced: You can test with other group uses than have-inside... have-inside = add-enter + remove-exit , you can test if permissions get added with add-enter and if removing works with another region that ust has remove-enter . The difference to testing with have-inside is, that all groups that are used with have-inside or remove-exit will get removed on checkout and also will be checked when a player joins. So using add-enter and remove-enter for two different regions can help to avoid automatic removal of permissions.
• Combine with the /ping ... command (0.12.0-DEV-6), to see where you have a certain permission and where not.
• Test with transient-groups first, then see if it works with the permission plugin too, if that is needed at all!
• [More to come with time, requests, experience...]

"Correct" case

In the RSP configuration you have to use the correct case for worlds, region names, permdef names, otherwise settings will not be recognized.
***
Some permission plugins like bPermissions have a configuration option to use lower case, or they demand it by default. In such case you might try using all lower case group names in the RSP configuration (not sure about permissions).

Configuration

Some points to know:

• Do not use tabs, only spaces. If you have a text editor that allows for putting spaces instead of tabs, that might be a good choice.
• Keep the entries for a section on exactly the same level:
  Correct example (saving period, use-worlds):

permissions:
    saving period: 180
    use-worlds: true

• Do not create duplicate sections!
  These might lead to one or more of them not being recognized.
  Correct example:

links:
    world:
        town1:
        - shopmaster
# NOW TO CREATE ANOTHER LINK FOR THE SAME WORLD,
# DO NOT DUPLICATE THE WORLD SECTION:
    #world: # <- AVOID ! (commented out, so it is no problem.)
        # Start at the same level as the previous entry for world:
        town2:
        - ilpeutdetreyavoirdelorage
        - shopmaster

Plugins

For more information about specific plugins such as Vault,
see: Troubleshooting/plugins

Examples

Visit the Examples page !