Starting July 30th, you will no longer be able to log in to a Curse account that was not merged with a Twitch account. If you have not yet merged your Curse account with a Twitch account, please do so here! Otherwise, your account and its content will be inaccessible.
Actually the post rate has stayed about the same. The view count on the other hand has gone WAY up. I think that the type of people who visit this forum are also the type of people who noticed pinned threads.
Rollback Post to RevisionRollBack
"Look, I don't care if your 8 or 20. If you can't take criticism or opinions, then get off the internet." -Stronghold257
as a side note, I'm not sure if this is mentioned anywhere in the texturing guides, but you might want to add a note that editing the light_normal.png file doesn't do anything at all and the actual lighting texture is simply generated at run-time. I'm not sure if the patcher changes anything on this front (99% sure it doesn't), but even that would be a lost cause as there would be no way to do skylight fades.
I bring this up because to this day Painterly still offers a option for changing the lightmap, heh.
EDIT: You know what, this is actually a bit unfitting for this thread in general, heh.
No, 4, as soon as it got stickied people read it, and moved on, without posting. :tongue.gif:
Just some commentary on this, all your statements are correct, but I know a few more reasons why people don't 'finish' packs.
Firstly, some texture pack makers don't 'finish' packs, because, theorteically they can't define an 'end', some packs are just the terrain and items redone, some not even that. 'Cause if you think about it, when does a texture pack go from a WIP to complete? When every single file that can be editted is? When you've editted all the terrain.png and item.png, and added a pack.png?
Secondly, some people don't know how to do animations, and even when people get told how to do lava and water, they don't know how to make a portal or fire animation.
Lastly, in the same vein as my first point, some texturers don't deem it necessary to do the extra's, like a font.txt, or even more rarely a clouds.png.
Which is exactly my point. Though I think I may need to reword it. There really is no "finished"
It really bugs me when people get on threads and say things like "Why haven't you finished *insert thing here*" Especially when the thread is labeled WIP. Personally I don't think any of my Pack will ever be finished. I hope to get to a point were everything has been re-textured but I know that I will keep improving them and adding alternates and mod support.
Rollback Post to RevisionRollBack
"Look, I don't care if your 8 or 20. If you can't take criticism or opinions, then get off the internet." -Stronghold257
I don't know if this holds true still, but you could crash Minecraft just with a texture pack. Minecraft was only coded to handle certain sizes for some images, and exceeding that size(2x default, or 32x, is usually the max) would give you a black screen as soon as the image was attempted to be loaded. For example, using a pumpkinblur 3x or higher would crash Minecraft as soon as you put a pumpkin on as a helmet. Again, not sure if this still applies since Minecraft is "hd compatible" now.
I don't know if this holds true still, but you could crash Minecraft just with a texture pack. Minecraft was only coded to handle certain sizes for some images, and exceeding that size(2x default, or 32x, is usually the max) would give you a black screen as soon as the image was attempted to be loaded. For example, using a pumpkinblur 3x or higher would crash Minecraft as soon as you put a pumpkin on as a helmet. Again, not sure if this still applies since Minecraft is "hd compatible" now.
Still not a problem with the Texture Pack, it's a problem with the game not being patched for it.
Rollback Post to RevisionRollBack
Theevilpplz is so fabulous, hetrosexual men turn bi when he passes by.
I don't know if this holds true still, but you could crash Minecraft just with a texture pack. Minecraft was only coded to handle certain sizes for some images, and exceeding that size(2x default, or 32x, is usually the max) would give you a black screen as soon as the image was attempted to be loaded. For example, using a pumpkinblur 3x or higher would crash Minecraft as soon as you put a pumpkin on as a helmet. Again, not sure if this still applies since Minecraft is "hd compatible" now.
If I get what you are saying, putting a pumpkin on your head that is included with a 128x texture pack would crash the game, if the .png file were increased in size at the same ratio as the rest of the pack? Easy to test that, the pumpkin blur for Impressions happens to be sized proportionality for that resolution.
Well, here is a screenshot that shows my pumpkin blur in game. (and my zombie mob skin as well. :smile.gif:
Still not a problem with the Texture Pack, it's a problem with the game not being patched for it.
The OP said texture packs can't crash Minecraft, and my point was they actually can. Yes, if the client is patched it wouldn't crash, but it's still the texture pack causing the crash regardless of whether the client is patched or not.
Anyways, good job, most of these points are true, but good luck getting people to read it. I have a FAQ in my own thread before people install and they still spam the same questions over and over about "WHY ARE BRICKS BROKEN!?!"
If I get what you are saying, putting a pumpkin on your head that is included with a 128x texture pack would crash the game, if the .png file were increased in size at the same ratio as the rest of the pack? Easy to test that, the pumpkin blur for Impressions happens to be sized proportionality for that resolution.
Well, here is a screenshot that shows my pumpkin blur in game. (and my zombie mob skin as well. :smile.gif:
Ah, so Minecraft actually is fully HD "compatible?" Well that's good to know, though now I'm curious to do more extensive testing.
The OP said texture packs can't crash Minecraft, and my point was they actually can. Yes, if the client is patched it wouldn't crash, but it's still the texture pack causing the crash regardless of whether the client is patched or not.
Anyways, good job, most of these points are true, but good luck getting people to read it. I have a FAQ in my own thread before people install and they still spam the same questions over and over about "WHY ARE BRICKS BROKEN!?!"
Ah, so Minecraft actually is fully HD "compatible?" Well that's good to know, though now I'm curious to do more extensive testing.
By all means, please. I would love to know more.
Though I would like to point out that the issue would still be a problem with patcher and not the texture pack.
But, I would concede the point anyway. :smile.gif:
Rollback Post to RevisionRollBack
"Look, I don't care if your 8 or 20. If you can't take criticism or opinions, then get off the internet." -Stronghold257
Though I would like to point out that the issue would still be a problem with patcher and not the texture pack.
Actually it's not the problem with the patcher since the client wouldn't be patched, it would be a problem with the person who doesn't read and find out they have to patch. In the end though, the texture pack is the one who would have been making Minecraft crap itself a black screen, in the most exact sense. Still the persons fault, but just saying a texture pack easily has the possibility(or did, at least) of crashing Minecraft, even if it didn't edit code.
Actually it's not the problem with the patcher since the client wouldn't be patched, it would be a problem with the person who doesn't read and find out they have to patch. In the end though, the texture pack is the one who would have been making Minecraft crap itself a black screen, in the most exact sense. Still the persons fault, but just saying a texture pack easily has the possibility(or did, at least) of crashing Minecraft, even if it didn't edit code.
hmm I suppose I can reword it.
If it is needed after some research. :smile.gif:
The vast majority of the posts that I run into were people are getting pissy at texture packs creators are because of issues caused with improper installation of the HD patches. That's what I was adressing.
Rollback Post to RevisionRollBack
"Look, I don't care if your 8 or 20. If you can't take criticism or opinions, then get off the internet." -Stronghold257
Ah, so Minecraft actually is fully HD "compatible?" Well that's good to know, though now I'm curious to do more extensive testing.
32x textures and below do not crash the game.
64x... I'm not sure. Haven't tested that in 1.8.1 or any of the 1.9 prereleases.
128x and above often can cause crashes even when enough memory is allocated, but does not black screen as soon as the texture is loaded.
Everything that is not 16x messes up the way the game locates individual tiles on texture sheets like terrain.png and items.png.
So that means you can still make many things in different resolutions that the default without any mods. But not everything, and not the most important things.
"He's the hero Minecraft Forums deserves, but not the one it needs right now. So, we'll hunt him, because he can take it. Because he's not our hero. He's a silent guardian. A watchful protector. A SilverMatt."
32x textures and below do not crash the game.
64x... I'm not sure. Haven't tested that in 1.8.1 or any of the 1.9 prereleases.
128x and above often cause crashes(even when enough memory is allocated) if you have a few textures at this resolution.
Everything that is not 16x messes up the way the game locates individual tiles on texture sheets like terrain.png and items.png.
So that means you can still make many things in different resolutions that the default without any mods. But not everything, and not the most important things.
But this would be the result of poor hardware. Not texture packs. :smile.gif:
Also, that is not quite what he was describing...I think.
Rollback Post to RevisionRollBack
"Look, I don't care if your 8 or 20. If you can't take criticism or opinions, then get off the internet." -Stronghold257
But this would be the result of poor hardware. Not texture packs. :smile.gif:
Also, that is not quite what he was describing...I think.
It's not the hardware's fault that minecraft can't properly handle it. Low computer specs certainly contribute to making the game crash more often though.
Rollback Post to RevisionRollBack
"He's the hero Minecraft Forums deserves, but not the one it needs right now. So, we'll hunt him, because he can take it. Because he's not our hero. He's a silent guardian. A watchful protector. A SilverMatt."
Saying that texture packs cause problems with Minecraft is like saying that your pencil makes spelling mistakes.
Well the point was that he claimed that texture packs couldn't crash Minecraft because they didn't change any code(as if this made it impossible), but that's not really true. It was perfectly capable of crashing Minecraft, regardless of the reason(I already said it's of course the persons fault for not reading and patching the client).
Actually the post rate has stayed about the same. The view count on the other hand has gone WAY up. I think that the type of people who visit this forum are also the type of people who noticed pinned threads.
as a side note, I'm not sure if this is mentioned anywhere in the texturing guides, but you might want to add a note that editing the light_normal.png file doesn't do anything at all and the actual lighting texture is simply generated at run-time. I'm not sure if the patcher changes anything on this front (99% sure it doesn't), but even that would be a lost cause as there would be no way to do skylight fades.
I bring this up because to this day Painterly still offers a option for changing the lightmap, heh.
EDIT: You know what, this is actually a bit unfitting for this thread in general, heh.
"sometimes, wizards are so awesome, it hurts"
Which is exactly my point. Though I think I may need to reword it. There really is no "finished"
It really bugs me when people get on threads and say things like "Why haven't you finished *insert thing here*" Especially when the thread is labeled WIP. Personally I don't think any of my Pack will ever be finished. I hope to get to a point were everything has been re-textured but I know that I will keep improving them and adding alternates and mod support.
No problem. :biggrin.gif:
I will add a section on that.
thank you, good sir.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Retired StaffStill not a problem with the Texture Pack, it's a problem with the game not being patched for it.
If I get what you are saying, putting a pumpkin on your head that is included with a 128x texture pack would crash the game, if the .png file were increased in size at the same ratio as the rest of the pack? Easy to test that, the pumpkin blur for Impressions happens to be sized proportionality for that resolution.
Well, here is a screenshot that shows my pumpkin blur in game. (and my zombie mob skin as well. :smile.gif:
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe OP said texture packs can't crash Minecraft, and my point was they actually can. Yes, if the client is patched it wouldn't crash, but it's still the texture pack causing the crash regardless of whether the client is patched or not.
Anyways, good job, most of these points are true, but good luck getting people to read it. I have a FAQ in my own thread before people install and they still spam the same questions over and over about "WHY ARE BRICKS BROKEN!?!"
Ah, so Minecraft actually is fully HD "compatible?" Well that's good to know, though now I'm curious to do more extensive testing.
By all means, please. I would love to know more.
Though I would like to point out that the issue would still be a problem with patcher and not the texture pack.
But, I would concede the point anyway. :smile.gif:
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumActually it's not the problem with the patcher since the client wouldn't be patched, it would be a problem with the person who doesn't read and find out they have to patch. In the end though, the texture pack is the one who would have been making Minecraft crap itself a black screen, in the most exact sense. Still the persons fault, but just saying a texture pack easily has the possibility(or did, at least) of crashing Minecraft, even if it didn't edit code.
hmm I suppose I can reword it.
If it is needed after some research. :smile.gif:
The vast majority of the posts that I run into were people are getting pissy at texture packs creators are because of issues caused with improper installation of the HD patches. That's what I was adressing.
32x textures and below do not crash the game.
64x... I'm not sure. Haven't tested that in 1.8.1 or any of the 1.9 prereleases.
128x and above often can cause crashes even when enough memory is allocated, but does not black screen as soon as the texture is loaded.
Everything that is not 16x messes up the way the game locates individual tiles on texture sheets like terrain.png and items.png.
So that means you can still make many things in different resolutions that the default without any mods. But not everything, and not the most important things.
"He's the hero Minecraft Forums deserves, but not the one it needs right now. So, we'll hunt him, because he can take it. Because he's not our hero. He's a silent guardian. A watchful protector. A SilverMatt."
But this would be the result of poor hardware. Not texture packs. :smile.gif:
Also, that is not quite what he was describing...I think.
It's not the hardware's fault that minecraft can't properly handle it. Low computer specs certainly contribute to making the game crash more often though.
"He's the hero Minecraft Forums deserves, but not the one it needs right now. So, we'll hunt him, because he can take it. Because he's not our hero. He's a silent guardian. A watchful protector. A SilverMatt."
-
View User Profile
-
View Posts
-
Send Message
Retired Staff-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWell the point was that he claimed that texture packs couldn't crash Minecraft because they didn't change any code(as if this made it impossible), but that's not really true. It was perfectly capable of crashing Minecraft, regardless of the reason(I already said it's of course the persons fault for not reading and patching the client).