From 1f770bcbdead83de3c0ff506c91151e87042e380 Mon Sep 17 00:00:00 2001 From: Luke aka SwissalpS Date: Mon, 23 Sep 2024 07:55:37 +0200 Subject: [PATCH] revised settingtypes.txt thanks SmallJoker --- settingtypes.txt | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/settingtypes.txt b/settingtypes.txt index 059bc35..1ca0d3f 100644 --- a/settingtypes.txt +++ b/settingtypes.txt @@ -3,15 +3,18 @@ # Static paths do not work well with settings #areas.filename (Configuration file path) string (world_path)/areas.dat -# Use smallest area volume precedence concept. (experimental may change) -# Determine area access based on the smallest area volume that contains -# the interaction position. Sharing areas is achieved with factions instead -# of using /add_owner. -# This allows players to have private areas within a greater open/shared area -# and also define open/shared areas within those private areas. -# If set to `false`: interacting is allowed if the interaction position -# resides in the players own area, area is open or shared with factions. -# Even if other more restrictive areas enclose the interaction position. +# Use smallest area volume precedence concept. (experimental; may change) +# +# If set to `true`: +# The interaction permission is defined by the smallest area volume that +# contains the interaction position. Granting access to areas is achieved +# by factions instead of using `/add_owner`. +# This allows players to have private areas within a greater open/shared +# area and also define open/shared areas within those private areas. +# If set to `false`: (default) +# Interacting is permitted if the interaction position resides in any of the +# player's own areas, shared or open areas. +# This permission is not impacted by more restrictive, intersecting areas. areas.use_smallest_area_precedence (Smallest area rules) bool false # Allow players with a privilege create their own areas using /protect