areas - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2016-12-19	Add API for adding areas to HUD	Tai @ Flex

2015-10-29	Add support for the AreaStore API	est31

2014-11-14	Add areas_high_limit privilege for trusted players	ShadowNinja

2014-07-12	Make canInteractInArea player optional and add an admin check	ShadowNinja

2014-07-12	Add canInteractInArea	ShadowNinja

2014-03-23	Allow open areas inside closed areas to be used openly	ShadowNinja

2014-02-07	Allow areas to be optionally open to all other users	Ciaran Gultnieks
	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-01-15	Add IDs to HUD and areas:getAreasAtPos(pos)	ShadowNinja

2013-11-18	Use table indices as IDs	ShadowNinja
	This significantly optimizes a lot of operations and removes redundancy.
2013-11-14	Move areas.hasOwner	ShadowNinja

2013-09-02	Initial commit	ShadowNinja