Minecraft Forums

Glad to see MCPatcher 4.3.0 is out, even though it still needs some work I am glad it is getting updated. I don't know if anybody else is seeing what I see but the mods still don't work (I use Sphax PureBD) and none of MCPatcher mods are working. I can select them but they don't work. Hope it's not just me ....

Quote from katCrusader

...things I've noticed lol.
1, The north and east faces of CTM glass blocks have their left and right borders swapped.
...

I've noticed this on any repeated connected textures, as well.
The texture on each block is mirrored on the North and East facing sides.
Using the latest MCPatcher.

Quote from ozBillo

I've noticed this on any repeated connected textures, as well.
The texture on each block is mirrored on the North and East facing sides.
Using the latest MCPatcher.

That's https://mojang.atlassian.net/browse/MC-37106 , will be fixed in the upcoming Minecraft 1.7.3

Quote from eleazzaar

Some of my CTM for stone brick is behaving differently for in the latest MCPatcher. Now it is applying itself to quartz slabs, but only for a single quartz slab in the upper position. I'm at a loss trying to figure out what's going on-- everything else seems to work as expected, and as it did in 1.6.x. My experimental cobble CTM also applies itself to the same quartz slabs.

File: block44side.properties

# Stonebrick Slab
metadata=5 13
method=fixed
faces=east west north south
tiles=sb_slabside

File: block44top.properties

# Stonebrick Slab
metadata=5 13
method=fixed
faces=top bottom
tiles=sb_top

You can also see the glitch in action in my pack (click my sig). Does this make sense to anybody?

It's a bug in mcpatcher with metadata of 15. Apparently its fixed in the next release, along with the custom biome colors bug.

So is anyone else not happy with Mojang's "fix" for not being able to see the water surface from underwater? (See MC-34751)

Quote from Killjoy1221

Hey, Kahr, I'm using mcpatcher 4.3.0 on 1.6.4 and I'm crashing while using Zan's Minimap on multiplayer.

This is surprisingly complicated to fix, but I may have something that will work.

Yeaah, the fix is kind of ugly. Good for still water, yeah, but flowing water looks buggy with just the top part rendering. I liked how it was in 1.6.4 since the water flowing water texture helps give it the look that you're behind water and it's cascading around you. With 1.7.2 and the "fixed" version, it really doesn't look right at all. I guess it ~might~ look better if some sort of falloff was applied to the surface when the water's flowing, but I don't know if that'd be possible.

Quote from Kahr

So is anyone else not happy with Mojang's "fix" for not being able to see the water surface from underwater? (See MC-34751)

Looks like quality work from our professional bandaiders over at Nojang.

Of course, I'm sure you know better than most people here just how messy the code is. I'm a java programmer myself, and even though I haven't actually looked at MC's source it's pretty obvious to me, just judging by the filenames they pick for the textures, they have no professional education on java programming. They seem to operate more like advanced amateurs. They seem to just do "eh whatever!" with no regard what so ever to any kind of organizational pattern, industry standard or their own.

/rantoff

Hey, Kahr!
Is there any way to add support nbt.display.Name for blocks?

Quote from Rayvolution

Of course, I'm sure you know better than most people here just how messy the code is. I'm a java programmer myself, and even though I haven't actually looked at MC's source it's pretty obvious to me, just judging by the filenames they pick for the textures, they have no professional education on java programming. They seem to operate more like advanced amateurs. They seem to just do "eh whatever!" with no regard what so ever to any kind of organizational pattern, industry standard or their own.

The code's messy in places for sure, but not horrible. I think you touched on a deeper problem though. It's a cycle. They sit down to fix bugs or do other grunt work, get distracted by some "cool" new feature -- this streaming thing being the latest example -- and the community fawns over it. The boring work of fixing/balancing the old stuff gets pushed to the background, piling onto the debt. No one at Mojang seems to be willing to crack the whip, so the backlog gets bigger and even easier to get distracted from next time.

Quote from _zombiehunter

Done. The original report is closed, so I made a new one specifically for flowing water: MC-40621 (please upvote this everyone).

I added my two cents as well. Everyone please upvote this one if you want to see it fixed.

Quote from _zombiehunter

What also bothers me is a little graphical glitch on my creative inventory tabs:

Strange. MCPatcher doesn't even modify the GUI classes, so it must be a side effect of something else. Do you happen to know which MCPatcher feature in particular causes it? I'll check myself later, but it will help me narrow the problem down.

Quote from Deonyi

I noticed in some old posts you stated that jukebox CTM does not work after 1.2.5. Does the server send NBT data about the music playing to the client? Perhaps using the way comparators detect it would work.

I haven't actually looked if anything changed, but the fact that comparators can detect it doesn't mean anything. Like all game logic, that's likely done on the server.

Um, I really need some help. I'm trying to make a resource pack that uses the CIT feature, but the help page doesn't give me the information I need. I don't need all of that help, I need a format, or an example on how you type it.

Basically, I need a pre-made CIT file for renamed items. It doesn't matter what the item is, I just need a pre-made CIT file.

Quote from Warpshard

Um, I really need some help. I'm trying to make a resource pack that uses the CIT feature, but the help page doesn't give me the information I need. I don't need all of that help, I need a format, or an example on how you type it.

Basically, I need a pre-made CIT file for renamed items. It doesn't matter what the item is, I just need a pre-made CIT file.

CIT is super easy, actually.
1. make a \assets\minecraft\mcpatcher\cit folder in your pack. (you can add subfolders as well)
2. Whatever texture you want to use CIT on, put the CIT-version in the folder.
3. Make a same-name .properties file (IE: damaged_diamond_pickaxe.png and .properties)
4. Inside, the only line *required* is:

 items=ItemID 

But, most people won't be using CIT for just that.. if they were, why would they even bother?

Here's an example .properties file for a bat spawn egg in my pack, where the damage property stores the type of mob that spawns

items=383
damage=65

..and one from Misa's pack, thats an example of tool desegregation, any durability level between 626-1249 on item 279 (an axe) would use the texture misaaxd1.png

misaaxd1.properties:

matchItems=279
damage=626-1249

As for settings and tweaks, this should help get you going in the right direction:
https://bitbucket.org/prupe/mcpatcher/src/cd62a7644b4ed60849cc5ff0dc970b7e58f4149d/doc/cit.properties?at=3.x

(EDIT: Note that matchItems and Items are the same thing basically)