Skip to content

misosoupTgit/NoRespLoadFix

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

NoRespLoadFix

A client-side Minecraft mod (Fabric / Forge / NeoForge) that prevents Windows from showing the "Not Responding" dialog during high-load operations such as modpack startup, texture reloading, world loading, and language loading.

Compared to the legacy edition, the features themselves have not evolved. What changed is the toolchain: combining Architectury API with Stonecutter made multi-version and multi-loader support far easier, which in turn makes active ongoing development practical.

How It Works

Uses DisableProcessWindowsGhosting() — a Win32 API provided by Microsoft for exactly this use case — to permanently disable OS-level window ghosting for the process. Where available, this is applied early (e.g. via Forge/NeoForge ITransformationService or Fabric preLaunch) before most Minecraft code runs — including the early loading window — so coverage starts as soon as possible.

A secondary heartbeat thread (PostMessage(WM_NULL)) runs as a lightweight fallback throughout the game session.

Layers of Protection

Layer Mechanism When Applied
1 (Primary) DisableProcessWindowsGhosting() Before the loading window appears
2 (Fallback) PostMessage(WM_NULL) thread From client setup until shutdown

Compatibility

  • Does not call any GLFW functions from background threads
  • Does not hook WindowProc or intercept messages
  • Compatible with Embeddium(Rubidium), ModernFix ...etc optimization mods

Requirements

  • Minecraft 1.16.5 ~ 26.1.2 Fabric/Forge/NeoForge
  • Architectury API
  • Client-side only

⚠️ Important Considerations

Masking Real Issues

This mod works by deceiving the Windows OS about the process responsiveness using heartbeat signals (PostMessage(WM_NULL)). While this prevents false "Not Responding" dialogs during legitimate high-load operations, it has a critical drawback:

If a genuine crash, hang, or serious problem occurs, you may not notice it immediately. The mod will continue to report the process as "alive" to Windows, potentially delaying your awareness of actual issues.

Recommendation

  • Stable Modpacks: Safe to use. If your modpack is already well-optimized and stable, this mod prevents frustrating false-positive notifications.
  • Unstable/Experimental Configurations: Use with caution. You risk missing early warning signs of real problems. Consider monitoring logs actively and watching for actual freezes or performance degradation rather than relying on the OS dialog to alert you.
  • Development/Testing: Not recommended. You want immediate feedback when something breaks.

Best Practice

Use this mod only in well-tested, stable configurations where you're confident the underlying modpack is functioning correctly. Do not rely on it as a substitute for proper troubleshooting in problematic setups.