Minecraft Forums

The Technician Remix is missing the right version of railcraft's disembarking track.

Hi. I may be wrong in posting this here (I certainly hope not), and forgive me if it is... but after I activated my customised pack, the diamond and ladder did not have textures. Should I simply choose a different texture for these items?

Is this intentional? and how do i change this? Slabs, and stairs are uneffected

Quote from TheManFromLolliLand

Is this intentional? and how do i change this? Slabs, and stairs are uneffected

I have no idea what this is but it would help if you list these three things that may help with the debugging.

Minecraft version.
John Smith Legacy version.
MCPatcher version.

Quote from Banduck

my mix

While posting a custom pack is aloud, posting it using an adfly links are against the original authors rules plus the pack you have posted is very old and not alot different from the version that was released at that time (July 2013).

so bibliocraft and EXBL textures don't load when starting any instance due to:

2014-01-07 16:45:10 [WARNING] [Minecraft-Client] ResourcePack: ignored non-lowercase namespace: BiblioCraft

@JimStoneCraft
can you tell me why this might be happening?

Another small update for some compatibility. (tested with Minecraft 1.7.2 and OptiFine_1.7.2_HD_U_A9, this is not ideal as the pack was made for 1.7.4 but should work for the most part.)

-{1.2.8}- 8th January 2014 - 1.7.4

I had no plans on testing this pack in Optifine but decided to do some limited testing anyway as some people are having some issues.

In Minecraft 1.7 onwards, blocks are referred to by name rather than ID number.

Numerical IDs are supported for older blocks currently, but newer blocks will be name only.

Stone blocks for example can be referred to as:-
1 (not recommended)
minecraft:stone (full name)
stone (name without prefix)

The trouble is Optifine still uses ID's so this is why the custom colours are not working correctly.

I've temporarily change the names back to ID's (names are still in the color.properties files but are commented out) as at least this is currently compatible with both Optifine and MCPatcher but with new blocks coming along like Granite, these will not even have an ID number and go by just a name so this will have to change to the newer system in the end anyway.

Some things like the trip wire hooks and lever do not work in Optifine (they will look default).

As the font can display wrong with Optifine, I've removed the two font kerning properties files.


On a side note, I have not bothered to update the John Smith Legacy - JimStoneCraft Edition pack as I do not and have no intention of using Optifine on a Vanilla world.

Ahh, thank you so much! very helpful! #NoMoreGreenWood XD

Some successfully made bump mapped texture for this? I can't get it to work on 1.6.4.

Quote from Motionless_Shade

so bibliocraft and EXBL textures don't load when starting any instance due to:

2014-01-07 16:45:10 [WARNING] [Minecraft-Client] ResourcePack: ignored non-lowercase namespace: BiblioCraft

@JimStoneCraft
can you tell me why this might be happening?

Sorry I only work with the Vanilla Minecraft Resource Pack, Glowstrontium and Greenhawk837 are the modded Minecraft specialists.


Hey it's Snapshot time again.

Note:- This is a Snapshot Resource Pack only and contains only the blocks that have been added or changed, a complete pack will be released when the next full release of Minecraft has been made.

John Smith Legacy Snapshot.zip

Make sure you have the John Smith Legacy pack {1.2.8}- 8th January 2014 and also put the Snapshot pack at the top of the list on the Resource Pack screen.


Note that this pack is no longer compatible with Minecraft 1.7.4 due to GUI changes, download the older packs for Minecraft 1.7.4, also CTM doesn't work with this latest release until a new version of MCPatcher is released.

JimStoneCraft
<ADDED>
[JimStoneCraft] textures/blocks/slime.png
textures/blocks/stone_andesite.png
textures/blocks/stone_andesite_smooth.png
textures/blocks/stone_diorite.png
textures/blocks/stone_diorite_smooth.png
textures/blocks/stone_granite.png
textures/blocks/stone_granite_smooth.png

Added new stone blocks and slime.

JimStoneCraft
<UPDATED>
[JimStoneCraft] textures/gui/widgets.png
textures/gui/container/enchanting_table.png

Added the lock icons and modified the enchanting screen.

@JimStoneCraft, what exactly did you change in the color.properties file pertaining to this post regarding fixing the top of Grass blocks being White?

I am asking because I want to use a version of that file from this texture pack from around the time of 1.6.4, because doing so gets me the results in 1.7.4 that custom colors produced in 1.6.4 and prior (which is what I greatly prefer), but it also gets me an issue with Grass blocks being White on top. I'd appreciate if you could tell me what change I would need to make to that file to fix the grass while not changing anything else.

I removed one line from the color.properties file listed below, just stick a hash # in front of it to make Minecraft ignore it if you don't want to remove it completely), I also removed the tint.png file as it would no longer be needed.

