Bukkit

Since RSP 0.9.2 you can have a set of specific settings for each world, which default to the basic settings.

Default configuration of RSP 0.11.7:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20

create-portals: false
errors:
    log:
        min-delay: 10000
stats:
    use: true
    show:
        range: false
    log: false
permissions:
    saving-period: 180
    save:
        on-check: false
        on-checkout: false
player-cache:
    lifetime: 12345
heuristic:
    lazy-dist: 5
confine:
    enabled: false

The entry create-portals only takes effect, if you use confinement settings. It has a more or less distant abuse potential (see below) for it creates portals to check if a player may move there, and might not respect things like WorldGuard regions for that. Thus it is set to false by default. The effect of create-portals being set to false is that the standard confinement violation treatment will be applied, instead of just denying the portal use, which might lead to teleport the player "somewhere" next to inside of the confinement or to the last valid position.

Examples for confinement and world specific settings:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17

confine:
    enabled: true
    center:
        x: 0
        z: 0
    radius: 2500
    circular: true
    message: 'World border reached !'
    resetto:
        recent: true

worlds:
    infinite_world:
        confine:
            enabled: false
        heuristic:
            lazy-dist: 10000

On "ground level" of the configuration file you can define confinement settings and lazy-dist which will be treated as default settings for all worlds, unless specific settings are given there.
Here The default confinement is set to circular with a radius of 2500 blocks to each direction (height is not checked).
The message need not be set, same as the resetto.recent setting (see below).
For world specific settings you have the section "worlds", which here stats that some world should not use confinement and have a very big lazy dist, which makes sense if there are no region specific permissions for that world.

Setting circular to false leads to more "minecraft-natural" feeling of the world border, due to being able to walk next to it, which is difficult with a circular border.

Standard confinement vilolation behavior:

• If the resetto.recent setting is set to true, RSP will attempt to teleport the player to the last "valid" position, which is "acurate" within lazy-dist. Actually this should never be a cross-world position, but i am not 100% sure, so if the behavior given below is ok, the most safe setting will be set this to false, to avoid strange effects, that might occur with presence of other plugins, potentially. I had no problems with this yet, but if so, this setting allows to force in-world teleport at the cost of reset-accuracy.
• If no "valid" position is stored (either due to simply not being present, or because resetto.recent is set to false), then the player will be teleported "somewhere" inside of the confinement, to the highest block that is just inside of the confinement:
  • circular: Along the line from the player to the center.
  • rectangular( circular=false): Orthogonally towards center both for x and z independently.
• If an action leading to an invalid position can be canceled, such will be attempted.