9 Commits

Author	SHA1	Message	Date
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