I'm not even sure what this even did as I saw no difference apart from the white grass.

palette.block.~/colormap/tint.png=1 2 3 4 5 6 7 13 14 15 16 17 20 21 22 23 24 35 37 38 39 40 41 42 43 44 45 47 48 49 53 54 56 58 60 61 62 63 64 65 67 71 72 73 74 82 86 87 88  89 91 96 97 98 98 101 102 108 109 110 111 112 113 114 116 117 118 120 121 125 126 127 128 129 130 133 134 135 136

I appreciate the help, although I haven't been able to find the desired solution. Doing either of the two things you listed does fix the grass, but alas, also breaks custom colors looking as they did before.

It appears that comment and that image file (perhaps among other things) are responsible for custom colors.

All the numbers listed in the palette.block code are Block ID's for the blocks in the game, try just removing the number 2 from that list as that's the ID for Grass.

palette.block.~/colormap/tint.png=1 3 4 5 6 7 13 14 15 16 17 20 21 22 23 24 35 37 38 39 40 41 42 43 44 45 47 48 49 53 54 56 58 60 61 62 63 64 65 67 71 72 73 74 82 86 87 88 89 91 96 97 98 98 101 102 108 109 110 111 112 113 114 116 117 118 120 121 125 126 127 128 129 130 133 134 135 136

This is the site I use which lists Block ID's if you are interested.

http://minecraft.gamepedia.com/Data_values#Block_IDs

Yay, it's all better! Thank you!

The funny thing is, knowing next to nothing about this stuff, I was looking at those numbers funny wondering what they were. I thought maybe they were color values at first, but I noticed the gaps and wondered if they were block ID numbers. I tried removing the first number and it didn't fix it, so I gave up. It figures if I would have tested the very next number I'd had found out.

If removing that bit of things was your fix for the White grass, knowing that it also effects custom colors, perhaps you could make this change to the live texture pack? I mean, only I seemed to be the one to notice and/or mention the changes to custom colors in this thread, but if that's all the fix was for, but you only have to remove that one number, perhaps you could do just that instead for any custom colors users?

Edit: I almost forgot, but I have another question. Is there a way to revert the over the top glow to enchanted items/icons of those icons that 1.7 introduced or no? I mean, I don't know why Mojang thought it was a good idea to make them so blindingly overdone to the point of it being hard to distinguish between the material of the item offhand sometimes.

Quote from Princess_Garnet

If removing that bit of things was your fix for the White grass, knowing that it also effects custom colors, perhaps you could make this change to the live texture pack? I mean, only I seemed to be the one to notice and/or mention the changes to custom colors in this thread, but if that's all the fix was for, but you only have to remove that one number, perhaps you could do just that instead for any custom colors users?

Block ID's are being phased out so it would have to be updated but I'll looked into it.

Quote from Princess_Garnet

Edit: I almost forgot, but I have another question. Is there a way to revert the over the top glow to enchanted items/icons of those icons that 1.7 introduced or no? I mean, I don't know why Mojang thought it was a good idea to make them so blindingly overdone to the point of it being hard to distinguish between the material of the item offhand sometimes.

The enchanted item glint is controlled by the file listed below, this is a twice resolution version with some extra smoothing, if you delete or rename the file and then reload the pack it will use the default resource pack that may be more to your liking, I'm not sure what's changed as this file has been is the JSL pack for over a year.

textures/misc/enchanted_item_glint.png

You can also if you like turn the glint off completely in the file below.

mcpatcher/cit.properties

change the line:-

useGlint=true

to

useGlint=false

This removes the glint from all the items that use it (Potions, Enchanted items etc..), it may not be what you want but it is an option.

Jim,

quartz_block_top.png and quartz_block_side.png files are the same. Is the former a placeholder you plan to change later? Or is this an oversight and quartz_block_bottom.png is the actual file intended for the upper and bottom faces of the quartz block?

(Just to post this again. If this is some sort of stupid mistake I am making, simply let me know.)
Hi. I may be wrong in posting this here (I certainly hope not), and forgive me if it is... but after I activated my customised pack, the diamond and ladder did not have textures. Should I simply choose a different texture for these items?

Quote from marfig

Jim,

quartz_block_top.png and quartz_block_side.png files are the same. Is the former a placeholder you plan to change later? Or is this an oversight and quartz_block_bottom.png is the actual file intended for the upper and bottom faces of the quartz block?

That's the way it is in Vanilla.

I understand that. What I'm saying is that currently the JSL only sets a different texture to the bottom face of the quartz block, Are you planning to change the top face too to match the bottom face or is it was intentional to have the top face file the same as the side face?

Quartz is special in Minecraft as it has textures for top, bottom and sides (no mcpatcher required).

But as I said in Vanilla the top and side faces are the same with a different bottom face, I have no plans to change that in JSL.