To my excitement, it seems I got atleast one fracture so far to link up to the emptiness within a Cubic Chunks world (also the first one I tried so far).

In using it however, I receive the following crash. Would you perhaps be able to see on what end the issue occurs, and if it's worth fixing?

Sincerely,
Hyxaru
crash-2020-09-22_21.48.42-server.txt

Can you post your debug.log (redacting any information from it as needed)? It might have some extra information for me about what the fracture was trying to do.

Also, from your crash log it looks like the fracture was in the nether, and was trying to link to a fracture in the dimension with id 4. Did you set the Emptiness to that ID, or if not, what dimension is that?

Currently my emptiness dimension is set as cubic, and the fracture locator and warding seem to work just fine.
Also indeed changing that configuration and manually securing the link with nbt edit worked.
The fracture in question would send me to the correct x and z, but the placed me at y0. Very likely due to CC. I editted the linkpos to the propper y value and it works smoothly.

It appears it was indeed connected to dim4, a non existent dimension. A leftover from some meddling I did in the config a long time ago. Since the mod updated, I went through the configuration again. I thought the config had entirely refreshed due to new entries, but apparently not.

I have no idea which supposed old version of CC did allow me to travel through fractures btw. I am not entirely sure if it ever did. The links are always invalid.

If I manually change the nbt data of a fracture to linkinvalid:0, and have the last configuration entry set to true so that they ignore checking again, it should work right? Although who knows where the player ends up.

The mod checks if the worlds actually exist on world load before adding them to the list of dimensions available for fractures to go to - that's how I can ship a default config with a whole bunch of modded dimensions in them. And yes, if you reset that flag on the fracture back to 0 and enable that config option it will take you somewhere, but no promises on whether that somewhere is anywhere safe or not.

I'll also check if I can do something to make the fracture checks work with CC. I have a feeling the way I do it might not be appreciated by CC, so a slightly different approach might be better. If you do go through some fractures and can confirm or deny that they always appear between y=0 and y=255, that would be helpful.

On the topic of CC things, I have a feeling that Fracture Locators and the Ward focus will be broken. They use chunk-based storage, like Vis does in TC, and I don't think those are implemented in CC. It would probably take CC-specific implementations of these things to make them work, which isn't out of the question but probably not the highest priority thing.