I found a bug with the HD Font patcher, it causes the numbers in the server online count for the server list to be offset to the left of the 'ping' indicator of the server. This bug has been around for a while, and I'm not sure if it's been reported before. I didn't find it, or anywhere to report bugs for this, so, here we go.
I just downloaded the 2.4.3_04 version but it immediately disappeared when I tried to run it. Turns out that my antivirus software (Comodo 5.12.256249.2599) quarentined it thinking it is TrojWare.Win32.Kryptik.AOMB@288704486
I uploaded it to virustotal.com and had it scanned by 30+ virus scanners and only 2 of them found it suspicious so it seems this is a false positive.
I just downloaded the 2.4.3_04 version but it immediately disappeared when I tried to run it. Turns out that my antivirus software (Comodo 5.12.256249.2599) quarentined it thinking it is TrojWare.Win32.Kryptik.AOMB@288704486
I uploaded it to virustotal.com and had it scanned by 30+ virus scanners and only 2 of them found it suspicious so it seems this is a false positive.
LHammonds
this is common.... this thread gets spammed with "it's a virus" every single update.
Can you make the username be always the same. I don't care if it's "McPatcher," "Player," "Offline," or whatever. I just want it to be the same all the time.
Looks like compatibility with Forge needs to be worked on. I'm using recommended build 372 and when I load a texture pack x128 or larger FML is throwing an error on a texturefx size issue.
2012-11-16 10:15:29 [WARNING] [ForgeModLoader] A problem occurred with the watch texture: animation will be disabled
java.lang.ArrayIndexOutOfBoundsException: Coordinate out of bounds!
at sun.awt.image.ByteInterleavedRaster.getDataElements(Unknown Source)
at java.awt.image.BufferedImage.getRGB(Unknown Source)
at bct.setup(TextureWatchFX.java:51)
at cpw.mods.fml.client.FMLTextureFX.onTextureDimensionsUpdate(FMLTextureFX.java:56)
at cpw.mods.fml.client.TextureFXManager.setTextureDimensions(TextureFXManager.java:201)
at bap.a(RenderEngine.java:292)
at bap.b(RenderEngine.java:584)
at bef.a(SourceFile:143)
at aug.a(GuiSlot.java:249)
at bee.a(SourceFile:106)
at bac.b(EntityRenderer.java:977)
at net.minecraft.client.Minecraft.J(Minecraft.java:888)
at net.minecraft.client.Minecraft.run(Minecraft.java:783)
at java.lang.Thread.run(Unknown Source)
Oddly enough this does not happen with Optifine or if I keep to x64 or smaller texture sizes then I do not get the error with MCPatcher.
I do compile my own builds rather than downloading from here so if you commit a fix I can pull it and compile to test it but to make sure that my build wasn't somehow getting buggered I went and downloaded the one here and it did the same thing.
Could someone please explain to me exactly what MCPatcher is? The OP doesn't explain very well TBH. From what I understand, it is a compilation of a fews mods and a GUI that allows installing them a bit easier. It seems there used to be issues switching texture packs back in the day and this was a fix, but this is no longer the case.
How does this compare/relate to MagicLauncher?
Is this simply a modloader/Forge replacement or does it work with Forge?
So what's all the buzz about? I see this is a popular subject and I'm wondering if it could cut out some workf or me or help me out. I'd appreciate some elaboration on this!
Could someone please explain to me exactly what MCPatcher is? The OP doesn't explain very well TBH. From what I understand, it is a compilation of a fews mods and a GUI that allows installing them a bit easier. It seems there used to be issues switching texture packs back in the day and this was a fix, but this is no longer the case.
How does this compare/relate to MagicLauncher?
Is this simply a modloader/Forge replacement or does it work with Forge?
So what's all the buzz about? I see this is a popular subject and I'm wondering if it could cut out some workf or me or help me out. I'd appreciate some elaboration on this!
It is primarily a means to enable HD textures. The patcher patches up the jar and makes HD texture packs work in the game properly. The ability to install additional included mods is a bit of a side effect as they got merged into the application.
It is primarily a means to enable HD textures. The patcher patches up the jar and makes HD texture packs work in the game properly. The ability to install additional included mods is a bit of a side effect as they got merged into the application.
Thanks...Basically what I wanted to know. I also need to know if this is compatible with the Forge, Player/RenderPlayer/GUI API's, QuinOptions, Optifine, modloader mods, etc? Basically, should I just being using MC Patcher to install everything from Forge to Optifine, to the HD Textures enabler?
This would really clarify things for me. Thanks a bunch!
just an fyi in case anyone actually has an anwer after a week of trying this is the same error i get no matter how often i completely delete the entire minecraft folder and download minecraft again and this is the first and only mod or patch i apply to minecraft vanilla.
MCPatcher version is 2.4.3_04
OS: Windows 7 6.1 amd64
JVM: Oracle Corporation 1.7.0_09 (64 bit)
Classpath: C:\Users\-\Downloads\mcpatcher-2.4.3_04 (2).exe
Minecraft version is 1.4.4 (md5 7aa46c8058cba2f38e9d2ddddcc77c72)
Launching C:\Users\-\AppData\Roaming\.minecraft\bin\minecraft.jar
java -cp C:\Users\-\AppData\Roaming\.minecraft\bin/minecraft.jar;C:\Users\-\AppData\Roaming\.minecraft\bin/lwjgl.jar;C:\Users\-\AppData\Roaming\.minecraft\bin/lwjgl_util.jar;C:\Users\-\AppData\Roaming\.minecraft\bin/jinput.jar; -Djava.library.path=C:\Users\-\AppData\Roaming\.minecraft\bin\natives -Xmx2048M -Xms512M net.minecraft.client.Minecraft
Exception in thread "main" java.lang.NoClassDefFoundError: com/pclewis/mcpatcher/TexturePackAPI$ChangeHandler
at ll.b(SourceFile:164) [Potion]
at ll.<clinit>(SourceFile:17)
at vs.<clinit>(SourceFile:74)
at uk.<clinit>(SourceFile:131)
at amj.<clinit>(SourceFile:335)
at bdb.<init>(SourceFile:14)
at net.minecraft.client.Minecraft.<init>(SourceFile:126)
at asi.<init>(SourceFile:36)
at net.minecraft.client.MinecraftApplet.init(SourceFile:36)
at net.minecraft.client.Minecraft.main(SourceFile:1670)
Caused by: java.lang.ClassNotFoundException: com.pclewis.mcpatcher.TexturePackAPI$ChangeHandler
at java.net.URLClassLoader$1.run(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 10 more
Someone is closing me!
Minecraft exited with status 1
I managed to get mcpatcher-2.4.3_04.exe to work on 1.4.4. I basically ticked random mobs on it's own, pressed patch and Minecraft loaded up without 'blackscreening'. Quit the game, loaded the patcher back up again and then ticked HD Font, pressed patch and Minecraft loaded again successfully. I continued to tick each box one by one (apart from the Better Grass as I get the 'greysides' error when using other mods) and it works. I have no idea why this method works for me!
This worked for me also. Attempting to patch it all at once gave me a black screen, but one but at a time seemed to work.
Could someone please explain to me exactly what MCPatcher is? The OP doesn't explain very well TBH. From what I understand, it is a compilation of a fews mods and a GUI that allows installing them a bit easier. It seems there used to be issues switching texture packs back in the day and this was a fix, but this is no longer the case.
How does this compare/relate to MagicLauncher?
Is this simply a modloader/Forge replacement or does it work with Forge?
So what's all the buzz about? I see this is a popular subject and I'm wondering if it could cut out some workf or me or help me out. I'd appreciate some elaboration on this!
MCPatcher is a "patch" basically for high-definition texture packs (HD). The default texture pack is 16x, and there are many texture packs that have higher resolutions such as 32x, 64x, 128x, etc. Since the default is 16x, higher resolution texture packs don't work properly and glitches happen. (i.e portal blocks messing up, fire glitching) MCPatcher fixes those glitches so that HD texture packs work properly. However, the higher resolution texture pack you use, the lower your FPS is going to get.
Thanks...Basically what I wanted to know. I also need to know if this is compatible with the Forge, Player/RenderPlayer/GUI API's, QuinOptions, Optifine, modloader mods, etc? Basically, should I just being using MC Patcher to install everything from Forge to Optifine, to the HD Textures enabler?
This would really clarify things for me. Thanks a bunch!
I'm pretty sureit works with Forge and Modloader, but I'm not sure about the other ones. However it does not work with Optifine. Optifine is basically the same thing as MCPatcher, but with added options to increase game performance and FPS. Optifine is missing a few features of MCPatcher however. (I'm not sure what they are.)
I personally have never used MCPatcher to install mods, I install them manually. It's up to you, but I don't know whether it works with all mods. Just remember to never install Optifine and MCPatcher together, because they are not compatible and will give you a black screen. Also if you've decided to use Optifine instead of MCPatcher, install all your mods then install Optifine last. Otherwise it probably won't work.
Yeah, thanks, I just found that out today watching a Kurtjmac video and he was having the same problem.
D_B
To tell them how to live is to prevent them living.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI uploaded it to virustotal.com and had it scanned by 30+ virus scanners and only 2 of them found it suspicious so it seems this is a false positive.
LHammonds
Minecraft Server: HammondsLegacy.com
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumthis is common.... this thread gets spammed with "it's a virus" every single update.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumtouchblock=blockID
touchtile=tileID
connectoverlay=source
tiles=4543
so, the CTM, repeat stuff goes first then the 'connect' overlay goes after.
So if there is CTM for stone, it would render that first then render the 'connect' overlay.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumOddly enough this does not happen with Optifine or if I keep to x64 or smaller texture sizes then I do not get the error with MCPatcher.
I do compile my own builds rather than downloading from here so if you commit a fix I can pull it and compile to test it but to make sure that my build wasn't somehow getting buggered I went and downloaded the one here and it did the same thing.
How does this compare/relate to MagicLauncher?
Is this simply a modloader/Forge replacement or does it work with Forge?
So what's all the buzz about? I see this is a popular subject and I'm wondering if it could cut out some workf or me or help me out. I'd appreciate some elaboration on this!
It is primarily a means to enable HD textures. The patcher patches up the jar and makes HD texture packs work in the game properly. The ability to install additional included mods is a bit of a side effect as they got merged into the application.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumyou know...most of the time the core patcher doesn't actually need updating right? been that way for a long time now.
Thanks...Basically what I wanted to know. I also need to know if this is compatible with the Forge, Player/RenderPlayer/GUI API's, QuinOptions, Optifine, modloader mods, etc? Basically, should I just being using MC Patcher to install everything from Forge to Optifine, to the HD Textures enabler?
This would really clarify things for me. Thanks a bunch!
This worked for me also. Attempting to patch it all at once gave me a black screen, but one but at a time seemed to work.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumMCPatcher is a "patch" basically for high-definition texture packs (HD). The default texture pack is 16x, and there are many texture packs that have higher resolutions such as 32x, 64x, 128x, etc. Since the default is 16x, higher resolution texture packs don't work properly and glitches happen. (i.e portal blocks messing up, fire glitching) MCPatcher fixes those glitches so that HD texture packs work properly. However, the higher resolution texture pack you use, the lower your FPS is going to get.
I'm pretty sure it works with Forge and Modloader, but I'm not sure about the other ones. However it does not work with Optifine. Optifine is basically the same thing as MCPatcher, but with added options to increase game performance and FPS. Optifine is missing a few features of MCPatcher however. (I'm not sure what they are.)
I personally have never used MCPatcher to install mods, I install them manually. It's up to you, but I don't know whether it works with all mods. Just remember to never install Optifine and MCPatcher together, because they are not compatible and will give you a black screen. Also if you've decided to use Optifine instead of MCPatcher, install all your mods then install Optifine last. Otherwise it probably won't work.