Areas Rework #6497

New Issue

tour · 2024-03-15T23:42:23Z

tour commented

2024-03-15 23:42:23 +00:00

There are so many open issues about areas. I guess its no good to write a GUI #6397 while planning changes that will change the interactions with areas. First code the features, then add a GUI around it :-)
Alias already made a checklist of what needs to be done: #4145 (comment)

Please notify me if anyone would like to pick this up, I#ll give you access to the relevant repo.

Here I am!

I guess the combination of two mayor changes will solve a lot of problems:

let /protect* take an area id as optional param. If the new area is fully inside the one from the id, let it be a subarea. This will make city accounts obsolete. One could work to disable the /change_owner bug.
Disable the creation of new masterareas if it overlaps with an existing area (or with the distance given to an existing area). I've already made a pr to areas (https://github.com/minetest-mods/areas/pull/74). If it gets merged, this shouldn't be too hard.

Alias states in #4331 that within the distance ranges of other areas/citys no new masterareas should be allowed. I can also imagine a /yes /no command to be run before the protection. But can also implement the proposed way.

There are quite a lot of issues about areas. Mostly no GUI/confusing chatcommands. I will try to deal with them in #6397.
Most of these issues are somewhat dupes of each other, some have unique ideas. Just adding some to keep track while coding.
#4770
#5159 (Is this still an option?)
#6147
#6071 (Follow discussion, give it a prominent place in the GUI)
#5291
#5271
#4331
#1848 (note that the formspec in my areasGUI already supports sorting)
#2324 (areasGUI has that feature already)
#3406
#4105 (Especially #4105 (comment))

There are so many open issues about areas. I guess its no good to write a GUI #6397 while planning changes that will change the interactions with areas. First code the features, then add a GUI around it :-) Alias already made a checklist of what needs to be done: https://gitea.your-land.de/your-land/bugtracker/issues/4145#issuecomment-49927 > Please notify me if anyone would like to pick this up, I#ll give you access to the relevant repo. Here I am! I guess the combination of two mayor changes will solve a lot of problems: 1) let `/protect*` take an area id as optional param. If the new area is fully inside the one from the id, let it be a subarea. This will make city accounts obsolete. One could work to disable the `/change_owner` bug. 2) Disable the creation of new masterareas if it overlaps with an existing area (or with the distance given to an existing area). I've already made a pr to areas (https://github.com/minetest-mods/areas/pull/74). If it gets merged, this shouldn't be too hard. Alias states in #4331 that within the distance ranges of other areas/citys no new masterareas should be allowed. I can also imagine a /yes /no command to be run before the protection. But can also implement the proposed way. There are quite a lot of issues about areas. Mostly no GUI/confusing chatcommands. I will try to deal with them in #6397. Most of these issues are somewhat dupes of each other, some have unique ideas. Just adding some to keep track while coding. #4770 #5159 (Is this still an option?) #6147 #6071 (Follow discussion, give it a prominent place in the GUI) #5291 #5271 #4331 #1848 (note that the formspec in my areasGUI already supports sorting) #2324 (areasGUI has that feature already) #3406 #4105 (Especially https://gitea.your-land.de/your-land/bugtracker/issues/4105#issuecomment-46386)