By now we've all gotten used to the cycle of Mojang getting distracted from bugfixes to play with a shiny new toy, but they really raised the bar this time. What exactly was the thought process here?
From a business standpoint, twitch.tv obviously benefits, but what does Mojang get out of it? Is a little ad revenue worth tying their flagship game and their players to another company?
On the technical side, why make your game dependent on a third-party feature that 99% of players will never use? Some players can't even start the snapshots because the twitch library is missing or crashing. And the timing. They delay a much-needed 1.7.3 to cram in a major new third-party library dependency. One that by necessity must hook fairly deeply into the rendering code. Is it any surprise that we're already up to 13w47e?
Even the players who do want to stream won't necessarily want to be locked into one streaming service. And presumably the dedicated LPers will continue to post pre-recorded and edited videos, so again I ask, what is the point of this?
-
- Kahr
- Registered Member
-
Member for 13 years, 5 months, and 5 days
Last active Fri, Jun, 5 2015 09:57:53
- 13 Followers
- 355 Total Posts
- 1437 Thanks
0
I've updated the patcher to 2.1.1_01 and fixed the bug with ModLoader. See OP for details.
0
I'm not having any problems with LB Photo Realism x128 6.5.0 or LB Photo Realism x256 6.5.0. Does changing the Java heap size (Options tab) make any difference? Are there any errors in the log window?
0
My guess is you have an incompatible mod loaded somehow. Remove all mods from the list except HD textures/fonts and Better Grass, delete minecraft-1.8.1.jar, force update the game, and repatch.
Good to know, thanks. As a happy side effect, this clears up the 1.8 preview vs. final minecraft.jar confusion once and for all. I wonder what the "final" 1.8 version number will eventually be.
0
Offhand, I'd say one of foliagecolor.png, grasscolor.png, or watercolor.png are the wrong size. They must be 256x256. If that's not it, send me a link to your texture pack and I'll try to figure it out.
I'm not a Mac user, so I don't know the details, but the same basic idea should work. Extract mcpatcher-2.1.1.jar to a folder and open a Terminal window. In that window cd into the directory you extracted it to and run the command
Maybe a Mac user can give better instructions.
0
Hm, I don't know where else it could be getting it from then. What OS are you using? Try searching your computer for minecraft*.jar and seeing if any other files pop up.
0
Yep, ModLoader changes qo.class just enough to prevent one of the needed patches from working. I should be able to come up with a fix, but in the meantime disable Better Grass.
The blue text in the OP tells you exactly what to do. Delete minecraft-1.8.jar from .minecraft/bin, force update the game using the launcher, then re-patch.
This one seems to work with 1.8 final, but I'll keep an eye out for bug reports and put out an update if needed.
0
Yes, it's downgrading to the 1.8 preview. This is because Mojang used the same version number for both preview and final. It's easy enough to fix, see the instructions in blue at the top of the OP.
0
You'll need to do this for any future "1.8" release (preview or final).
EDIT: Clarified
0
0
That sounds familiar, but I think I fixed that bug a while back. I remember tightening that class signature specifically, and, to be extra sure, restricting the matching algorithm to class files with all lowercase names.
facepalm
The reason I ask for specifics is because I tried installing zombe's mod myself using the patcher and didn't notice any obvious problems. Does it fail to patch? Does it patch but the game fails to launch? Does the game launch but some of the mod's features don't work? Do hordes of carnivorous pink bunnies burst forth from your PC and devour your pets?
This is a bug that will be fixed in the next release. In the meantime, deleting the file called "md5s" in the .minecraft/bin folder should fix the problem. This may cause the launcher to redownload the game next time, so copy back the 1.8 minecraft.jar if it does.
Hopefully this evening. I considered including idshift's patch for the furnace crash, but Jeb said on Twitter that the bug will be fixed in an updated pre-release tomorrow anyway.
0
Could either of you be more specific...?
0
Wait, what's wrong with silverfish? I tried a couple different packs and they seem ok. Did I miss something obvious?
0
The patcher has a problem with ! in paths, a bug I plan to fix in the next release. In the meantime move the mcpatcher exe to a different folder, and it should work.
0
That is strange. I'll look into it.
EDIT: The white spider bug happens even without the patcher. I created a texture pack containing only mob/spider_eyes.png, unpatched, and still had the problem.
The culprit is this change to the spider class:
1.7.3 (yx.class):
protected boolean a(cn, int, float) { ... glBlendFunc(770 /* GL_SRC_ALPHA */, 771 /* GL_ONE_MINUS_SRC_ALPHA */); ... }And the same method in 1.8 (aeb.class):
protected boolean a(bh, int, float) { ... glBlendFunc(1 /* GL_ONE */, 1 /* GL_ONE */); ... }I created a patch to restore the old glBlendFunc call, and it seems to work, but I don't understand why Jeb changed it.
0
Haven't seen anything like that. What texture pack is it and what are your system specs?
Sounds like a problem with your Java installation. Do you have the same problem with both the .exe and .jar versions? Try uninstalling all versions of Java and installing the 64-bit version from here.
You probably had TMI installed the first time you ran the patcher. In your .minecraft/bin folder, delete the both minecraft.jar and minecraft-1.7.3.jar, then redownload using the game's launcher.