Commit Graph

18 Commits

Author SHA1 Message Date
Luke aka SwissalpS
d2b227eca6
Make smallest area concept optional (#80)
This restores the behaviour to before #79.
2024-10-01 17:54:47 +02:00
Luke aka SwissalpS
c2e3d073be
Use smallest area at given position (#79)
When checking for permission to interact, currently the smallest id takes precedence in a situation where areas enclose other areas. This makes it complicated to set up private areas within faction areas and vice versa. Same applies for open areas within a bigger private area.

When multiple areas have the same volume, players seem to agree that the most recently protected area should also take precedence.
Since we can't guarantee that the largest id is the most recent, we still use that info as we have no other way to determine age.
2024-09-11 22:00:47 +02:00
tour
0bad0ec0ae
Allow custom checks before allowing a player to protect new areas (#74) 2024-03-22 22:26:12 +01:00
Kalio_42
c167b30ebf
Adapt to the new version of playerfactions (#48)
Enable to open an area to many factions
    Update to adapt to the new version of playerfactions mod, with its new multi-faction mode
2020-09-05 18:49:17 +02:00
MoNTE48
800a93f5ee Minor cleanup 2020-06-04 20:36:12 +02:00
Alden Peeters
aca830fd22 Add support for playerfactions mod (#37)
Add faction indicator to HUD
2019-09-21 15:33:42 +02:00
sofar
1bbb997c7a
Add callbacks for area operations 2019-04-01 20:28:50 -07:00
Tai @ Flex
6080ff065e Add API for adding areas to HUD 2016-12-19 16:36:37 +00:00
est31
8b0b8c1ad2 Add support for the AreaStore API 2015-10-29 16:49:35 -04:00
ShadowNinja
e4aef02cb9 Add areas_high_limit privilege for trusted players 2014-11-14 13:21:09 -05:00
ShadowNinja
65013863b2 Make canInteractInArea player optional and add an admin check 2014-07-12 19:06:05 -04:00
ShadowNinja
e17cda925b Add canInteractInArea 2014-07-12 16:37:54 -04:00
ShadowNinja
ce8891a325 Allow open areas inside closed areas to be used openly 2014-03-23 12:25:44 -04:00
Ciaran Gultnieks
1a5efd07f1 Allow areas to be optionally open to all other users
In other words, you can retain ownership of an area but disable and
re-enable the protection aspect at will, via the area_open chat command.

By default, nothing is any different following this commit - all
existing areas are protected, as are new ones. But you can do (for
example) "area_open 1" and if you're the owner of that area, it's
now possible for other users to interact there. "area_open 1" again to
toggle the protection back on.

Where there are sub-areas, the main owner and ALL sub-area owners at a
particulare location must have set the areas to open to disable
protection.
2014-02-07 18:07:56 -05:00
ShadowNinja
ed7f57bf2f Add IDs to HUD and areas:getAreasAtPos(pos) 2014-01-15 20:10:24 -05:00
ShadowNinja
f096fb4dbb Use table indices as IDs
This significantly optimizes a lot of operations and removes redundancy.
2013-11-18 21:12:09 -05:00
ShadowNinja
b40b9d2c39 Move areas.hasOwner 2013-11-14 18:26:57 -05:00
ShadowNinja
4ae050a3ae Initial commit 2013-09-02 19:16:14 -04:00