So pretty simple. It'd be cool if in the json we can include a "group" that the structure spawning optionally considers when calculating distance from same type. I think the addition of "minDistanceToSameTypeStructures" is amazing and likely already positioned well for this kind of change.
The addition of something like "structureGroup" would then just add a check to see if the structure is part of the group in addition to the checks for same type structures distance. If there wasn't a group listed, then just handle it as "minDistanceToSameTypeStructures" currently does.
As an example, I happen to have a few structures where they are essentially 2 of the same structure with different decoration to tailor it to the world which currently means then they can still spawn next to each other. This example shows the old Ice and Fire gorgon temple. Typically, stock ice and fire, spawn them on the beach or gravel beach, but they would always spawn 1 block lower than they should, so I use pillar to spawn them more correctly.

I also have different types of dungeons that I don't want spawning near or on top of each other. I also have a farm house category which I want to spawn at regular intervals which spawns a unique house and food supply depending on the biome.
I think the biggest problem I can forsee with this type of system is the requirement of the modpack dev to essentially "thread the needle." If my criteria is too restrictive the structures might always fail to spawn causing confusion.
So pretty simple. It'd be cool if in the json we can include a "group" that the structure spawning optionally considers when calculating distance from same type. I think the addition of "minDistanceToSameTypeStructures" is amazing and likely already positioned well for this kind of change.
The addition of something like "structureGroup" would then just add a check to see if the structure is part of the group in addition to the checks for same type structures distance. If there wasn't a group listed, then just handle it as "minDistanceToSameTypeStructures" currently does.
As an example, I happen to have a few structures where they are essentially 2 of the same structure with different decoration to tailor it to the world which currently means then they can still spawn next to each other. This example shows the old Ice and Fire gorgon temple. Typically, stock ice and fire, spawn them on the beach or gravel beach, but they would always spawn 1 block lower than they should, so I use pillar to spawn them more correctly.

I also have different types of dungeons that I don't want spawning near or on top of each other. I also have a farm house category which I want to spawn at regular intervals which spawns a unique house and food supply depending on the biome.
I think the biggest problem I can forsee with this type of system is the requirement of the modpack dev to essentially "thread the needle." If my criteria is too restrictive the structures might always fail to spawn causing confusion.