Is it possible to "pre-profile" Mystcraft to be more performance friendly?

[TheDeviantCrafter]

Mystcraft requires profiling which can be pretty intensive on lower quality machines. It needs to create scripts that take all of the dimensions, ores and whatnot into account so dimensions can be generated smoothly.

Does this need to be done at run time by my end users, though? Could I pre-profile it on my side, then release the pack with those profiles completed? Assuming they don't change anything, the profiling on my side and on my user's side should come up with exactly the same results, right? The list of biomes will be the same.

[XCompWiz]

You have a few options. I'll need to write up proper documentation for the instability configs on our wiki, but you could specify the numbers in config.

The profile result data can also be distributed and used. It's stored in the mystcraft folder at the same level as the saves folder.

[keybounce]

One thing that I noticed is that the default configs do one chunk every 5 ticks, I think.

I think this is the biggest reason that profiling seems to take forever. Even if you have a decent machine, it takes a long time to generate all those chunks, especially with all the mod biomes that exist.

[keybounce]

but you could specify the numbers in config.

It would be nice if there was some way to tell Mystcraft to write the numbers out from the profiling data into the config file.

[Shahelion]

If I use the config option to read a file instead, does it work fine or will I have problems?

Apologies for the resurrection of this post, but it's relevant.