Brotato: Best config.json for Wave 50+ Performance

The primary goal for Brotato performance is Data-Point Culling. The game’s default settings keep every damage number and particle effect in the render pipeline, even if they are set to 0% opacity. This configuration focuses on disabling the Damage Numbers and Visual Effects entirely, while leveraging the “Optimize End of Wave” logic added in version 1.1.9 to prevent crashes during item collection.

File Path

Brotato stores its configuration and save data in a subfolder named after your Steam/User ID.

%AppData%\Roaming\Brotato\[Your_ID]\save_v2.json

(Note: If you are using mods like “Configurator,” you may also have specific files in %AppData%\Brotato\mod_config\).

Technical Configuration (The 2026 “Wave-Breaker” Template)

Open save_v2.json in a text editor (like VS Code or Notepad++). Search for the settings or options block and ensure these specific values are set to minimize CPU interrupts:

{
  "options": {
    "show_damage_numbers": false,
    "explosion_opacity": 0.0,
    "vfx_opacity": 0.0,
    "optimize_end_of_wave": true,
    "max_fps": 60,
    "screen_shake": 0.0,
    "projectile_outlines": true
  }
}

Parameter Breakdown:

• show_damage_numbers=false: In Wave 50+, you are dealing damage to hundreds of enemies simultaneously. Calculating the floating text for each hit is the #1 cause of frame drops.
• explosion_opacity=0.0: Even at 1% opacity, the engine still processes the alpha-blending. Setting it to 0.0 in the JSON helps the renderer bypass the call more efficiently.
• optimize_end_of_wave=true: This is a native feature that bundles material and fruit collection into a single calculation rather than individual “magnetic” paths, preventing the 5-second freeze at the end of late-game waves.
• max_fps=60: Do not play Brotato at 144Hz in Endless mode. Capping the game at 60 FPS gives your CPU more “headroom” between frames to handle the escalating physics calculations.
• projectile_outlines=true: Since you are turning off VFX, keep outlines on. This allows you to see enemy bullets through the “brown soup” of thousands of enemies without needing the laggy glow effects.

Strategy for 2026 Endless Stability

• The “Fruit Lag” Solution: High Luck stats generate thousands of fruits. If you have high Pickup Range, these will all rush toward you at the end of the wave, crashing the game. Focus on killing elites quickly so the wave ends before the floor is entirely covered in materials.
• Weapon Selection (CPU-Friendly): In 2026, the laggiest weapons are those with infinite bounce and pierce, like the Sniper Gun. For Wave 50+, Aura weapons or high-damage single-target weapons (like Excalibur or Potato Thrower) are much “lighter” on the engine than Baby with a Beard or Ricochet builds.
• Avoid Turrets: In late-game Endless, turrets and “Gardens” create massive overhead because each one acts as an independent “AI” entity. For a lag-free run, focus on the “Potato” himself rather than a mechanical army.
• Steam Beta Branch: If you are still stuttering, right-click Brotato in Steam > Properties > Betas and opt into the “Beta” branch. The developers often test immaculate performance patches here that fix endless-run memory leaks months before the main branch.

Key Stability Parameters

Parameter	Recommended Value	Impact
Damage Numbers	OFF	Prevents CPU-hitches during “Critical Hit” chains.
Explosion Opacity	0%	Essential for Nuke Launcher or Precision builds.
Pickup Range	High	Minimizes the time materials stay on the floor.
Screen Shake	0%	Prevents camera-logic lag during massive explosions.

Frequently Asked Questions (FAQ)

Conclusion and Expected Results

By manually forcing show_damage_numbers=false and explosion_opacity=0.0 in your save_v2.json, you are stripping away the visual clutter that chokes the CPU. You can expect a much smoother frame-rate in the final 30 seconds of a wave, instantaneous material collection, and the ability to push into Wave 100+ without the game crashing.