No Render

Cuts rendering work while a macro runs, from limiting nearby terrain to a blank screen with only the Macro HUD, plus an FPS cap.

No Render cuts how much Minecraft draws while a Polinex macro controls your character, which saves CPU and GPU during long sessions. You can keep only nearby blocks visible or blank the screen entirely and keep just the Macro HUD.

Nearby Blocks sets how much terrain stays rendered. Blank Screen stops world and HUD rendering, and Show Macro HUD keeps your stats in view. Hide HUD, Hide Particles, Hide Entity Models and Hide Client Rendering each strip more away. FPS Cap limits frame rate unless you choose Uncapped FPS, and Free Memory releases cached sounds and unused memory while No Render is active.

Settings 10

Shown at their defaults
  • Blank Screen

    Stops rendering the world and HUD entirely, leaving a black screen.

  • Show Macro HUD

    Keeps the Macro HUD while the rest of the HUD is hidden (Blank Screen or Hide HUD).

  • Free Memory

    Frees cached sounds and makes Java hand unused memory back to the OS while No Render is active. With Blank Screen also drops chunk meshes and particles. Short hitch at macro start.

  • Uncapped FPS

    Lifts the FPS cap No Render applies.

  • FPS Cap

    Max FPS while No Render is active. Your own limit still applies if it's lower.

  • Nearby Blocks

    Blocks around you to keep rendered while No Render is active. Rounded up to chunk distance. 0 hides all blocks.

  • Hide Entity Models

    Stops world entity models from rendering while No Render is active.

  • Hide Client Rendering

    Stops Polinex render events, ESPs, overlays and post-render effects while No Render is active.

Included with Polinex. See packages

All features