I've just updated the mirror links for JSTR and Legacy with mod support, thanks to Dweller_Benthos for posting those, I have merged some of the items, and there has been a few minor fixes for Railcraft (black lines on tanks .etc).
We have also started with Gregtech, although only some of the blocks and GUIs are currently done.
I created a mod called Walking Dead. I would like to use the zombie villager texture from this pack. I don't think it's from the original JohnSmith Pack. Whom do I need to ask permission to use the zombie_villager.png texture in my mod?
I created a mod called Walking Dead. I would like to use the zombie villager texture from this pack. I don't think it's from the original JohnSmith Pack. Whom do I need to ask permission to use the zombie_villager.png texture in my mod?
You can use it as you wish, it's just you can't make any money with his work. So if you plan on putting your mod under adf.ly, that won't be possible for as long as you are using his texture.
You can use it as you wish, it's just you can't make any money with his work. So if you plan on putting your mod under adf.ly, that won't be possible for as long as you are using his texture.
I don't use adf.ly. I don't make any money in any way from my mods. I give credit to JohnSmith in my forum thread and in the mod itself. I don't think this image was in the last pack updated by JohnSmith, that's why I was asking. I think maybe someone else made it. I'll go ahead and use it and if someone knows who actually made the zombie_villager texture they can post here or PM me.
thanks.
All of the download links are formatted to the new snapshot format. With the individual texture files. Am I the only one having this problem?
It won't matter if you're using a version of minecraft that isn't one of the snapshots. MC will still take all of the textures straight from the terrain.png.
It won't matter if you're using a version of minecraft that isn't one of the snapshots. MC will still take all of the textures straight from the terrain.png.
As a clarification, that means 1.5 texture packs works with all previous versions of minecraft?
I've made some better can & cell textures, I hope you'll like them... I originally made them for myself, but then I found this great texture pack and decided that they could be useful to someone else.
Does anyone know why the clouds are screwed up in this texture pack as of lately? For a long time I never had a problem with clouds in the Johnsmith texture pack, but for some reason lately the pack's clouds are invisible from the ground and cut off all visibility to objects above the 127 layer. If I go up above 127, I see everything normally and can see the cloud later underneath, however; it's only when viewing from the ground that it's all screwed up.
I'm 99.9% certain the problem is with this texture pack now, as swapping to minecraft's default textures causes clouds to be visible and for objects to properly render above the 127 layer from the ground. What's going on?!
@Lobotomy, if your using Optifine try adjusting the cloud level or maybe turning it off?
I don't use optifine, but I do use mcpatcher; is there some setting in there I'd need to tweak to fix it? I'm kinda hoping to not have to turn clouds off, since they look really nice above the cloud level (it makes them look like this dense mist/fog); I'm just bothered by how they're invisible from the ground and make structures not render at all where they are passing through (I could post a screenshot if that would help?)
I don't use optifine, but I do use mcpatcher; is there some setting in there I'd need to tweak to fix it? I'm kinda hoping to not have to turn clouds off, since they look really nice above the cloud level (it makes them look like this dense mist/fog); I'm just bothered by how they're invisible from the ground and make structures not render at all where they are passing through (I could post a screenshot if that would help?)
You need to tick the "Better Skies" box before patching, refer to the McPatcher thread's first post more more information if you need it. Otherwise, update both your McPatcher and your copy of the texture pack.
As for the "devs" here... I notice none of you use McPatcher, or encourage its users to switch to Optifine. I'd rather not go into a rant about why McPatcher is better (regarding FEATURES, not PERFORMANCE (and sometimes even that)), so I'd like to ask if one of you could either give McPatcher a try or instead of recommending Optifine, wait McPatcher users to chime in and help.
You need to tick the "Better Skies" box before patching, refer to the McPatcher thread's first post more more information if you need it. Otherwise, update both your McPatcher and your copy of the texture pack.
As for the "devs" here... I notice none of you use McPatcher, or encourage its users to switch to Optifine. I'd rather not go into a rant about why McPatcher is better (regarding FEATURES, not PERFORMANCE (and sometimes even that)), so I'd like to ask if one of you could either give McPatcher a try or instead of recommending Optifine, wait McPatcher users to chime in and help.
I use optifine because of its compatibility with Minecraft forge. I realize that for ease of use, MCPatcher is better, but that compatibility makes or breaks it for me. We recommend optifine because we know it works, and there's no problems with it.
Does anyone know why the clouds are screwed up in this texture pack as of lately? For a long time I never had a problem with clouds in the Johnsmith texture pack, but for some reason lately the pack's clouds are invisible from the ground and cut off all visibility to objects above the 127 layer. If I go up above 127, I see everything normally and can see the cloud later underneath, however; it's only when viewing from the ground that it's all screwed up.
I'm 99.9% certain the problem is with this texture pack now, as swapping to minecraft's default textures causes clouds to be visible and for objects to properly render above the 127 layer from the ground. What's going on?!
You're not the only one having issues with "invisible structures" above the cloud level. The truth is, I never noticed it (I disable clouds by default, because they always got in my way)... but now I see the issue. It's present in 1.4.6 and 1.4.7 (it might even be in earlier versions).
And to confirm, I'm also using MCPatcher... so it might ~actually~ be an MCPatcher issue, and not a problem with the texture pack itself. You may also notice that in the default texture pack, you can see slight errors with the clouds (for instance, 0% transparency for the body of the clouds, but a slight 2px thick transparent "gap" at the edges of the cloud, and then another 2px "strip" of normal clouds at the leading edge). I don't know about OptiFine, or how it looks there... so I can't speak for it... but I think it may just be "how clouds work" by default (obscuring anything above them, and only revealing structures when they are no longer directly below it).
I don't use optifine, but I do use mcpatcher; is there some setting in there I'd need to tweak to fix it? I'm kinda hoping to not have to turn clouds off, since they look really nice above the cloud level (it makes them look like this dense mist/fog); I'm just bothered by how they're invisible from the ground and make structures not render at all where they are passing through (I could post a screenshot if that would help?)
I have "Better Skys" enabled, and have made sure that none of my other mod class files are conflicting with MCPatcher... and it has the same issue... so I can't help you fix it, as I'm also seeing it, and it ~shouldn't~ be happening.
You need to tick the "Better Skies" box before patching, refer to the McPatcher thread's first post more more information if you need it. Otherwise, update both your McPatcher and your copy of the texture pack.
As for the "devs" here... I notice none of you use McPatcher, or encourage its users to switch to Optifine. I'd rather not go into a rant about why McPatcher is better (regarding FEATURES, not PERFORMANCE (and sometimes even that)), so I'd like to ask if one of you could either give McPatcher a try or instead of recommending Optifine, wait McPatcher users to chime in and help.
I've chimed in, but there isn't anything I can offer, in terms of help, other than "Turn off Clouds". Sorry. And while I contribute to the JSTP, I'm not exactly a dev... but I've always used MCPatcher... as I've never needed OptiFine (I'm typically seeing 150~300fps, depending on what I'm doing)... so I don't know if OptiFine users have the same issue.
I've made some better can & cell textures, I hope you'll like them... I originally made them for myself, but then I found this great texture pack and decided that they could be useful to someone else.
Thanks for those, as it happens I was planning to make some replacements for the faithful cans, but now I don't have to
As for the "desktop.ini" files and etcetera, I believe most of those are relics left over from the period from when we edited the pack directly on Google Drive without being .zipped, however I can probably run the archive though a filter to remove them.
We probably won't be using Dropbox for much longer anyway as the transfer caps are just not going to cut it. Even if we purge unneeded files and go over to .rar archives, in the grand scheme of things it won't make hardly any difference, so we will probably end up either migrating back to gDrive or (god forbid) MS Skydrive soon.
Check this out.
When I created the beam I tested it on the server. It looked like this
When I checked it yesterday it looked the same.
This screenshot was captured a few minutes ago:
It is definitly a server lag (or maybe bug of craftbukkit). This thing can happen with all transparent beams.
I made a new version of the beam - it has less amount of transparent pixels so it should be more visible.
Also I think this version looks better in SP )
Glad to see that it wasn't just me that was having issues... well, texture pack issues I went ahead and swapped out the beam.png with the one above and it works just as illustrated in your screenshots. Oh, and right now we are running a vanilla server, so craftbukkit isn't to blame.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWe have also started with Gregtech, although only some of the blocks and GUIs are currently done.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt is mix of zombie.png and zombie6.png textures from JohnSmith 9.7 . So technically he is the author
You can use it as you wish, it's just you can't make any money with his work. So if you plan on putting your mod under adf.ly, that won't be possible for as long as you are using his texture.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI don't use adf.ly. I don't make any money in any way from my mods. I give credit to JohnSmith in my forum thread and in the mod itself. I don't think this image was in the last pack updated by JohnSmith, that's why I was asking. I think maybe someone else made it. I'll go ahead and use it and if someone knows who actually made the zombie_villager texture they can post here or PM me.
thanks.
Oh I see! Yes that's the one. Thanks. I missed your post, it was on the previous page.
It won't matter if you're using a version of minecraft that isn't one of the snapshots. MC will still take all of the textures straight from the terrain.png.
As a clarification, that means 1.5 texture packs works with all previous versions of minecraft?
I've made some better can & cell textures, I hope you'll like them... I originally made them for myself, but then I found this great texture pack and decided that they could be useful to someone else.
Here the source .psd:
http://dl.dropbox.co...ll-and-cans.psd
I'm 99.9% certain the problem is with this texture pack now, as swapping to minecraft's default textures causes clouds to be visible and for objects to properly render above the 127 layer from the ground. What's going on?!
I don't use optifine, but I do use mcpatcher; is there some setting in there I'd need to tweak to fix it? I'm kinda hoping to not have to turn clouds off, since they look really nice above the cloud level (it makes them look like this dense mist/fog); I'm just bothered by how they're invisible from the ground and make structures not render at all where they are passing through (I could post a screenshot if that would help?)
You need to tick the "Better Skies" box before patching, refer to the McPatcher thread's first post more more information if you need it. Otherwise, update both your McPatcher and your copy of the texture pack.
As for the "devs" here... I notice none of you use McPatcher, or encourage its users to switch to Optifine. I'd rather not go into a rant about why McPatcher is better (regarding FEATURES, not PERFORMANCE (and sometimes even that)), so I'd like to ask if one of you could either give McPatcher a try or instead of recommending Optifine, wait McPatcher users to chime in and help.
I use optifine because of its compatibility with Minecraft forge. I realize that for ease of use, MCPatcher is better, but that compatibility makes or breaks it for me. We recommend optifine because we know it works, and there's no problems with it.
And to confirm, I'm also using MCPatcher... so it might ~actually~ be an MCPatcher issue, and not a problem with the texture pack itself. You may also notice that in the default texture pack, you can see slight errors with the clouds (for instance, 0% transparency for the body of the clouds, but a slight 2px thick transparent "gap" at the edges of the cloud, and then another 2px "strip" of normal clouds at the leading edge). I don't know about OptiFine, or how it looks there... so I can't speak for it... but I think it may just be "how clouds work" by default (obscuring anything above them, and only revealing structures when they are no longer directly below it).
I have "Better Skys" enabled, and have made sure that none of my other mod class files are conflicting with MCPatcher... and it has the same issue... so I can't help you fix it, as I'm also seeing it, and it ~shouldn't~ be happening.
I've chimed in, but there isn't anything I can offer, in terms of help, other than "Turn off Clouds". Sorry. And while I contribute to the JSTP, I'm not exactly a dev... but I've always used MCPatcher... as I've never needed OptiFine (I'm typically seeing 150~300fps, depending on what I'm doing)... so I don't know if OptiFine users have the same issue.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThanks for those, as it happens I was planning to make some replacements for the faithful cans, but now I don't have to
As for the "desktop.ini" files and etcetera, I believe most of those are relics left over from the period from when we edited the pack directly on Google Drive without being .zipped, however I can probably run the archive though a filter to remove them.
We probably won't be using Dropbox for much longer anyway as the transfer caps are just not going to cut it. Even if we purge unneeded files and go over to .rar archives, in the grand scheme of things it won't make hardly any difference, so we will probably end up either migrating back to gDrive or (god forbid) MS Skydrive soon.
Meh, meh...
Glad to see that it wasn't just me that was having issues... well, texture pack issues
Thanks for doing a bit of detective work!