I am trying to update Misa's beautiful ctm glass texture to 1.8 but I don't seem to be doing it right because its not working. If anyone could help that would be awesome, love her pack, but she is no longer working on it.
This has probably been asked before, but I can't get the search function to work for specific threads anymore, sorry.
But is it possible to give fire random textures? I don't think I've seen it in many packs, so I don't really want to go through the hassle of making a bunch of new textures without knowing for sure.
I still cant get the new version to work, it downloads as a 0_01[1] File (.0_01[1]) file now instead of an Application (.exe) file and I cant open it.
anyone have an idea how to get it working?
A 0_01[1] file? That's really strange. You can try the alternate download under other platforms. That one's a jar file and you may be able to use it. If it still comes out as 0_01[1] then you can try renaming it to a jar file. It's possible you have a setting in your browser that renames the file when it saves.
Rollback Post to RevisionRollBack
I'm not active on these forums, so forgive me if I don't respond!
If you want to contact me, try going through Discord or you can find me on GitHub where I am still updating the below mods (and more):
A 0_01[1] file? That's really strange. You can try the alternate download under other platforms. That one's a jar file and you may be able to use it. If it still comes out as 0_01[1] then you can try renaming it to a jar file. It's possible you have a setting in your browser that renames the file when it saves.
what do I do with the jar file ?
nvrmnd, it just opens......derp
so, a few questions about the new metadata specifications
You wrote instead of minecraft:leaves:0,4,8,12 to use minecraft:leaves:variant=oak
To be specific, just "variant=oak" means the same thing as "variant=oak:check_decay:false,true:decayable:false,true"? IE all values of the other, non specified properties are included? So functionally one is eliminating the values not listed for any property given, but including all values for properties not given?
because BlockLeaf.getDefaultState().withProperty(BlockOldLeaf.VARIANT, BlockPlanks.EnumType.OAK); is equivalent to metadata 8, so I assume MCPatcher's parser is rolling in the other values for decayable and check_decay as well for it to be equivalent to 0,4,8,12?
its like a rule for CIT. As long as the rules match, it applies the given textures. So when you only apply minecraft:leaves:variant=oak it goes for every variant=oak leave including decayable and undecayable ones
which makes it nice and easy for texture pack authors, but more of a PITA for someone trying to parse metadata stuff in code! I'll deal with it
Sphax 1.7.10 does though, and it still doesn't work. I used the same resourcepack with Optifine and connected textures work.
Also, every time I load up Minecraft, it switches to the default resourcepack. It shows the Sphax "Mojang" logo, but then is at the default when the game fully loads. This only happens when MCPatcher is installed.
I think there's a bug with the overlay textures on leather armor and CIT. For some reason "texture.leather_layer_1_overlay=" and "texture.leather_layer_2_overlay=" don't replace the texture in-game anymore.
The Meaning of Life, the Universe, and Everything.
Location:
California
Join Date:
9/16/2011
Posts:
43
Minecraft:
HunterBlackbrick
Member Details
Okay so I'm still having a problem with custom colors, my grid colormaps aren't being read as grid. Everything was working fine in 1.7, but now in 1.8 it's not working, I'm not sure why though. I've checked the files and they all seem to be written correctly.
From that picture you can see what I mean about the colors not reading correctly. None of that is supposed to be those colors...
So uhhh... I'm not even sure if this is an MCPatcher bug, or just minecraft, but I'll post it here anyway in case it is? Also, it's kind of funny.
I'm on a survival world, but in creative because I just wanna build stuff, and I was flying around mapping out the area, when I saw a floating, upside down skeleton nearby. It kinda teleported around whenever i looked towards it, sometimes disappearing or glitching back onto the ground or something. Then as I flew around some more and went up and down, other mobs started doing that too. There was also sometimes a bow floating below me.
The Meaning of Life, the Universe, and Everything.
Location:
Christchurch
Join Date:
12/18/2011
Posts:
43
Minecraft:
eccentric_nz
Member Details
Hello all, I could do with a little help.
In conjunction with my Bukkit plugin TARDIS, I have a companion Resource Pack that re-textures TARDIS items using the Custom Textures and Models mod (CIT). One of the items is a re-textured compass (which via the plugin has been repurposed as a TARDIS locator i.e. the needle points to the TARDIS Police Box's current location).
The Locator image and .mcmeta files are basically the same setup as the vanilla compass texture - I'm not using a custom dial animation
The problem I am having is that the TARDIS Locator animation now runs permanently when using MCPatcher 5.0.0_1 and Minecraft 1.8.1-pre3, where as in the previous version (4.3.2_03 / MC 1.7.10) the locator acted normally like a regular compass.
So uhhh... I'm not even sure if this is an MCPatcher bug, or just minecraft, but I'll post it here anyway in case it is? Also, it's kind of funny.
I'm on a survival world, but in creative because I just wanna build stuff, and I was flying around mapping out the area, when I saw a floating, upside down skeleton nearby. It kinda teleported around whenever i looked towards it, sometimes disappearing or glitching back onto the ground or something. Then as I flew around some more and went up and down, other mobs started doing that too. There was also sometimes a bow floating below me.
I've had this same problem prior to 1.8.
Is it a bug in the CIT or is there another way to do it?
I also attempted to apply it via the numbers IDing each potion type, which also did not work.
It looks like a Minecart with Hopper, try the latest release (mcpatcher-5.0.0_01) as this has been sorted out.
https://www.johnsmithlegacy.co.uk/ - John Smith Legacy for Minecraft
My renderpass properties are
backfaceCulling.overlay=false
blend.overlay=alpha
then for block20.properties (the glass frame)
method=ctm
tiles=0-47
renderPass=backface
innerSeams=true
and for block20a.properties (the glass block)
method=ctm
tiles=0-47
renderPass=overlay
innerSeams=true
the tiles for the frame and block are numbered the same, but they are in different folders with their properties file. Would that make a difference?
In game I can see the frame outlines, but the glass texture is completely missing, not showing at all.
I still cant get the new version to work, it downloads as a 0_01[1] File (.0_01[1]) file now instead of an Application (.exe) file and I cant open it.
anyone have an idea how to get it working?
But is it possible to give fire random textures? I don't think I've seen it in many packs, so I don't really want to go through the hassle of making a bunch of new textures without knowing for sure.
A 0_01[1] file? That's really strange. You can try the alternate download under other platforms. That one's a jar file and you may be able to use it. If it still comes out as 0_01[1] then you can try renaming it to a jar file. It's possible you have a setting in your browser that renames the file when it saves.
If you want to contact me, try going through Discord or you can find me on GitHub where I am still updating the below mods (and more):
PRESENCE FOOTSTEPS - (github)
VOID FOG - (github)
what do I do with the jar file ?
nvrmnd, it just opens......derp
You wrote instead of minecraft:leaves:0,4,8,12 to use minecraft:leaves:variant=oak
To be specific, just "variant=oak" means the same thing as "variant=oak:check_decay:false,true:decayable:false,true"? IE all values of the other, non specified properties are included? So functionally one is eliminating the values not listed for any property given, but including all values for properties not given?
because BlockLeaf.getDefaultState().withProperty(BlockOldLeaf.VARIANT, BlockPlanks.EnumType.OAK); is equivalent to metadata 8, so I assume MCPatcher's parser is rolling in the other values for decayable and check_decay as well for it to be equivalent to 0,4,8,12?
which makes it nice and easy for texture pack authors, but more of a PITA for someone trying to parse metadata stuff in code! I'll deal with it
Sphax 1.8.3 doesn't have connected textures.
Sphax 1.7.10 does though, and it still doesn't work. I used the same resourcepack with Optifine and connected textures work.
Also, every time I load up Minecraft, it switches to the default resourcepack. It shows the Sphax "Mojang" logo, but then is at the default when the game fully loads. This only happens when MCPatcher is installed.
From that picture you can see what I mean about the colors not reading correctly. None of that is supposed to be those colors...
I'm on a survival world, but in creative because I just wanna build stuff, and I was flying around mapping out the area, when I saw a floating, upside down skeleton nearby. It kinda teleported around whenever i looked towards it, sometimes disappearing or glitching back onto the ground or something. Then as I flew around some more and went up and down, other mobs started doing that too. There was also sometimes a bow floating below me.
more screenshots:
In conjunction with my Bukkit plugin TARDIS, I have a companion Resource Pack that re-textures TARDIS items using the Custom Textures and Models mod (CIT). One of the items is a re-textured compass (which via the plugin has been repurposed as a TARDIS locator i.e. the needle points to the TARDIS Police Box's current location).
The properties file for the Locator contains:
type=item
texture=locator.png
items=minecraft:compass
nbt.display.Name=TARDIS Locator
The Locator image and .mcmeta files are basically the same setup as the vanilla compass texture - I'm not using a custom dial animation
The problem I am having is that the TARDIS Locator animation now runs permanently when using MCPatcher 5.0.0_1 and Minecraft 1.8.1-pre3, where as in the previous version (4.3.2_03 / MC 1.7.10) the locator acted normally like a regular compass.
Any clues as to how I can get this working again?
TIA
eccentric
I can confirm this as happening to me also. Can't confirm if it's related to MCPatcher though.