(second half of the title only because of the minimum of 15 characters)
From the main page:
Recently a lot of weird Bugs popped up with peoples Modpacks, like ForgeMultiPart crashing on startup, or FML Log Files flat out not existing. If you have one of these Issues, please tell me everything you know about it, because I want this bullshit to be fixed, and I cant replicate it to find a solution myself! Someones sloppy log4j fix is probably fucking up 1.7.10 and I need to find out why!
I’m not 100% sure on FML log files not existing, but the times I had that same report it was always on the Technic launcher. Checking a random Technic profile right now confirms that:
Multipart crashing IIRC was a somewhat common issue with Mekanism a few months back, either it was Mek conflicting with the current version of FMP or Mek actually needing it as a dependency now (some old forum posts would confirm that since the crash has been resolved multiple times simply by installing both FMP and CodeChickenCore). I don’t know what other mods may be involved with that but Mek has been present in every report I’ve gotten so far.
A different (and seemingly new) problem would be people’s graphics glitching out when holding any item or aiming at a mob (I suspect the GL12 lib that’s being used by the font renderer, my old laptop would render anything using GL12 in solid white).
Confirmed: Only happens on 1.7.10, even with no mods installed
Questionable: Whether it happens in vanilla 1.7.10 or if forge is required
Most but not all reports use integrated graphics, one supposed fix was to turn on dedicated graphics, another was apparently possible by downgrading GPU drivers. It’s impossible to replicate on any of my machines with a variety of settings and due to the diverse set of reports I can’t even make any proper guesses. Maybe it’s some specific launcher that ships with a broken version of the graphics library? The only launchers that I know where used were Curse and that weird russian cracked launcher.
Yet another issue (which is technically “intended behavior”) that I feel deserves more attention is Thermos’ ridiculous “optimization” feature that is enabled by default where tiles in chunks that have no players in them only tick once per second. Apparently nobody knows about this “optimization” setting or why it’s enabled for everything by default, but you can imagine what happens when peoples’ reactors tick 20 times a second while their water supply only does a single one.
Another classic problem (which was also recently solved in the forums), having a render distance above the maximum crashes the game instantly, it’s pretty common too when downgrading MC (only with terrible launchers that reuse the same folders for everything cough Microsoft) or uninstalling Optifine. It got so bad that I had to add my own render distance fixer into NTM, thankfully I haven’t gotten a single report since.
I hope this ramble has been vaguely helpful or topical (I don’t check the main page that often, the disclaimer could be a year old for all I know). Thank you for coming to my TED talk.
