This was suggested by RBA to fix the follow.
```
18:43:28: ACTION[ServerThread]: Sofia punches object -27616: LuaEntitySAO at (13.9607,18.7545,-77.3249)
18:43:41: ERROR[main]: ERROR: An unhandled exception occurred: /home/minetest/Server/bin/../mods/areas/api.lua:5: attempt to index local 'pos' (a nil value)
18:43:41: ERROR[main]: stack traceback:
18:43:41: ERROR[main]: /home/minetest/Server/bin/../mods/areas/api.lua:5: in function 'getAreasAtPos'
18:43:41: ERROR[main]: /home/minetest/Server/bin/../mods/areas/legacy.lua:101: in function 'HasOwner'
18:43:41: ERROR[main]: ...inetest/Server/bin/../mods/plantlife/plants_lib/init.lua:448: in function 'node_is_owned'
18:43:41: ERROR[main]: ...etest/Server/bin/../mods/plantlife/flowers_plus/init.lua:97: in function <...etest/Server/bin/../mods/plantlife/flowers_plus/init.lua:74>
In thread b693a220:
/home/minetest/Server/src/main.cpp:1870: int main(int, char**): Assertion '0' failed.
Debug stacks:
DEBUG STACK FOR THREAD b20ff440:
#0 virtual void* CurlFetchThread::Thread()
DEBUG STACK FOR THREAD b693a220:
#0 int main(int, char**)
(Leftover data: #1 Dedicated server branch)
(Leftover data: #2 virtual void ServerMap::save(ModifiedState))
(Leftover data: #3 virtual void Database_SQLite3::saveBlock(MapBlock*))
(Leftover data: #4 void ItemStack::serialize(std::ostream&) const)
Aborted
```
I did not test that yet, will comment again here when tested.
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.
