Zombie Invade 100 Days Server Hosting

It depends on the run you want. A flat or superflat world gives you the village-fortress style the 100 Days format is known for, with clear sightlines and defence as the main problem. A normal world gives you terrain, caves and more places to hide. The choice is made at world creation through the datapack screen and cannot be changed afterwards, so decide as a group first.

No, they generate in the overworld by default on current versions. Older guides that tell you to turn them on are out of date, and following them can cause problems rather than fix any. If you want them off instead, the Lost Cities configuration has profile settings where removing the overworld entry stops them generating, and that also lightens the server noticeably.

6 GB for a group of around six. At roughly 129 entries this is a mid-weight pack, but the cost profile is unusual: ruined city chunks are dense and full of loot containers, so the areas your players actually spend time in are much heavier than open terrain. That is where the memory goes rather than into a large mod list.

At world creation, through the datapack screen, rather than afterwards. The pack ships optional datapacks that extend the apocalypse into the Nether and the End and that add horde nights. Because they are applied when the world is made, adding them later is not the intended route, so decide whether your group wants the harder run before you generate the world.

Yes. The pack originates from a Chinese-speaking creator and its documentation is written in Simplified Chinese first, but the pack itself plays in whatever language your client is set to, and the in-game wilderness handbook guides you regardless. The practical effect is that you may need to work a little harder to find setup answers, which is part of why this page exists.

Back up first, and be more careful than usual. This pack has changed its core zombie mod between major versions, and the world type and datapack choices are baked in when the world is created, so a jump between major versions can behave unpredictably on an existing save. Staying on one build for the length of a hundred-day run is the simplest approach.