I'm not sure exactly what you're asking, but if the NPC Mod uses forge, then there's no way around needing forge to run it. That said, MCPatcher generally works fine with forge as long as you load it with MCPatcher. Start from a fresh minecraft.jar, click the Add (+) button and select the minecraftforge-universal-<version>.zip. Add any other zip-based mods (TMI, etc.) the same way.
As for the forge team's rudeness, they pretty much treat anyone who refuses to play in their sandbox that way. Frankly, I consider it a badge of honor.
Thank you for answering me politely! I swear even the mods here started getting up my butt about things and its really kind of depressing when you see an entire community of people steam-roll over you for trying to put out personal experiences so others can semi-understand a situation ahhaa. I've tried to use Forge in MCPatcher many times and it never seems to work - something about the guy/team who made Forge simply hated the MCPatcher stuff and said it was nothing but stolen code and the people were money hungry "Jews" and it was just rude wrong nasty and bleh....
Right now I can't even get MCPatcher to work anyway so I can't use Texture Packs, Mods, nothing until it gets fixed. I mean I could I suppose if I installed things like Optifine etc but meh I'd rather wait for MCPatcher to come out during the 2.5.2 (1.5.2 but technically it's not that) or the 2.6 update (whenever that is).
SO in short..
- Do you know a way / can you confirm Forge working with MCPatcher? It never has for many people and it was a huge issue.
- Is MCPatcher working at all for anyone else in 1.5.2 or is it constantly crashing upon start up for them like it is me?
i have installed the mc patcher software for minecraft 1.5.2 and tried to patch it. it said that it did it successfully, but I still cant get HD textures. When patching, I checked all the boxes but changed nothing else. The texture pack shows up in the folder and I have no mods installed. Please help!
I'm not sure exactly what you're asking, but if the NPC Mod uses forge, then there's no way around needing forge to run it. That said, MCPatcher generally works fine with forge as long as you load it with MCPatcher. Start from a fresh minecraft.jar, click the Add (+) button and select the minecraftforge-universal-<version>.zip. Add any other zip-based mods (TMI, etc.) the same way.
As for the forge team's rudeness, they pretty much treat anyone who refuses to play in their sandbox that way. Frankly, I consider it a badge of honor.
I had an issue patching with Forge on 1.5.2. I used to do it like you described above with no problems but now there are conflicts between internal mods in MCPatcher (__Base and __TexturePackBase) that conflict with Forge. I can still patch and play the game but there are visual bugs. Any insight to this conflict?
When I try and patch my Mega Doku texture pack minecraft will not start and an error pops up. If i unpatch the pack Minecraft runs perfectly, is anyone else experiencing this problem
I don't know if anyone else has actually noticed or had this issue in particular because from what i've seen so far, nobody has.
My issue is with the randomized mobs. It works fine of course, but there is one thing that doesn't work as it use to before 1.5, which is randomized character skins. Basically my texturepack has an abundant amount of substitutes for steve skins so when your spawn in and have no skin, it'll select it from the list, but now it only selects the base char.png one and not the char2.png or any other.
This is also an issue because it does not randomize skins for my server plugin [Citizens] which I use to enjoy but not anymore.
I could use some help for this which would be very much appreciated. (this may possibly be a bug that could be fixed although I have no idea)
Hello people, anyone got mc crash with mcpatcher 3.04 and some texture pack hd?
eg: KDS realistic hd with mcpatcher .jar mc crash and without mcpatcher that work :|
I hope someone can help me.
To be sure everything worked fine, I deleted my .Minecraft map and redownloaded minecraft.
But after using the patcher (3.0.3 I left everything on default) my minecraft crashes with this log:
Minecraft has crashed!
----------------------
Minecraft has stopped running because it encountered a problem; Unexpected error
A full error report has been saved to C:\Users\Allard\AppData\Roaming\.minecraft\crash-reports\crash-2013-05-11_18.34.30-client.txt - Please include a copy of that file (Not this screen!) if you report this crash to anyone; without it, they will not be able to help fix the crash
--- BEGIN ERROR REPORT ac7aa50f --------
Full report at:
C:\Users\Allard\AppData\Roaming\.minecraft\crash-reports\crash-2013-05-11_18.34.30-client.txt
Please show that file to Mojang, NOT just this screen!
Generated 11-5-13 18:34
-- System Details --
Details:
Minecraft Version: 1.5.2
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.7.0_13, Oracle Corporation
Java VM Version: Java HotSpot™ 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 455048216 bytes (433 MB) / 514523136 bytes (490 MB) up to 954466304 bytes (910 MB)
JVM Flags: 2 total; -Xmx1024M -Xms512M
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: [com.prupe.mcpatcher.MCPatcherUtils, Config, MCLogger, ...], [com.prupe.mcpatcher.mod.ColorizeItem, AAHelper, TessellatorUtils, ...]
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
LWJGL: 2.4.2
OpenGL: GeForce GTX 260/PCIe/SSE2 GL version 3.3.0, NVIDIA Corporation
Is Modded: Very likely; Jar signature invalidated
Type: Client (map_client.txt)
Texture Pack: Default
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
java.lang.IllegalArgumentException: ByteBuffer is not direct
at org.lwjgl.BufferChecks.checkDirect(BufferChecks.java:105)
at org.lwjgl.BufferChecks.checkBuffer(BufferChecks.java:164)
at org.lwjgl.opengl.GL11.glTexSubImage2D(GL11.java:2908)
at bio.b(SourceFile:333)
at bil.l(SourceFile:148)
at bir.c(SourceFile:166)
at bge.b(SourceFile:294)
at net.minecraft.client.Minecraft.l(SourceFile:1060)
at net.minecraft.client.Minecraft.K(SourceFile:574)
at net.minecraft.client.Minecraft.run(SourceFile:526)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT ae9e86f0 ----------
Crashlog from AppData\Roaming\.minecraft\crash-reports\crash-2013-05-11_18.34.30-client.txt
---- Minecraft Crash Report ----
// Oh - I know what I did wrong!
Time: 11-5-13 18:34
Description: Unexpected error
java.lang.IllegalArgumentException: ByteBuffer is not direct
at org.lwjgl.BufferChecks.checkDirect(BufferChecks.java:105)
at org.lwjgl.BufferChecks.checkBuffer(BufferChecks.java:164)
at org.lwjgl.opengl.GL11.glTexSubImage2D(GL11.java:2908)
at bio.b(SourceFile:333)
at bil.l(SourceFile:148)
at bir.c(SourceFile:166)
at bge.b(SourceFile:294)
at net.minecraft.client.Minecraft.l(SourceFile:1060)
at net.minecraft.client.Minecraft.K(SourceFile:574)
at net.minecraft.client.Minecraft.run(SourceFile:526)
at java.lang.Thread.run(Unknown Source)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- System Details --
Details:
Minecraft Version: 1.5.2
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.7.0_13, Oracle Corporation
Java VM Version: Java HotSpot™ 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 455048216 bytes (433 MB) / 514523136 bytes (490 MB) up to 954466304 bytes (910 MB)
JVM Flags: 2 total; -Xmx1024M -Xms512M
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: [com.prupe.mcpatcher.MCPatcherUtils, Config, MCLogger, ...], [com.prupe.mcpatcher.mod.ColorizeItem, AAHelper, TessellatorUtils, ...]
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
LWJGL: 2.4.2
OpenGL: GeForce GTX 260/PCIe/SSE2 GL version 3.3.0, NVIDIA Corporation
Is Modded: Very likely; Jar signature invalidated
Type: Client (map_client.txt)
Texture Pack: Default
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
What did I do wrong? Thank you for taking your time to read all of this :S
Hello people, anyone got mc crash with mcpatcher 3.04 and some texture pack hd when connect to serv.?
eg: KDS realistic hd with mcpatcher .jar mc crash and without mcpatcher that work :|
I think there's a problem with doors and connected textures method=horizontal.
They seem a bit mixed up.
I'm not sure how to proceed with them.
The left door only has the correct connected texture when the right door is open.
The right door, closed or open, is always using the non-connected textures in textures\blocks.
Firstly, for that block, I think you need to put a matchBlocks and not a matchTiles with metadata definition
For that, you should look for these values on the wiki that I have shortened here : minecraftwiki.net : Data Values - Door
Normally you should do these properties files and it should works, I haven't tested, I'm not at home, so don't blame me:
If you want to aim to the iron door, simply match 71 instead of 64
Connected doors still don't work properly, even when using matchBlocks instead of matchTiles.
Using your properties, when both doors are closed...
- the bottom halves are using the correct connected textures
- both top halves are using the single door texture from the connected textures
When either or both doors are open...
- both doors (upper and lower) are using the single door texture from the connected textures
Currently, it looks like connected textures (horizontal) don't work properly with MCPatcher.
It took a while to get something stable enough for release, but here's MCPatcher 4.0.0 beta (exe) for 13w19a. Mojang's changes to the texturing code necessitated yet another break in backward compatibility; hence the jump to the next major version. This also means it works with the new launcher only. CIT and two new CTM methods are still works in progress.
Hey Kahr, I have a few questions:
1: I've been having some troubles with CTM. Are horizontal methods not supposed to work on the top of blocks? I've been trying to get some horizontally connected planks going for my pack, only to find that the CTM rules have no effect on the top face of the block!
2: Is there any way to disable anisotropic filtering in the patcher options? It doesn't seem to do that much good, and produces a bunch of strange visual artifacts to boot...
It took a while to get something stable enough for release, but here's MCPatcher 4.0.0 beta for 13w19a. Mojang's changes to the texturing code necessitated yet another break in backward compatibility; hence the jump to the next major version. This also means it works with the new launcher only. CIT and two new CTM methods are still works in progress.
So how will this whole "custom item textures" thing work? what will it let us do?
1: I've been having some troubles with CTM. Are horizontal methods not supposed to work on the top of blocks? I've been trying to get some horizontally connected planks going for my pack, only to find that the CTM rules have no effect on the top face of the block!
No, because there's no inherent "left" or "right" relative to the top/bottom faces. Horizontal CTM would arbitrarily work only in the north-south or east-west direction, which probably isn't what you want.
The good news is that I'm adding two new CTM methods that will address this better. Something in between horizontal&vertical and full 8-way CTM.
2: Is there any way to disable anisotropic filtering in the patcher options? It doesn't seem to do that much good, and produces a bunch of strange visual artifacts to boot...
When I enable anti-aliasing through Extended HD, any block that I work on lights up and flickers.
The option is right there under Extended HD. I'm afraid there's not much I can do about the artifacts as they're likely video driver-related. Mipmapping is more important for overall visual quality and tends to have fewer compatibility problems.
So how will this whole "custom item textures" thing work? what will it let us do?
It will do for items what CTM did for blocks. Along with different textures based on damage values and NBT data, there will be custom enchantment effects and armor textures. I haven't published the .properties file format yet because it is still changing (plus the new launcher + 1.6 interrupted development), but some people have already figured out how it works and have been playing around with it.
Well if CTM was really that broken I never would have released it. Can you give more specifics? What texture pack? Folder or zip? Do all packs do this or just some? What OS?
I'm afraid there's not much I can do about the artifacts as they're likely video driver-related.
Alrighty. I was afraid it was a possibility. I understand that anti-aliasing isn't supported natively by Minecraft, but I have no idea why the driver's anti-aliasing implementation would cause lighting peculiarities only in Minecraft.
Thank you for answering me politely! I swear even the mods here started getting up my butt about things and its really kind of depressing when you see an entire community of people steam-roll over you for trying to put out personal experiences so others can semi-understand a situation ahhaa. I've tried to use Forge in MCPatcher many times and it never seems to work - something about the guy/team who made Forge simply hated the MCPatcher stuff and said it was nothing but stolen code and the people were money hungry "Jews" and it was just rude wrong nasty and bleh....
Right now I can't even get MCPatcher to work anyway so I can't use Texture Packs, Mods, nothing until it gets fixed. I mean I could I suppose if I installed things like Optifine etc but meh I'd rather wait for MCPatcher to come out during the 2.5.2 (1.5.2 but technically it's not that) or the 2.6 update (whenever that is).
SO in short..
- Do you know a way / can you confirm Forge working with MCPatcher? It never has for many people and it was a huge issue.
- Is MCPatcher working at all for anyone else in 1.5.2 or is it constantly crashing upon start up for them like it is me?
I had an issue patching with Forge on 1.5.2. I used to do it like you described above with no problems but now there are conflicts between internal mods in MCPatcher (__Base and __TexturePackBase) that conflict with Forge. I can still patch and play the game but there are visual bugs. Any insight to this conflict?
My issue is with the randomized mobs. It works fine of course, but there is one thing that doesn't work as it use to before 1.5, which is randomized character skins. Basically my texturepack has an abundant amount of substitutes for steve skins so when your spawn in and have no skin, it'll select it from the list, but now it only selects the base char.png one and not the char2.png or any other.
This is also an issue because it does not randomize skins for my server plugin [Citizens] which I use to enjoy but not anymore.
I could use some help for this which would be very much appreciated. (this may possibly be a bug that could be fixed although I have no idea)
User: GOODBYE.
Cleverbot: Tool.
User: What did you call me you piece of ****?
Cleverbot: I called you cheese.
User: Oh.
Cleverbot: Love You.
User: I... Love you too..
eg: KDS realistic hd with mcpatcher .jar mc crash and without mcpatcher that work :|
better than this:
To be sure everything worked fine, I deleted my .Minecraft map and redownloaded minecraft.
But after using the patcher (3.0.3 I left everything on default) my minecraft crashes with this log:
Minecraft has crashed!
----------------------
Minecraft has stopped running because it encountered a problem; Unexpected error
A full error report has been saved to C:\Users\Allard\AppData\Roaming\.minecraft\crash-reports\crash-2013-05-11_18.34.30-client.txt - Please include a copy of that file (Not this screen!) if you report this crash to anyone; without it, they will not be able to help fix the crash
--- BEGIN ERROR REPORT ac7aa50f --------
Full report at:
C:\Users\Allard\AppData\Roaming\.minecraft\crash-reports\crash-2013-05-11_18.34.30-client.txt
Please show that file to Mojang, NOT just this screen!
Generated 11-5-13 18:34
-- System Details --
Details:
Minecraft Version: 1.5.2
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.7.0_13, Oracle Corporation
Java VM Version: Java HotSpot™ 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 455048216 bytes (433 MB) / 514523136 bytes (490 MB) up to 954466304 bytes (910 MB)
JVM Flags: 2 total; -Xmx1024M -Xms512M
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: [com.prupe.mcpatcher.MCPatcherUtils, Config, MCLogger, ...], [com.prupe.mcpatcher.mod.ColorizeItem, AAHelper, TessellatorUtils, ...]
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
LWJGL: 2.4.2
OpenGL: GeForce GTX 260/PCIe/SSE2 GL version 3.3.0, NVIDIA Corporation
Is Modded: Very likely; Jar signature invalidated
Type: Client (map_client.txt)
Texture Pack: Default
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
java.lang.IllegalArgumentException: ByteBuffer is not direct
at org.lwjgl.BufferChecks.checkDirect(BufferChecks.java:105)
at org.lwjgl.BufferChecks.checkBuffer(BufferChecks.java:164)
at org.lwjgl.opengl.GL11.glTexSubImage2D(GL11.java:2908)
at bio.b(SourceFile:333)
at bil.l(SourceFile:148)
at bir.c(SourceFile:166)
at bge.b(SourceFile:294)
at net.minecraft.client.Minecraft.l(SourceFile:1060)
at net.minecraft.client.Minecraft.K(SourceFile:574)
at net.minecraft.client.Minecraft.run(SourceFile:526)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT ae9e86f0 ----------
Crashlog from AppData\Roaming\.minecraft\crash-reports\crash-2013-05-11_18.34.30-client.txt
---- Minecraft Crash Report ----
// Oh - I know what I did wrong!
Time: 11-5-13 18:34
Description: Unexpected error
java.lang.IllegalArgumentException: ByteBuffer is not direct
at org.lwjgl.BufferChecks.checkDirect(BufferChecks.java:105)
at org.lwjgl.BufferChecks.checkBuffer(BufferChecks.java:164)
at org.lwjgl.opengl.GL11.glTexSubImage2D(GL11.java:2908)
at bio.b(SourceFile:333)
at bil.l(SourceFile:148)
at bir.c(SourceFile:166)
at bge.b(SourceFile:294)
at net.minecraft.client.Minecraft.l(SourceFile:1060)
at net.minecraft.client.Minecraft.K(SourceFile:574)
at net.minecraft.client.Minecraft.run(SourceFile:526)
at java.lang.Thread.run(Unknown Source)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- System Details --
Details:
Minecraft Version: 1.5.2
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.7.0_13, Oracle Corporation
Java VM Version: Java HotSpot™ 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 455048216 bytes (433 MB) / 514523136 bytes (490 MB) up to 954466304 bytes (910 MB)
JVM Flags: 2 total; -Xmx1024M -Xms512M
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: [com.prupe.mcpatcher.MCPatcherUtils, Config, MCLogger, ...], [com.prupe.mcpatcher.mod.ColorizeItem, AAHelper, TessellatorUtils, ...]
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
LWJGL: 2.4.2
OpenGL: GeForce GTX 260/PCIe/SSE2 GL version 3.3.0, NVIDIA Corporation
Is Modded: Very likely; Jar signature invalidated
Type: Client (map_client.txt)
Texture Pack: Default
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
What did I do wrong? Thank you for taking your time to read all of this :S
up please :|
Connected doors still don't work properly, even when using matchBlocks instead of matchTiles.
Using your properties, when both doors are closed...
- the bottom halves are using the correct connected textures
- both top halves are using the single door texture from the connected textures
When either or both doors are open...
- both doors (upper and lower) are using the single door texture from the connected textures
Currently, it looks like connected textures (horizontal) don't work properly with MCPatcher.
@Kahr: is this something that you can fix?
Game designer, forum stalker.
Edit: exe version.
1: I've been having some troubles with CTM. Are horizontal methods not supposed to work on the top of blocks? I've been trying to get some horizontally connected planks going for my pack, only to find that the CTM rules have no effect on the top face of the block!
2: Is there any way to disable anisotropic filtering in the patcher options? It doesn't seem to do that much good, and produces a bunch of strange visual artifacts to boot...
When I enable anti-aliasing through Extended HD, any block that I work on lights up and flickers.
I'm not using any mods besides MCPatcher, and I have the default texture pack.
I reported this bug in an earlier version of MCPatcher and Minecraft.
So how will this whole "custom item textures" thing work? what will it let us do?
No, because there's no inherent "left" or "right" relative to the top/bottom faces. Horizontal CTM would arbitrarily work only in the north-south or east-west direction, which probably isn't what you want.
The good news is that I'm adding two new CTM methods that will address this better. Something in between horizontal&vertical and full 8-way CTM.
The option is right there under Extended HD. I'm afraid there's not much I can do about the artifacts as they're likely video driver-related. Mipmapping is more important for overall visual quality and tends to have fewer compatibility problems.
It will do for items what CTM did for blocks. Along with different textures based on damage values and NBT data, there will be custom enchantment effects and armor textures. I haven't published the .properties file format yet because it is still changing (plus the new launcher + 1.6 interrupted development), but some people have already figured out how it works and have been playing around with it.
Well if CTM was really that broken I never would have released it. Can you give more specifics? What texture pack? Folder or zip? Do all packs do this or just some? What OS?
Here you go. By the way, I use 64-bit Java too and have no problems launching jar files directly. You may just need to reinstall Java.
Alrighty. I was afraid it was a possibility. I understand that anti-aliasing isn't supported natively by Minecraft, but I have no idea why the driver's anti-aliasing implementation would cause lighting peculiarities only in Minecraft.
Thanks for the reply and for updating.
Couldn't see it on the main page where it was before.