Performance & best settings
DrAyriAddons itself is small and GPU-light. The Fabric stack you load it into is what actually moves your framerate. Here is the setup we recommend.
How much does DrAyriAddons cost in FPS?
On a mid-range GPU (RTX 3060 / RX 6600) running vanilla 1.21 + Fabric Loader, enabling all modules costs roughly 2–5 FPS compared to Fabric without DrAyriAddons. Most of that comes from the HUD, not the scanners. With Sodium installed, the absolute frame budget is high enough that the cost is barely measurable.
Recommended Fabric performance stack
- Sodium — the single biggest FPS gain on 1.21. Required.
- Lithium — CPU-side optimisations for entity ticks and pathfinding.
- Iris — shader compatibility. Skip if you don't use shaders.
- Indium — needed when running Sodium together with mods that use the Fabric Rendering API.
- FerriteCore — lower RAM usage for big modpacks.
- EntityCulling — skips rendering for entities behind walls.
Install all of those alongside DrAyriAddons and you'll outperform vanilla 1.21 even with the HUD enabled.
RAM allocation
| Setup | Recommended RAM |
|---|---|
| Vanilla 1.21 + DrAyriAddons | 4 GB |
| + Sodium + Lithium | 4 GB |
| + Iris + medium shaders | 6 GB |
| + Iris + heavy shaders (BSL, Complementary) | 8 GB |
Set this in the Minecraft launcher under Installations → Edit → More options → JVM arguments. Look for -Xmx4G and adjust the number.
Best in-game settings
Low-end laptops (integrated GPU)
- Render distance: 8 chunks
- Simulation distance: 6 chunks
- Graphics: Fast
- Smooth lighting: Minimum
- Particles: Decreased
- Sodium → Performance preset
Mid-range desktops
- Render distance: 16 chunks
- Simulation distance: 10 chunks
- Graphics: Fancy
- Sodium → Balanced preset
High-end desktops
- Render distance: 24–32 chunks
- Simulation distance: 12 chunks
- Graphics: Fabulous
- Iris with Complementary shaders
- Sodium → Quality preset
BaseFinder and your CPU
BaseFinder is the only DrAyriAddons module that touches your CPU in a measurable way, because it scans surrounding chunks on a background thread. If your CPU is a bottleneck (older 4-core laptop chips), raise the Scan Interval in the BaseFinder config from 20 to 60 ticks. You'll still get useful pings without the per-tick cost.