Firstly, I would like to say that the site is awesome.
I want to upload my NorseCraft texture pack, but like some others I've run in to some problems with the dimensions. My pack is 16x16 with 32x32 mobs and armour, I saw there was an option for some of the sprites to change the resolution manually, so I set it to 32x32 and tried to make the terrain and such set to the default resolution, but that doesn't seem to work, it still asks for the 32x32 dimensions in all cases but a few where it says it can be any resolution (like the title).
I also noticed that I cannot change any of the settings apart from uploading images in either firefox or IE, updateing the description and such only works in Google Chrome.
The pack settings cannot be changed? Does it just never show a result after clicking the save button or what? Do the descriptions let you type in them?
Which versions of IE and Firefox do you have? If you don't have the latest version i HIGHLY recommend upgrading.
I have a suggestion for uploading char.png.
I have two different sizes of skins I would like to upload to my 32x32 pack.
One of the sizes is a hi res skin to match my pack which is 128x64, this is the size the site is expecting from my pack, so no troubles there.
However that size character skin cannot be used online, only offline. I would also like to upload standard size character skins that can be used online if that's what people prefer. I can't upload these currently.
Do you think the char.png could be allowed to be any resolution?
Done!
You know I think I may just let everything be any resolution...because anything really can. I may just check to make sure its the correct proportion and that it is greater or equal to the default size.
Seeing how as far as I can tell, I'm the only one this affects, it seems kinda self serving but... think you could come up with a script that gets rid of the extra pack on my name? KabPack pack is a bit redundant. Something like if (*Pack or *pack) then don't frickin pack.
Cheers and gnight
Hahaha I'll just change your name manually for now....
I've got another question. I usually have my terrain.png at 64x and my kz.png (paintings) at 128x. I assume that if I did that with the website, it would upsize my terrain.png, right?
aaah. seems like we should probably add kz.png to the list of customizable palette resolutions. So you could make your pack as 64x (the res of terrain.png like you should) then update your kz.png resolution to be of 128x scale. I'll add that in right now.
I have a few notes, but I can't see any major problems. The site is looking great now.
Mojang.png can't be bigger than 128x128, my png is 512x512. Its not exactly an important part of the texture pack though, so I don't really mind if you'd rather not fiddle with it.
My Custom Fire files are 64xAny, so I can't use it on a 32x32 pack. No matter though, I've just scaled it down to 32xAny instead. :happy.gif:
Portal and fire squares missing from terrain.png. This one is a little important. If a person sets MCPatchers options for portals and fire to "not animated" those squares from the terrain.png are used. Here is an image to show what I mean.
And spoiler options and centering would be nice if we have a lot of screenshots. :smile.gif:
Fantastic!
Okay all of those images you mentioned are no longer size restricted. upload whatever you want!!!! hehehe. Gonna work on the portals and lava in terrain.png.
Spoiler and centering is a good idea.
EDIT: Ahh i see. Fire not the lava. and Portal. Those are both MC Patcher textures?
One way of fixing this would be to make a membership structure (instead of ownership), where the textures have a membership. When membership reaches 0 the texture is deleted. This can be expanded upon by adding an owner to it, allowing derivative packs with permission of the owner.
With our framework that doesn't seem to be beneficial. The exception list is easy for us and is easily-manageable. For the future shared textures I think I will keep it quite similar to how it currently is...like so.
- Uploader is owner
- Owner selects usernames of verified "sharers"
- the "Sharer" is then notified and has the ability to import textures from the source pack (not sure how im going to present this option to mixer pack creator)
Same errors. Its not letting me upload them, its tying it to the pack resolution. Alsol if thats the case, whats the point of the pallete resolution chooser?
Point of pallete resolution chooser
This is only for "palettes" that have multiple textures within them, otherwise, it doesn't matter. The uploader needs to know the resolution you are choosing these in so it knows how to crop the multiple images within it. Also, when uploading individually, it needs to know what size you have selected for that individual textures palette (if necessary) as well. This is also needed for the download. The downloader doesn't know for certain which resolution to make one of these palettes because it is possible that you could have (accidentally or on purpose) textures not of the same resolution, but from the same palette.
NOTE: You can upload any palette image straight from your pack using the "by Filename" option in the uploader. No need to upload textures such as moon, sun, grasscolor, foliagecolor, sign, etc. by searching for its name in the list. The list only needs to be used for textures that don't have their own palette image to themselves (any texture in terrain, particles, icons, items, or gui)
Uploading those images you mentioned above works fine for me using the "by Filename" option. I will look into the uploading by texture name in the list issue right now.
Oh I was just thinking in general. There's only so many ways to make a targeting reticle, and there doesn't seem to be much sense in forcing someone to make an extravagant one when what they want involves 4 white pixels.
Yeah on second thought I'll just create an exception list. Thanks for all the fantastic ideas! You guys are really thinking about any future incidences. thanks!
With these, I don't use 512x512 images, I only use 256x256. Now, the site is wanting me to upload these at 512x512. I could double all of these images using nearest neighbour, However there has to be a simpler way of doing it, Not spesifically for me, but because I imagine a lot of packs may have the same problem.
Now, the only conclusive thing I can think of is to get the site itsself to auto resize everything. If you have a 32x32 resolution pack, and upload something that is a fraction of that (Smaller, not larger,) then it should be resized. For example, I upload an inventory.png. The standard for 32x packs is 512x512, However mine is 128x128. This then gets resized automatically up to 512x512, without throwing an error. This means that textures don't have to be uniform in the upload, but the outcome from the site generates the correct size. So in the pack that I download from the site, it ends up as 512x512. The downside of this is that when mixing textures, your algorithm is smooth gradient when sizing down. This would make textures that have been doubled then downsize look blurry at their essential native resolution.
The only other thing that I can think of is to add every single file to the resolution selector. If you feel thats a better option, then do that. However, it would have to be EVERYTHING, apart from terrain.png. This isnt related to my pack personally, Im trying to think of texture packs as a whole.
EDIT: On reflection, the second option sounds eaier, since you've already got that option enabled for some of the files, but it would have to be everything. The other option is to get the person uploading the textures to resize them manually, however this would make the current selection option redundant. This also means that with the favourates and mixing system, Stuff would be the right size.
EDIT2: Actually,
Pretty sure I fixed it. All of those images were made "Static" by us which means they don't change resolution along with different pack resolutions. They are all the default resolutions, though some aren't size restricted.
I imagine there may be a few that you would like to be unrestricted in size that are not currently, so let me know...
This got me thinking: with such a small, single color texture, people are fairly likely to get the duplicate message when compared to an official pack. Not sure how to get around that though.
The duplicate checking won't come out positive if they aren't alike. If anything it won't find dupes that should be. I don't predict it will be an issue as they would have to be 100% exactly the same. Though, if it arises, we'll give it heed.
0
The pack settings cannot be changed? Does it just never show a result after clicking the save button or what? Do the descriptions let you type in them?
Which versions of IE and Firefox do you have? If you don't have the latest version i HIGHLY recommend upgrading.
0
Done!
You know I think I may just let everything be any resolution...because anything really can. I may just check to make sure its the correct proportion and that it is greater or equal to the default size.
0
Hahaha I'll just change your name manually for now....
0
aaah. seems like we should probably add kz.png to the list of customizable palette resolutions. So you could make your pack as 64x (the res of terrain.png like you should) then update your kz.png resolution to be of 128x scale. I'll add that in right now.
DONE!!!
0
I'm not getting the warning about the images not being 512 on the custom lava, water, fire or mojang.png. Which are you getting it one?
0
Should work now.
0
0
Okay all of those images you mentioned are no longer size restricted. upload whatever you want!!!! hehehe. Gonna work on the portals and lava in terrain.png.
Spoiler and centering is a good idea.
EDIT: Ahh i see. Fire not the lava. and Portal. Those are both MC Patcher textures?
0
ok which parts do you mean? Is it just that its asking for a different resolution?
0
oh hmmm....is it working now?
0
With our framework that doesn't seem to be beneficial. The exception list is easy for us and is easily-manageable. For the future shared textures I think I will keep it quite similar to how it currently is...like so.
- Uploader is owner
- Owner selects usernames of verified "sharers"
- the "Sharer" is then notified and has the ability to import textures from the source pack (not sure how im going to present this option to mixer pack creator)
0
Point of pallete resolution chooser
This is only for "palettes" that have multiple textures within them, otherwise, it doesn't matter. The uploader needs to know the resolution you are choosing these in so it knows how to crop the multiple images within it. Also, when uploading individually, it needs to know what size you have selected for that individual textures palette (if necessary) as well. This is also needed for the download. The downloader doesn't know for certain which resolution to make one of these palettes because it is possible that you could have (accidentally or on purpose) textures not of the same resolution, but from the same palette.
NOTE: You can upload any palette image straight from your pack using the "by Filename" option in the uploader. No need to upload textures such as moon, sun, grasscolor, foliagecolor, sign, etc. by searching for its name in the list. The list only needs to be used for textures that don't have their own palette image to themselves (any texture in terrain, particles, icons, items, or gui)
Uploading those images you mentioned above works fine for me using the "by Filename" option. I will look into the uploading by texture name in the list issue right now.
0
Yeah on second thought I'll just create an exception list. Thanks for all the fantastic ideas! You guys are really thinking about any future incidences. thanks!
0
Pretty sure I fixed it. All of those images were made "Static" by us which means they don't change resolution along with different pack resolutions. They are all the default resolutions, though some aren't size restricted.
I imagine there may be a few that you would like to be unrestricted in size that are not currently, so let me know...
0
The duplicate checking won't come out positive if they aren't alike. If anything it won't find dupes that should be. I don't predict it will be an issue as they would have to be 100% exactly the same. Though, if it arises, we'll give it heed.