
Wiki · Servers & help
Performance
Make Lunchtime run smoothly: the right Java, how much memory to give it, which settings matter most, shaders, stutter and server lag.
For Lunchtime v2.5.1 · Minecraft 1.20.1
Lunchtime is a big pack, with 338 mods, and it already ships with the performance mods it needs: Embeddium, ModernFix, FerriteCore, Entity Culling, ImmediatelyFast, Radium Re-Reforged, Create: LazyTick and more. You don't need to add any. Extra optimisation mods or Java flags copied from other guides can clash with the ones already in the pack.
If the game feels slow, start with the quick reference, then read the section that fits. For crashes and errors, see Troubleshooting.
Java
Minecraft 1.20.1 with Forge 47.4.29 runs on Java 17, 64-bit. A wrong or 32-bit Java can stop the game from starting, or limit how much memory it can use.
Most players don't need to do anything. The CurseForge app installs a matching Java for the game automatically, and Prism Launcher can detect or download the right one for you.
Check which Java the game uses
In game, press F3. The top right of the debug screen shows the Java version, for example Java: 17.0.13 64bit. To check the Java installed on your computer, run java -version in Command Prompt or Terminal.
Install Java 17 yourself
You only need this if your launcher can't find Java 17. Download Eclipse Temurin 17 from adoptium.net:
- Windows: the x64
.msiinstaller. - macOS: the
.pkg, aarch64 for Apple Silicon (M1 and newer) or x64 for Intel. - Linux: your distribution's Java 17 package, or Adoptium's installation guide.
Choose Java in Prism Launcher
- Open Prism's Settings → Java. Keep Autodetect Java version and Auto-download Mojang Java turned on; Prism then picks or downloads the right Java when you launch. (Prism's Java settings guide)
- To set it for Lunchtime only: select the instance, choose Edit → Settings → Java, tick the Java installation option, choose Auto-detect and pick a Java 17 entry.
Choose Java in the CurseForge app
The CurseForge app installs and uses the right Java on its own. If you need a different one, open Settings → Game Specific → Minecraft and use Java Versions further down the page to choose a Java 17 program.
Memory (RAM)
Give Lunchtime 8,000 MB (about 8 GB). That's the recommendation in the pack's own CurseForge manifest. Most launchers start at 4 GB, which isn't enough for a pack this size.
Allocated memory isn't the same as your computer's RAM
Your computer's system RAM is all the memory it has, shared by everything you run. Allocated memory is the slice you let Minecraft use. Your system, the launcher, your browser and Discord all need memory too, so never give Minecraft all of it.
| Your system RAM | Give Lunchtime | Left for everything else |
|---|---|---|
| 8 GB | Below the recommendation. Try 6 GB, shaders off, lower distances | About 2 GB, which is tight |
| 16 GB | 8 GB (recommended) | About 8 GB |
| 32 GB or more | 8 to 10 GB | Plenty |
So 16 GB of system RAM is the comfortable minimum for Lunchtime. On a Mac with Apple Silicon, graphics share that same memory, so leave a little more room than you would on a PC with its own graphics card.
Change it in Prism Launcher
- Select the Lunchtime instance and choose Edit.
- Open Settings → Java and tick Memory.
- Set Maximum memory allocation to
8000MiB and save. You can leave the minimum as it is.
Change it in the CurseForge app
- Open Settings (the gear) → Game Specific → Minecraft.
- Under Java Settings, move Allocated Memory to about 8,000 MB.
- To set it for Lunchtime only, open the profile, choose the ⋯ menu → Profile Options, and change the memory there instead.
The CurseForge app warns you if you go above 75% of your system RAM. Restart the game completely after changing memory.
Signs of too little memory
- The game freezes for a moment every few seconds, and it gets worse the longer you play.
- The memory figure on the F3 screen sits near 100%.
- The game closes or crashes with
java.lang.OutOfMemoryErrorin the log.
Problems with too much memory
- Your whole computer slows down, because other programs are left without memory.
- Longer pauses. Above about 10 GB, Java's memory clean-up pauses can get longer and cause stutter instead of fixing it.
FPS settings
Your settings are in Options → Video Settings. Embeddium replaces that screen with its own, split into a few pages; the settings below are all there. Change one setting at a time and test in the same place in the same world. Exploring new terrain makes the game generate chunks, which isn't a fair comparison.
The biggest differences come from shaders, render distance, simulation distance and entity distance. The rest help a little each.
| Setting | Lunchtime default | Impact | On a slower computer |
|---|---|---|---|
| Shaders | Off | Biggest | Keep them off (see Shaders) |
| Render distance | 10 chunks | Big | 6 to 8 chunks |
| Simulation distance | 8 chunks | Big for lag around Create machines and farms | 5 to 6 chunks |
| Entity distance | 100% | Medium, more in busy bases | 50 to 75% |
| Graphics | Fancy | Medium | Fast |
| Particles | All | Medium in busy scenes | Decreased |
| Clouds | On | Small | Off |
| Mipmap levels | 4 | Small | Lower it if textures load slowly |
| VSync | On | Caps FPS at your screen's refresh rate | Off can raise FPS but may cause tearing |
| Max framerate | 120 | Caps FPS | Set it near your screen's refresh rate so the game doesn't waste power |
| Resource packs | The pack's own set | Small, unless you add high-resolution packs | Don't add extra high-resolution packs |
Simulation distance is about how far the world keeps running, not how far you can see. Lowering it helps most when machines, farms and mobs make the game lag even though your FPS counter looks fine.
Shaders and resource packs
Shaders are optional and off by default. Lunchtime includes Oculus, which runs shader packs on top of Embeddium, and ships with two shader packs: Complementary Reimagined and Miniature Shader.
- Open Options → Video Settings → Shader Packs.
- Pick a shader pack and choose Apply. The same screen has the button that turns shaders on and off.
Shaders can cost more FPS than every other setting together. On a slower computer:
- Try them only after the game runs well without them.
- In the shader pack's own settings, pick a lower quality profile and lower the shadow distance. Lunchtime already sets the shadow distance to 6 chunks.
- Turn shaders off completely whenever you're troubleshooting.
Lunchtime also turns on a set of resource packs that are part of its look. They're light, normal-resolution packs. Adding your own high-resolution packs on top uses more memory and makes loading slower.
Stuttering and long loading
- Let it finish loading. The first launch after installing or updating takes the longest. Wait at the main menu until everything has loaded, and give a new world a moment to settle after you join.
- Close background apps. Browsers, video calls, screen recorders and other games all compete for memory and graphics power.
- Check your free memory. If your computer is short of memory, see Memory.
- Exploring new terrain makes the game generate chunks, which causes stutter, especially with Lunchtime's world and structure mods. Go back to an area you've already explored and compare, or lower render distance while you travel.
- Big bases and old worlds with many Create contraptions, farms, animals or dropped items cost more every tick. Lower simulation distance, and gather up dropped items.
- Too many extra resource packs make loading longer and use more memory.
Windows and Linux: graphics drivers
Keep your graphics drivers up to date from NVIDIA, AMD or Intel. On a laptop with two graphics chips, make sure Minecraft's Java uses the dedicated one: on Windows, open Settings → System → Display → Graphics, add javaw.exe and set it to High performance. On Linux, use your distribution's recommended drivers.
Macs with Apple Silicon
Graphics on Apple Silicon Macs come with macOS, so there's nothing separate to install. Keep macOS up to date, plug in your MacBook while you play, and turn off Low Power Mode (System Settings → Battery) because it slows the game down. Use a native arm64 Java (aarch64), which the CurseForge app and Prism Launcher pick by default.
Multiplayer and servers
Three different things are called "lag", and each has a different fix:
| Name | What it is | What you notice |
|---|---|---|
| FPS | Frames your own computer draws each second | Choppy movement on your screen. Only you have it |
| TPS | Ticks the server runs each second. 20 is full speed | Everyone sees machines slow down, mobs jump and blocks reappear |
| Ping | How long data takes to reach the server and back | Your actions arrive late or snap back. Worse the farther you are from the server |
If only you have the problem and your FPS counter is low, change your own settings. If everyone has it, it's the server.
For server owners
- Memory: 6 to 8 GB is a reasonable start for a small group. It's set in
variables.txt; see Server setup. - Distances: in
server.properties, tryview-distance=8andsimulation-distance=6, then adjust for your group. - Entity buildup: big mob farms, crowded animal pens and piles of dropped items cost the server every tick. Keep farms tidy and collect dropped items.
- New terrain: generating chunks is the heaviest thing a server does. The pack includes Chunky, so you can pre-generate the area around spawn while nobody's online. Back up the world first.
- Find the cause: the pack includes spark. Run
/spark tpsto see the server's TPS, or/spark profiler start --timeout 120while the lag is happening. After two minutes spark gives you a link that shows which mod or machine is using the time.
/chunky center 0 0
/chunky radius 3000
/chunky start
Replace 0 0 with your spawn's X and Z.
Quick reference
These are good first things to try, not a guaranteed fix. To find the real cause, change one thing at a time and test in the same place, and use spark (/spark profiler) to see what's actually slow.
| Problem | Likely cause | What to try |
|---|---|---|
| Low FPS | Shaders, long render distance, busy scenes | Shaders off, render distance 6 to 8, entity distance 50 to 75%, particles Decreased |
| Stuttering | Too little memory, new chunks generating, background apps | Allocate 8,000 MB, close other apps, compare in an explored area |
| Long loading | First launch after an update, extra resource packs, slow drive | Wait for the first load to finish, remove packs you added yourself |
| High memory use | Normal for a big pack, or too little allocated | Allocate 8,000 MB; if F3 stays near 100%, see Memory |
| Multiplayer rubber-banding | Low server TPS or high ping | Ask if others have it, check /spark tps, lower the server's simulation distance |
| Shader lag | Shader quality and shadows | Lower the shader profile and shadow distance, or turn shaders off |
Still slow? Ask on Discord with your spark link, or see Troubleshooting.