The six title-screen panorama faces were 4096×4096, 110 MB in total, about 90% of every mod jar. Each jar was 121.7 MB per Minecraft version. That caused three problems:
The release workflow's upload was rejected with 413 Payload Too Large. The Cloudflare tunnel in front of git.selimaj.dev caps uploads at 100 MB.
Every player downloaded 120+ MB per version.
The panorama took about 400 MB of GPU memory on the title screen (6 × 4096² × 4 bytes).
Change
The faces are resized to 2048×2048 with macOS sips (aspect ratio kept). Vanilla uses 1024×1024; 2048 stays sharp on 1440p and 4K screens, where a face spans roughly the screen width. File names and paths are unchanged, so no code changes are needed.
Before
After
Panorama total
110 MB
33.5 MB
Mod jar (1.21.11)
121.7 MB
45.3 MB
Panorama GPU memory
~400 MB
~100 MB
The 4096 originals remain in git history.
Testing
:mc-1.21.11:remapJar builds, and the jar is 45.3 MB, under the 100 MB upload limit.
Visually checked a downscaled face (panorama_0): detail is intact, with no banding or artifacts.
Not checked in game: the rendered title screen. The panorama code is unchanged; only the texture resolution differs.
Follow-up
After merging, a saturnclient PR will bump common and switch the release workflow's uploads back from http://gitea:3000 (unreachable from the job container) to the public URL.
## Problem
The six title-screen panorama faces were **4096×4096, 110 MB in total, about 90% of every mod jar**. Each jar was **121.7 MB** per Minecraft version. That caused three problems:
- The release workflow's upload was rejected with `413 Payload Too Large`. The Cloudflare tunnel in front of `git.selimaj.dev` caps uploads at 100 MB.
- Every player downloaded 120+ MB per version.
- The panorama took about 400 MB of GPU memory on the title screen (6 × 4096² × 4 bytes).
## Change
The faces are resized to **2048×2048** with macOS `sips` (aspect ratio kept). Vanilla uses 1024×1024; 2048 stays sharp on 1440p and 4K screens, where a face spans roughly the screen width. File names and paths are unchanged, so no code changes are needed.
| | Before | After |
| --- | --- | --- |
| Panorama total | 110 MB | 33.5 MB |
| Mod jar (1.21.11) | 121.7 MB | **45.3 MB** |
| Panorama GPU memory | ~400 MB | ~100 MB |
The 4096 originals remain in git history.
## Testing
- `:mc-1.21.11:remapJar` builds, and the jar is 45.3 MB, under the 100 MB upload limit.
- Visually checked a downscaled face (`panorama_0`): detail is intact, with no banding or artifacts.
- **Not checked in game:** the rendered title screen. The panorama code is unchanged; only the texture resolution differs.
## Follow-up
After merging, a saturnclient PR will bump `common` and switch the release workflow's uploads back from `http://gitea:3000` (unreachable from the job container) to the public URL.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The six 4096x4096 faces were 110 MB, about 90% of every mod jar
(121.7 MB per Minecraft version). That exceeded the 100 MB upload limit
in front of git.selimaj.dev, made every download huge, and cost ~400 MB
of GPU memory on the title screen. At 2048x2048 they're 33.5 MB (jar
~45 MB, ~100 MB GPU memory) and still sharp on 1440p/4K screens.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
The six title-screen panorama faces were 4096×4096, 110 MB in total, about 90% of every mod jar. Each jar was 121.7 MB per Minecraft version. That caused three problems:
413 Payload Too Large. The Cloudflare tunnel in front ofgit.selimaj.devcaps uploads at 100 MB.Change
The faces are resized to 2048×2048 with macOS
sips(aspect ratio kept). Vanilla uses 1024×1024; 2048 stays sharp on 1440p and 4K screens, where a face spans roughly the screen width. File names and paths are unchanged, so no code changes are needed.The 4096 originals remain in git history.
Testing
:mc-1.21.11:remapJarbuilds, and the jar is 45.3 MB, under the 100 MB upload limit.panorama_0): detail is intact, with no banding or artifacts.Follow-up
After merging, a saturnclient PR will bump
commonand switch the release workflow's uploads back fromhttp://gitea:3000(unreachable from the job container) to the public URL.🤖 Generated with Claude Code