I have the mod, "Space Exploration" installed alongside this one, and there is a conflict on startup:

Failed to load mods: Error in assignID: autoplace-control with name 'prismite-ore' does not exist

Source: prismite-ore (resource).
Mods to be disabled:
Voidcraft (2.4.3)
alien-biomes (0.7.4)
space-exploration (0.7.35)
space-exploration-postprocess (0.7.4)

The conflicting code is probably in the file "prismite-common" in your mod, and most likely in the file "resource_autoplace_overrides" from SE. The error likely isn't your mod's fault, and instead SE's fault, because they completely rework the autoplace system. If you would like, you can add a setting to disable the prismite resource generation, which should fix the error. Thank you for taking the time to read this.

Space Exploration seems to assume that every resource has an autoplace control. This is not necessarily a valid assumption, so is probably something that should be fixed on SE's end.

Space Exploration seems to assume that every resource has an autoplace control. This is not necessarily a valid assumption, so is probably something that should be fixed on SE's end.

To be fair, IMO it would be a safe assumption on SE to think that ores were meant to be placed on the map and mined, as long as there is a toggle for this sort of situation.

Which, if I understood Bob_lob_law's post correctly, actually exists.

Because like, if Prismite isn't meant to be generated, and the error can be fixed by marking the resource as something that shouldn't be generated, then it should be simple to fix, no?

It has long been a stance of mine that mods with restrictive licenses (like Space Exploration) get significantly less latitude than mods with free licenses (like MIT or GPL) when it comes to the amount of work that I'm willing to do to support them. If they don't want to share, that's their right, but then I figure they can clean up their own mess. I am not pursuing this.