Commit Graph

22 Commits

Author SHA1 Message Date
Muhammad Nur Hidayat Yasuyoshi (MNH48.com) a23d2bad3a Manual update due to conflict
This adds part of PR #4 and they came from inpos/areas repo, author for the changes is ElementW.
2018-02-17 01:34:29 +08:00
Tai @ Flex 767d8ff348 Merge branch 'master' of https://github.com/ShadowNinja/areas
Merge ShadowNinja's version
2016-12-19 16:42:46 +00:00
Tai @ Flex 5349738fc6 stylistic fixes etc 2016-12-19 16:40:42 +00:00
Tai @ Flex 6080ff065e Add API for adding areas to HUD 2016-12-19 16:36:37 +00:00
Tai @ Flex ea0d14d312 added space for stylistic imrpovement 2016-11-28 22:51:47 +08:00
Tai @ Flex 9fc3583509 restore code style, adjust further style 2016-11-28 22:40:00 +08:00
Tai @ Flex 60d7a41c8c De-couple from original code
* `api.lua` create separate handler for listing registered nodes, leave the areas list clean
* `hud.lua` call second handler separately
* `api.md` extended and clarified documentaion
2016-11-26 13:48:48 +00:00
Tai @ Flex 4eda120fc1 rename to explicit variables 2016-11-26 13:27:15 +00:00
Tai @ Flex 77a30f9e05 commentary 2016-11-26 12:32:11 +00:00
Tai @ Flex 6708c966ca adjusted handler registration name 2016-11-26 12:23:46 +00:00
Tai @ Flex dedd0ebf6e Add handler for other mods to advise protection
* Allow other mods to register a handler to display protected areas in the hud
* remove the protector mod specific code from this areas code
2016-11-26 12:14:30 +00:00
Tai @ Flex 45afbfe8a6 add protector blocks to hud 2016-11-26 07:20:23 +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