How to Host a VerityPack Server (Forge 1.20.1 Setup Guide)
VerityPack takes the same Verity AI horror mod found in VerityCraft and wraps it in high-FPS and quality-of-life mods — it's the performance-tuned build of the same horror experience, not a different concept. Hosting it right on Forge 1.20.1 comes down to starting with enough RAM, importing the server pack cleanly, and confirming a clean first boot before anyone connects.
Start with at least 8 GB of RAM allocated to the server process — that's VerityPack's own recommended floor for running Verity's AI horror logic alongside the high-FPS and quality-of-life mods wrapped around it on Forge 1.20.1. Going lower risks stutters right when Verity is active, which is the worst possible moment for lag.
Import the VerityPack server files directly from a Forge 1.20.1 modpack source instead of guessing from a client-side export — mismatched mod versions between client and server are the most common cause of Verity behaving incorrectly or not spawning at all.
Watch the console on first boot until the world finishes generating and every Forge mod reports loaded with no missing dependency errors — Verity's AI and the performance/QoL mods layered around it need a clean first load to register correctly.
Only invite players in after you've confirmed that clean first startup. Letting people connect mid-load is how you end up troubleshooting a Verity encounter and a half-loaded mod list at the same time.
Take a backup before importing an existing world, updating the Forge loader, or touching any mod configs. VerityPack's horror pacing depends on persistent world state, and a bad config edit can corrupt a save you won't get back.
Use a cleaner VerityPack path
CoalHost is built around modpack hosting, which makes VerityPack much less annoying to launch correctly.
Deploy VerityPack now →