[MC-5238] 10 MB server texture pack limit too small

I run a couple servers for myself and some friends. On one of these servers we are running the "Feed the Beast" mod pack and there are a lot of textures for the various machines, pipes, etc.

I am attempting to use a 16x16 texture pack for this server which weighs in at about 14 MB (http://prenetic.com/ftb/mc14_16x_isabella_ii.zip). Since there are so many textures for the various blocks and items in this mod it actually exceeds the 10 MB limit in Minecraft and will not complete downloading. Despite this being a fully-supported 16x16 texture pack (this is NOT an HD pack as was the case with MC-2134) it is not compatible with the "automagic" downloader due to its larger size.

I've verified the download begins in IIS and an HTTP 200 code is sent. 10 MB is not a lot to work with considering more and more mod packs are coming out which requires texture artists to pack more textures into their products.

Please at the least consider allowing server administrators to override the maximum texture pack size limit in server.properties. It's a great feature, but as-is it falls short with larger mod packs out there.

Linked issues

is duplicated by 5

MC-2134 Client will not load Texturepack due to size Resolved

MC-4847 Server textures cannot be larger than 10mb Resolved

MC-5662 Server textures do not work with large texture packs Resolved

MC-8161 Server textures won't load over a specific size Resolved

MC-13433 Server Texture Pack not working Resolved

relates to 1

MC-1436 server texture don't work anymore Resolved

Attachments

ftb_isabella.zip

Comments 33

kumasasa 2012-12-23T08:04:17Z

How do you know that there is a 10 MB limit ?

Michael V. Coppola 2012-12-23T09:48:09Z

Hi Kumasasa, sorry I did not include this information in the original report. Please see the error message observed through the Java console below while on our primary server, as well as the corresponding HTTP 200 code from IIS. The maximum file size is denoted in bytes (10 MB = 10,000 KB = 10,000,000 B). The 10 MB limit was also confirmed when successfully downloading a texture pack weighing in just under 10 MB.

Java console output while on primary server:
2012-12-23 01:45:55 [INFO] [STDOUT] Deleting C:\Users\Public\Feed the Beast\FTBBETAA\minecraft\texturepacks-mp-cache\mc14_16x_isabella_ii.zip as it does not match what we currently have (14028561 vs our 0).
2012-12-23 01:45:55 [INFO] [STDERR] java.io.IOException: Filesize is bigger than maximum allowed (file is 3.0, limit is 10000000)
2012-12-23 01:45:55 [INFO] [STDERR] at jn.run(SourceFile:133)
2012-12-23 01:45:55 [INFO] [STDERR] at java.lang.Thread.run(Unknown Source)

IIS log output for the texture pack request:
2012-12-23 09:45:55 10.2.2.11 GET /ftb/mc14_16x_isabella_ii.zip - 80 - 50.46.243.53 Java/1.7.0_07 - 200 0 995 2197

I have also confirmed this is an issue with vanilla Minecraft by performing the same test against a vanilla server. Please see the error message observed through the Java console below while on a vanilla test server, as well as the corresponding HTTP 200 code from IIS.

Java console output while on vanilla test server:
Deleting C:\Users\mcoppola\AppData\Roaming\.minecraft\texturepacks-mp-cache\mc14_16x_isabella_ii.zip as it does not match what we currently have (14028561 vs our 0).
java.io.IOException: Filesize is bigger than maximum allowed (file is 3.0, limit is 10000000)
at jw.run(SourceFile:133)
at java.lang.Thread.run(Unknown Source)

IIS log output for the texture pack request:
2012-12-23 09:59:30 10.2.2.11 GET /ftb/mc14_16x_isabella_ii.zip - 80 - 50.46.243.53 Java/1.7.0_07 - 200 0 995 2220

Zuriki 2012-12-23T12:36:58Z

I could open the texture pack without any issue. It seems to contain a lot of mod-related textures though, which implies to me that this is not an issue with vanilla Minecraft.

Michael V. Coppola 2012-12-23T21:43:47Z

I strongly disagree with your assumption Zuriki.

This isn't a bug regarding a specific texture pack or whether or not you can load it manually; this is a bug related to "automagic" texture packs downloaded as recommended packs on SMP servers. It does contain mod-related textures, but vanilla doesn't map these to anything as those blocks and items don't currently exist in vanilla builds. Any additional textures that are in the pack would simply be unused by a vanilla build of Minecraft.

But let's assume one day more blocks and items are added to vanilla Minecraft, as this has been the trend for the past several updates. These new blocks and items are causing texture packs to grow even for vanilla builds, which takes me to my main point:

Assuming vanilla Minecraft continues to grow and continues to get new blocks and items it becomes more and more likely that a 16x16 texture pack for even just the vanilla game would exceed 10 MB in size. This is a ceiling that needs to be adjusted, either with an override option made available to server administrators or adjusted within the code itself.

Furthermore, since you have stated you could open the pack without any issue manually (as can I) it only furthers my point that this is a limitation in the "automagic" downloader, as I have performed tests against both a modded server and a vanilla server above.

Michael V. Coppola 2012-12-23T21:54:17Z

Another test you could perform Zuriki, take the official vanilla texture pack that comes with Minecraft and try the following:

1. Load in a single 10 MB dummy file to guarantee the size is greater than the 10 MB limit.
2. Rename and re-package the pack and publish it to an accessible web server (it can be local).
3. Configure this as the recommended texture pack in "server.properties".
4. Load Minecraft with the Java console open, connect to the server and read the output once you click "Yes" to "automagically" download the recommended texture pack.

You should see the same errors I posted above, even without any extra mods in the pack. It's a limitation of the file size, not the content of the texture pack.

23 more comments

Daniel 2012-12-23T22:21:13Z

While it would be more comfortable to have Minecraft download texture packs >10MB (for example in your case),
it is technically speaking not a bug in vanilla Minecraft as texture packs that only contain the custom textures required for vanilla Mincraft should not exceed the limit.
@Michael Coppola While this might (I have not tested it, but it should) result in an error, it is not a real argument as there is no point in adding Megabytes of data to a texture pack.

Michael V. Coppola 2012-12-23T22:30:53Z

Perhaps not yet, but as I stated with more blocks and items added this will eventually wind up being a problem for vanilla servers as well as modded servers. I think we can agree that this is not an issue with mods, it's not an issue with modded texture packs, but that the file size limit is simply too small to support a common scenario with a supported 16x16 texture pack.

Regarding your comment on the dummy file, it is in fact a real argument to what Zuriki proposed as his comment implied this was not a problem with vanilla Minecraft due to the extra textures in my pack. I was providing a test to confirm this is not an issue with extra textures, that this is instead an issue with file size regardless of the content of the texture pack and this test confirms that.

Daniel 2012-12-24T00:09:59Z

OK, now I understand what the dummy file was for 🙂
But is it possible using the worst possible .png compression to make a texture pack containing only textures for the current version - 1.4.6 - that is that big?
You speak of a "common scenario", but the texture packs I use are <5MB, can you provide a link to a texture pack that includes only 1.4.6 textures and exceeds the 10MB limit?
If so, it would be a bug.
If not, it would not be a bug since the limit is sufficient for the version it is included in. When future versions require a higher limit - e.g. because of the new format 🙂 - it will probably be increased but at the moment I do not see the necessity to do so for vanilla Minecraft to function properly. That said, I still think it should be increased as there are obviously people that would benefit from it and I do not see any negative effects, but technically speaking it would not be a bug then.

Michael V. Coppola 2012-12-24T00:24:12Z

Daniel, while I agree that this would more appropriately be filed as an "Improvement" in JIRA this was simply not an option when creating the issue initially. I just went back and double-checked to make sure I wasn't doing something wrong on my end, but the only option listed from what I can see is "Bug". To echo your comment, the functionality works as intended, however its design limitations are preventing it from being utilized across a broad set of scenarios.

To clarify, when I say "common scenario" I mean servers with additional blocks and items. Since I believe there are drastically more of these than vanilla servers out there, at least when it comes to public Internet-facing servers, this is a significant design limitation inherent to this feature.

Also, I appreciate you taking the time to understand where I am coming from with this request.

Daniel 2012-12-24T09:36:23Z

OK, so to sum it up, we agree on what type of issue this is and that it should be fixed.
The misunderstanding came up because Mojira currently does not use other issue types than "Bug".

So @Mojang: Please add "Improvement" and / or "Feature Request" to the list of issue types.
Voting up these issues would show quite clearly what the majority of the players would like to have in the game, not just which bugs they want to see fixed, and is more structured than the forum.
Furthermore different priorities could prevent bugs like MC-4715 to make it into the final versions.

Zuriki 2012-12-24T17:54:01Z

This will only be a problem with the coming official support for HD texture packs. Here is how I would solve the problem:

1. Remove the maximum texture pack download size on servers.
2. Change the message to tell you how big the file is (fetch the size from the server).
3. If the server lies and tells the client the size is 2MB but the file is actually 10MB (and vice versa), the client should block the transfer after 2MB (this is a security issue).

This allows you to transfer texture packs that are 100MB, but gives the player the insight to say "hey, I don't have the bandwidth to download this" and refuse it.

Michael V. Coppola 2012-12-24T18:28:57Z

Sounds good to me, I think those are some solid recommendations Zuriki.

Dratini Zero 2013-01-20T12:41:03Z

As a temporary fix, I could compress your TP just below 10 megs, by using optipng, advpng, and advdef, in two rounds, and then optimizing the archive with advzip.

It is so "small" that it fits as an attachment! (ftb_isabella.zip)

Michael V. Coppola 2013-01-20T17:05:16Z

I hadn't even heard of these utilities before, thanks for the explanation and modified pack!

Talven81 2013-01-29T17:48:43Z

Personal comment, not on behalf of Mojang:

The main reason I was able to find for the 10MB limit was security issues. Large packs could include a virus. I'm not here to debate the "security issue" I'm aware of the security setup of Java that would make this difficult to infect a system, but there you have it.

On the flip side with the coming full release of 1.5 and the native HD support, I would like to see this limit increased as well. The majority of HD packs can reach the 50-150MB range. While compression is an option, it is not lossless compression, which can reduce the quality of the texture.

Martin Stumpf 2013-03-03T16:52:53Z

+1 for Zuriki's fix

Tails 2013-03-17T15:00:17Z

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

dianne estock-annen 2013-03-18T23:36:45Z

I just wanted to mention that this is more important now that texture packs can have animated images and there are so many items at this point that the limit is really restrictive.

Xikage 2013-03-19T00:36:00Z

Agree with the previous comment. This is only going to become an increasingly annoying issue. Need to raise awareness of this to get it fixed.

Michael V. Coppola 2013-03-19T02:30:52Z

Updating for current releases. Should also note that with the increase to texture pack sizes some sort of intelligent caching should be implemented to avoid repeated downloads of the same pack between play sessions.

Zuriki 2013-07-28T02:22:47Z

Whilst this issue can not yet be confirmed for 1.6.x versions - as the system responsible for pushing texture packs has been disabled - it is now a very big issue; or will be if not resolved before the reimplementation of this system.

I would like to reiterate my previous suggestions:
1. Remove the maximum resource pack download size.
2. Change the message to tell you how big the file is (fetch the size from the hosting server).
3. If the server lies and tells the client the size is 2MB but the file is actually 10MB (and vice versa), the client should block the transfer after 2MB (this is a security issue).

kumasasa 2013-08-28T21:05:14Z

Limit increased to 50 MB

Martin Stumpf 2013-08-29T14:45:39Z

Still too low, my server uses a 128x128 FTB texture pack sized 75 MB ...

kumasasa 2013-08-29T15:10:17Z

Why not 1000? We have to draw the line somewhere.

https://twitter.com/Dinnerbone/status/372758096562900992

Michael V. Coppola 2013-08-29T15:51:09Z

Set a 50 MB default ceiling if you wish, but this should really be a tunable/overridable limit for those who wish to utilize larger texture packs. So long as the pack itself is within Minecraft-supported parameters what is the functional need for such a small hard-coded file size limit?

If I am a server admin and I put my texture pack in CloudFront, Akamai, or any other CDN of my choosing it's not as if the texture pack will necessarily take a long time to download (which, to clarify, is burden of the client/server relationship anyway, and should be up to the admin of the server). If it becomes a problem for the client, they can simply choose to not use the advertized texture pack for that server, which is again the burden of the client/server relationship and not Minecraft.

Martin Stumpf 2013-08-29T19:40:07Z

Why have a limit at all?
There's no real reason ...

Absolutely +1 for Coppola

_zombiehunter 2013-08-29T20:07:16Z

@Martin Stumpf:
Yes, absolutely. Why do we need a limit at all? Many packs are larger than 50 MB and if someone wants to use such one for a server, it should be "at own risk", but no stupid limits 😞

dianne estock-annen 2013-08-31T21:41:05Z

I'm adding to the "it's pointless" group for a limit.

I use spigot and was going to use a plugin so people could choose the texture pack size they prefer...

Nathan Gilbert 2013-10-22T23:27:45Z

As 50MB seems quite sufficient for a vanilla pack, I would recommended suggesting to this modding community (eg Forge) for options if this limit is still too low for your needs. I also agree a pack this large shouldn't be downloaded without knowing the size before accepting.

Xikage 2013-10-23T00:05:51Z

I personally have to disagree that 50MB is sufficient even for a vanilla pack, especially now. Once you start considering that resource packs can add new sounds, change sounds, and change the music in particular, you can get over 50MB very easily.

One of my vanilla resource packs is sitting at 65MB and this is mainly due to the addition of new sounds and music. If music in resource packs is a supported feature, then it should be fully supported.

I'd also like to add that not even the default Minecraft assets are under 50MB (it's sitting at 87MB on my harddrive, unzipped at least).

Gunni 2013-10-23T04:42:43Z

I do not agree that there should be a pre-set limit.

The client should be prompted when there is a resource pack offered.

"There is a resource pack named x being offered by the server. It is y MiB.
Do you want to download it?"
Yes / No

And then display a nice progress bar if yes is clicked.

Why not?

Steven Valenski 2013-10-23T05:00:41Z

or even something in your user profile before start up that allows you to limit the packs to a size you manually enter or not at all

edit: never mind didn't see the fixed tag

Jakub Hlusička 2014-07-11T11:50:29Z

50 MB is still not enough. You don't have to draw a line anywhere. It'd be nice if Minecraft informed the player of the texturepack size.