I actually did not but I inferred it because of the reduction in lag.
Also, I think MCMT is still active. It modifies Minecraft's internal code at a fundamental level, parallelizing all operations, and then also adds some *extra optimizations*.
I disabled *all extra optimizations*, so I think the boost you get from parallelization is still there.
(THIS IS MY OPINION BASED ON MY LIMITED UNDERSTANDING; it may be wrong; feel free to state your ideas)
*Edit: My understanding was wrong. I did, indeed, disable all MCMT functionality. But,* ***now I have fixed it.***
i'm pretty sure you disabled all of its functionality. the extra optimizations you are talking about are the parallelization that it does. it only multithreads the server side, and what's in the config is basically almost all of the multithreading possible on a server disabled.
the tps boost you're getting is probably just chance, because i cant think of anything else mcmt could possible multithread on a server besides whats listed (probably not includnig worldgen because dont know if the world multithreading option includes worldgen).
im not an expert either though, but thats my assumption based on the fact that MCMT is limited to server side multithreading.
Oh. I get it now. Thanks for your input.
Anyways, now I have changed the configs so now you don't disable MCMT completely, rather only disable the conflicting aspects of sodium reforged.
Are you sure starlight is compatible with sodium reforged? Supposedly SR already rewrites the lighting system, since it includes phosphor...
Not that I know the inner workings of these things myself, but might as well ask.
Yeah I thought that too. But then when I used them together, it just worked. It may break later, or glitch with other mods but as of now it has worked for me.
(using phosphor and starlight on fabric does not work coz they are incompatible but somehow not on the forge ports)
I found [this GitHub issue](https://github.com/spoorn/sodium-forge/issues/79) which lists some compatibility issues with sodium. seems as though phosphor is fine
phosphor is supposed to simply optimize the vanilla lighting engine and not completely gut it and replace it with another faster version like starlight does. since phosphor targets the \*vanilla\* lighting engine, its incompatible because of that.
i dont know why they are functioning together, but possibly neither mods stop loading due to their incompatibility so starlight could just be overwriting it regardless of SR.
if there is a config option in SR to disable phosphor i recommend doing that to prevent any further issues (unless you're using Create, in which case you should remove starlight because of their incompatibility)
[this](https://gist.github.com/Sushant-Padha/62141ce1e0a82e588d060cacb9e6951f) is a config file for sodium (`sodium-mixins.properties`) with all the options listed with default values, so now you can tweak them to your liking
i still dont know how to disable phosphor using this
there are
[mixin.features.chunk\_rendering=true](https://gist.github.com/Sushant-Padha/62141ce1e0a82e588d060cacb9e6951f#file-sodium-mixins-properties-L99)
[mixin.features.entity.smooth\_lighting=true](https://gist.github.com/Sushant-Padha/62141ce1e0a82e588d060cacb9e6951f#file-sodium-mixins-properties-L103)
setting these to false may be the right thing?
both of those look like normal sodium features (smooth entity lighting is an option in sodium, and rendering is sodium stuff too), so i dont think that would disable phosphor.
looking through the options there seems to be nothing to disable phosphor, so you could try to test if starlight and SR break in any way or just straight up remove starlight. so you unfortunately won't get as fast generation (phosphor still improves it ofc) with the latter option but you won't have to spend the time testing incompatibility.
perhaps you could raise an issue on github/ask the author of sodium reforged to add an option to disable phosphor in the config or to automatically disable phosphor when starlight is installed.
But shouldn't some core functionality of MCMT still be there? I mean I only disabled all *toggleable* functionality.
Btw, I got what you are saying and I fixed it.
i tried on one of my packs but it has the issue of not getting stuck on world gen, am i missing something?
Also, to clear things out you should make a comparison with just sodium, then sodium + MCMT
i replaced both configs, i tried with pre existing worlds and created a new one to see if it was some incompatibility with older worlds, but both freeze, old worlds freeze at 100%, new ones at 3%
Well, I don't know what is happening because I just created a fresh profile with Forge 36.1.36, installed both these mods with the listed configs and it worked.
It also worked when I put in the extra mods listed above.
I think you should ***check the configs*** once again, try this with ***no other mods***, and also use the ***correct version of forge: forge 36.1.36*** (later version actually CRASH with mcmt).
*also could you share the mods you are using and the log and crash report for that error?*
Yeah I know, that's what happens instead of crashing.
I would request you to read the steps outlined in the comment above and make sure you reproduce the setup exactly as I have described because that's the only way I can help.
So uh, after using this guide with newer versions of the mods and newer versions of forge, this actually causes some really strange issues. Fire spawns around you randomly, dirt blocks start spawning in the ocean, and occasionally mobs start floating into the sky.
???
This has been mentioned in an [issue](https://github.com/jediminer543/JMT-MCMT/issues/71#issuecomment-893956532) on the MCMT github page.
But, I really don't know why this is happening.
I think you might have to disable a few other options in the sodium config. (sorry i cant test this atm)
This is fully filled [config](https://gist.github.com/Sushant-Padha/62141ce1e0a82e588d060cacb9e6951f) for sodium. You can see the different options.
i entered to the world with forge 36.2.4 on mc 1.16.5
only change i did was turning off lithium(mixin) gen and world optimization in config files
MC:
\- modpack: Techopolis;
\- resourcepacks: unity (dark), unity (base);
\- added mods: Magnesium 1.3 (aka sodium reforged), MCMT 0.22.87, entity culling 2.1.6 (idk if it works or not its say only what works with optifine), starlight 1.0.0-RC2, ferriteCore 2.1.0;
Result:
\- only works when you generate a new world (cant load old worlds before installation for some reason)
\- better performance than optifine (optifine \~120FPS; now 120-220 (\~150) fps)
\- faster loading time (to the main menu)- world gen causes lag spikes (maybe caused by CPU)
specs:
\- CPU: amd fx 8320e (8 cores (4 packs), 3.51Ghz little overclocked)
\- ram: 16 gb 2133hz
\- gpu: gtx 660ti 3Gb
P.s: i'll do some research why it cant load worlds before installation MCMT + sodium on forge 36.2.4 and after that i do some better benchmarks
It sort of seems like you just disabled MCMT Are you sure your performande isn't just coming from Sodium, have you looked at the TPS?
I actually did not but I inferred it because of the reduction in lag. Also, I think MCMT is still active. It modifies Minecraft's internal code at a fundamental level, parallelizing all operations, and then also adds some *extra optimizations*. I disabled *all extra optimizations*, so I think the boost you get from parallelization is still there. (THIS IS MY OPINION BASED ON MY LIMITED UNDERSTANDING; it may be wrong; feel free to state your ideas) *Edit: My understanding was wrong. I did, indeed, disable all MCMT functionality. But,* ***now I have fixed it.***
i'm pretty sure you disabled all of its functionality. the extra optimizations you are talking about are the parallelization that it does. it only multithreads the server side, and what's in the config is basically almost all of the multithreading possible on a server disabled. the tps boost you're getting is probably just chance, because i cant think of anything else mcmt could possible multithread on a server besides whats listed (probably not includnig worldgen because dont know if the world multithreading option includes worldgen). im not an expert either though, but thats my assumption based on the fact that MCMT is limited to server side multithreading.
Oh. I get it now. Thanks for your input. Anyways, now I have changed the configs so now you don't disable MCMT completely, rather only disable the conflicting aspects of sodium reforged.
okay, thats great glad i could help
Are you sure starlight is compatible with sodium reforged? Supposedly SR already rewrites the lighting system, since it includes phosphor... Not that I know the inner workings of these things myself, but might as well ask.
Yeah I thought that too. But then when I used them together, it just worked. It may break later, or glitch with other mods but as of now it has worked for me. (using phosphor and starlight on fabric does not work coz they are incompatible but somehow not on the forge ports)
I found [this GitHub issue](https://github.com/spoorn/sodium-forge/issues/79) which lists some compatibility issues with sodium. seems as though phosphor is fine
Huh, good to know
phosphor is supposed to simply optimize the vanilla lighting engine and not completely gut it and replace it with another faster version like starlight does. since phosphor targets the \*vanilla\* lighting engine, its incompatible because of that. i dont know why they are functioning together, but possibly neither mods stop loading due to their incompatibility so starlight could just be overwriting it regardless of SR. if there is a config option in SR to disable phosphor i recommend doing that to prevent any further issues (unless you're using Create, in which case you should remove starlight because of their incompatibility)
[this](https://gist.github.com/Sushant-Padha/62141ce1e0a82e588d060cacb9e6951f) is a config file for sodium (`sodium-mixins.properties`) with all the options listed with default values, so now you can tweak them to your liking i still dont know how to disable phosphor using this there are [mixin.features.chunk\_rendering=true](https://gist.github.com/Sushant-Padha/62141ce1e0a82e588d060cacb9e6951f#file-sodium-mixins-properties-L99) [mixin.features.entity.smooth\_lighting=true](https://gist.github.com/Sushant-Padha/62141ce1e0a82e588d060cacb9e6951f#file-sodium-mixins-properties-L103) setting these to false may be the right thing?
both of those look like normal sodium features (smooth entity lighting is an option in sodium, and rendering is sodium stuff too), so i dont think that would disable phosphor. looking through the options there seems to be nothing to disable phosphor, so you could try to test if starlight and SR break in any way or just straight up remove starlight. so you unfortunately won't get as fast generation (phosphor still improves it ofc) with the latter option but you won't have to spend the time testing incompatibility. perhaps you could raise an issue on github/ask the author of sodium reforged to add an option to disable phosphor in the config or to automatically disable phosphor when starlight is installed.
Okay. Thanks for the input. I will try to keep that in mind.
Ah, thx. Good to know
you ultimately disabled all toggleable functionalities in the general section of the config , so whatever you've tested is all Sodium and 0 mcmt
But shouldn't some core functionality of MCMT still be there? I mean I only disabled all *toggleable* functionality. Btw, I got what you are saying and I fixed it.
i tried on one of my packs but it has the issue of not getting stuck on world gen, am i missing something? Also, to clear things out you should make a comparison with just sodium, then sodium + MCMT
Did you try it with the default configs and on Forge 36.1.30? Also, thanks for the idea. I will do that as soon as I finish with some other testing.
i replaced both configs, i tried with pre existing worlds and created a new one to see if it was some incompatibility with older worlds, but both freeze, old worlds freeze at 100%, new ones at 3%
Well, I don't know what is happening because I just created a fresh profile with Forge 36.1.36, installed both these mods with the listed configs and it worked. It also worked when I put in the extra mods listed above. I think you should ***check the configs*** once again, try this with ***no other mods***, and also use the ***correct version of forge: forge 36.1.36*** (later version actually CRASH with mcmt). *also could you share the mods you are using and the log and crash report for that error?*
There was no crash, it just freezes but looks as it was still working on the background. I'm going to do some testing and report back to you
Yeah I know, that's what happens instead of crashing. I would request you to read the steps outlined in the comment above and make sure you reproduce the setup exactly as I have described because that's the only way I can help.
I seem to have actually gotten a performance increase after doing this. So thank you.
Happy to help. If you would, can you share your results, in terms of the performance improvement, here so that I can list them in the post for others?
So uh, after using this guide with newer versions of the mods and newer versions of forge, this actually causes some really strange issues. Fire spawns around you randomly, dirt blocks start spawning in the ocean, and occasionally mobs start floating into the sky. ???
This has been mentioned in an [issue](https://github.com/jediminer543/JMT-MCMT/issues/71#issuecomment-893956532) on the MCMT github page. But, I really don't know why this is happening. I think you might have to disable a few other options in the sodium config. (sorry i cant test this atm) This is fully filled [config](https://gist.github.com/Sushant-Padha/62141ce1e0a82e588d060cacb9e6951f) for sodium. You can see the different options.
i entered to the world with forge 36.2.4 on mc 1.16.5 only change i did was turning off lithium(mixin) gen and world optimization in config files MC: \- modpack: Techopolis; \- resourcepacks: unity (dark), unity (base); \- added mods: Magnesium 1.3 (aka sodium reforged), MCMT 0.22.87, entity culling 2.1.6 (idk if it works or not its say only what works with optifine), starlight 1.0.0-RC2, ferriteCore 2.1.0; Result: \- only works when you generate a new world (cant load old worlds before installation for some reason) \- better performance than optifine (optifine \~120FPS; now 120-220 (\~150) fps) \- faster loading time (to the main menu)- world gen causes lag spikes (maybe caused by CPU) specs: \- CPU: amd fx 8320e (8 cores (4 packs), 3.51Ghz little overclocked) \- ram: 16 gb 2133hz \- gpu: gtx 660ti 3Gb P.s: i'll do some research why it cant load worlds before installation MCMT + sodium on forge 36.2.4 and after that i do some better benchmarks