Fix Ago ModLauncher Connectivity
Budget: $10 – $100 USD
My Wurm dedicated server on Windows Server 2022 launches fine, shows up online, and is fully playable—until I drop the latest version of Ago ModLauncher into the mix. With Ago enabled the console says the server is running, no errors appear in the logs, yet the world never becomes visible to players.
Environment at a glance:
• Ago ModLauncher: latest release
• Java: 8 (fresh install)
• Server config: brand-new, no custom tweaks beyond the vanilla setup
What I need is a clear-cut diagnosis and fix so the server lists publicly and accepts connections while ModLauncher is active. If a clean reinstall is the fastest route, I’m ready for that; otherwise I’m open to any targeted adjustments—be it JVM flags, modloader parameters, or networking quirks unique to Wurm on Windows Server 2022.
Deliverable: a step-by-step set of changes (or a working re-installation) that brings the server online with Ago ModLauncher enabled, confirmed by you and me logging in successfully.
Once it’s stable I’d also appreciate a brief rundown of what caused the conflict so I can avoid it on future updates.
Environment at a glance:
• Ago ModLauncher: latest release
• Java: 8 (fresh install)
• Server config: brand-new, no custom tweaks beyond the vanilla setup
What I need is a clear-cut diagnosis and fix so the server lists publicly and accepts connections while ModLauncher is active. If a clean reinstall is the fastest route, I’m ready for that; otherwise I’m open to any targeted adjustments—be it JVM flags, modloader parameters, or networking quirks unique to Wurm on Windows Server 2022.
Deliverable: a step-by-step set of changes (or a working re-installation) that brings the server online with Ago ModLauncher enabled, confirmed by you and me logging in successfully.
Once it’s stable I’d also appreciate a brief rundown of what caused the conflict so I can avoid it on future updates.