Happy (early) Christmas!
Here's a new release of Immersive Engineering to tide you over the holiday time!
For 1.18.2:
https://t.co/qf79Qx1Ddc
For 1.19.2:
https://t.co/wwUiuDvZRv
(files still under review at the time of posting this)
…and fixed 1.16.5 builds:
https://t.co/H1a6OKUdUD
https://t.co/ElDsE0XzAR
On 1.17+ Fabric this was already fixed, so those versions did not get Fabric builds.
I've uploaded a FerriteCore build for 1.19.2 to fix the crash with the latest CF/MC launcher update:
https://t.co/ZuX8ITgSB6
https://t.co/3nYSC9myqQ
I'll fix earlier MC versions as well as soon as I get the build scripts to behave.
@BluSunrize@Rosespikes Lithium (and by extension Radium) are actually super powerful performance improvements (50% tick time reductions with RR in 1.16 IIRC). But porting Li to Forge is really tricky, and Ra has been taking far too many shortcuts. Even RR wasn't great, despite a lot of work from me.
@blacknight7890@BluSunrize Playing it safe and not bothering to look into it too much. Someone sent me the relevant guidelines from Mojang last night, I'll read through them later and discuss them with Blu.
Control Engineering is a new IE addon for MC 1.18.2 focussing on redstone control. The main features are control panels similar to those in Industrial Wires and logic cabinets, my own take on redstone logic in IEs style.
@McJty They work fine on their own, but try to call `Class#getMethod` on one of your block classes on a server. That will crash, and there are valid reasons for calling that. E.g. Chisels&Bits uses it to check if blocks have certain special behavior and should not be chiselable.
Immersive Engineering now has a beta release for 1.18.1!!!
https://t.co/pf7LOii8EX
Even though we've been testing it for a good few weeks now, this may still break things! If you find issues, please report them so we can fix it =)
FerriteCore beta for 1.18:
https://t.co/dprf2FpNcP
https://t.co/cdnEF9HDKi
A direct port for now, I will be looking into 1.18-specific optimizations soon
I think I delivered on that point: OBS used the worst microphone it could have used, and it was set to maximum amplification as well for some reason. I might try again today, if I have time for it.