Loaded up the 1.9 snapshot, and unfortunately the same significant bugs that were in 1.8 snapshots still exist. Why do I get the feeling that these will make it into 1.9 release as well?
Recent Events Discussion (RED) Thread
- Thread starter VapourDrive
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
They're on the bug tracker, I don't really know what more you can do than that without seeming like a pest. Besides, if they run the game at all then they know that these are issues.
Meanwhile, I "melted" 1.9 (what I call renaming all the snowmen characters in the local variable tables that they started leaving mid-1.8), gave it generic class names, and tried to decompile it. The resulting source code is really broken. This is the same version of Fernflower that I modified for FMC with 1.8 (my MCP alternative) that worked remarkably well. I even tried the version that comes with MCP, which is older but with many of its own custom patches, and it made no difference. Don't get me wrong, it's not really Mojang's fault, but it's certainly disappointing. Might be time to find a different decompiler.
EDIT: Looks like a lot of it is related to inner classes being referred to as their parent class.
Last edited:
Actually Mojang revealed the path blocks around the same time as Vazkii showed off the ones in Botania. And the beetroot was originally from the Pocket Edition.
Correct me if I am wrong but I think Vazkii got the idea from the 1.9 sneak peaks
https://www.reddit.com/r/Minecraft/comments/2sqwu6/i_made_a_road_simple_yet_so_much_nicer_than/
Took me a minute to find it. Like most Mojang content, it's blatantly community originated/directed. Horses, Pistons, Path Blocks, Hoppers... *sigh*
It's why I'm happy that Fyber is making "bring all the mods to 1.7" mods, and Gany (and others) are making "bring all the features from 1.8+ to 1.7" mods. We might finally have a stable version, Forge just has to stop supporting 1.8 so we can quit explaining this to all the new modders that are like "But mods are updating to 1.8!"
Took me a minute to find it. Like most Mojang content, it's blatantly community originated/directed. Horses, Pistons, Path Blocks, Hoppers... *sigh*
It's why I'm happy that Fyber is making "bring all the mods to 1.7" mods, and Gany (and others) are making "bring all the features from 1.8+ to 1.7" mods. We might finally have a stable version, Forge just has to stop supporting 1.8 so we can quit explaining this to all the new modders that are like "But mods are updating to 1.8!"
"Just". Lex will have other ideas. Like completely opposite ideas.
Hey, just because it's simple and easy doesn't mean it's going to be likely. *sigh* I was really hoping that Minecraft Forkage was actually going to be a thing.
Barring the easy solution, we just need to keep the major mods off 1.8... so far we've only really lost TC5, so that front is relatively secure at least with the sheer number of coders that are giving 1.8 the giant middle finger.
Barring the easy solution, we just need to keep the major mods off 1.8... so far we've only really lost TC5, so that front is relatively secure at least with the sheer number of coders that are giving 1.8 the giant middle finger.
Celestialphoenix
Too Much Free Time
Same here.
Though if the entire community moved, there'll probably be several fixes floating around before long.
I fixed that physics crap a while back because it drives me crazy. This is compatible with Forge. The caveat is that it exaggerates another bug that makes mobs sink into blocks in certain situations, now going half-way down into'em instead of just hiding their shadows. But I can live with that.
There's also a version for Meddle now that works on any version of 1.8 and all of the 1.9 snapshots so far.
There's also a version for Meddle now that works on any version of 1.8 and all of the 1.9 snapshots so far.
If I remember correctly, they switch the physic calculation from client-side to server-side and the delay between them is what caused the floatiness. I'm guessing they felt that the server should be the one that does the number-crunching while the client just handle the renderings.
Mob physics have always been kinda bugged...I guess everyone has seen these client-side glitches: When you have lots of mobs in a tight space (e.g. at the bottom of a mob farm) they occasionally appear to escape the confinement. Or when a mob or item is close to a ledge it looks like it would fall down and you can't hit it or pick it up. Or climbing spiders that appear at the wrong vertical position.
I wonder if that was a hasty attempt to fix these
I wonder if that was a hasty attempt to fix these
Last edited:
1.8 still has some really bad collision detection despite their attempt to put movement server-side only. I saw a Youtube video before where someone hit a mob clear through the floor when they had strong-enough knockback on their weapon. Probably happened when the bug where they sink partially into the floor was occurring.
The networking code just isn't good enough for everything to be server-side. You get the delay of the packet being processed probably on the next tick, then you get literally 3+ more ticks of movement smoothing. If you remove the smoothing then it's just all herky-jerky. In 1.7 and earlier it wasn't perfect either, since network packets coming in still affected the motion and gave a subtle stutter sometimes (which you can also see with my 1.8 patch). But I'll take that any day. I'll even take the glitching out of items on edges and spiders (which is probably due to floating point inaccuracies between the client and server).
It's fine x3 I like the new name better anyway, plus it suites your mod better.I'm sorry.