Simple example: bPermissions

This example lets all (default) users use the command '/time add <amount> ' inside a specific region.

World name: world
Region name: test_rsp (to be created with WorldGuard)
Permission group: timetest

Notes:

• Make the region big enough to allow for some inaccuracy with a lazy-dist setting of 5, or adjust lazy-dist to a lower value (at the cost of some performance).
• If your world name differs from 'world', then change it in the links section of the RSP configuration.
• In this example the filter-permission is added to the default group (presumably everyone) of course you can add the permission to some tester-group and use it that way then.
• Latest versions of bPermissions feature an auto-save option by configuration. If you set this to false, permission changes will not be saved to disk directly, but require explicit saving. In that case you will have to enable the saving options in the RSP configuration !

/plugins/RSP/rsp.yml

# DEFAULT CONFIGURATION OF RSP 0.12.0-DEV-3
create-portals: false
errors:
    log:
        min-delay: 10000
stats:
    use: true
    show:
        range: false
    log: false
load-plugins: []
permissions:
    saving-period: 180
    save:
        on-check: false
        on-checkout: false
    use-worlds: true
player-cache:
    lifetime: 12345
generic-links:
    ownership: []
    online: []
heuristic:
    lazy-dist: 5
confine:
    enabled: false
# ADDED PARTS (PERMDEFS + LINKS)
# PERMDEFS:
permdefs:
    test_time:
        ignore-perm: test.ignore.test
        filter-perm: test.test.test
        have-inside:
            groups:
            - timetest
# LINKS:
links:
    world:
        test_rsp:
        - test_time

plugins/bPermissions/.../groups.yml

groups:
    default:
        permissions:
        - test.test.test
        # ... more permissions ...
    timetest:
        permissions:
        - bukkit.command.time.add
    # ... more groups ...