Blightfall Minecraft server setup

Blightfall is a Minecraft 1.7.10 challenge pack by Talonos, tagged Adventure, Challenge Map and Thaumcraft on Technic and described there as questing, adventure and exploration. Its Technic description asks if you can survive on the blighted planet. The pack lives on Technic, and its author publishes a ready-to-run server download there. The Modpacks tab installs that download through its Technic search source.

Checked against Blightfall 3.1.1-CE on Minecraft 1.7.10, October 2026.

What the pack needs

• Minecraft 1.7.10 with Forge. The server download carries its own launch jar, Blightfall.jar, which is a Forge 1.7.10 build, plus the Minecraft 1.7.10 server jar. Java 8 is what 1.7.10 needs, and the panel selects it from the pack's version.
• Memory. The pack's start script asks for 2 GB at the start and 3 GB at most. The panel ignores that script, writes its own and sizes the memory from your plan, so how much RAM a Minecraft server needs is the guide to read when you pick one.
• Matching clients. Every player installs Blightfall 3.1.1-CE, which Technic serves through the Technic launcher.

Install the pack

1. Open your server and choose Modpacks under Content in the left rail.
2. In the source chip row at the top of the tab, press Technic and search for Blightfall.
3. Press Install on Blightfall. A pack without a server download shows No server download instead, and this one has one. The popup should read Forge, Minecraft 1.7.10.
4. Keep Take a backup first ticked. The server download includes its own world folder, so your current world is replaced. If the popup shows Keep my world, settings and player lists, tick it to keep your own world instead. If it shows a note about your world's Minecraft version in its place, your world is newer than the pack (1.7.10) and cannot be kept: the pack starts a fresh world and your old one stays in the backup. Tick Start the server when it's ready if you want it to start by itself.
5. Press and hold Hold to Install and reinstall for 3 seconds. A plain press does nothing.

The panel downloads the pack's server zip, unpacks it, and finds the launch jar from the pack's own start script. The pack's script is not used to launch the server: the panel writes its own.

Once the install finishes, the Modpacks tab shows the pack as installed, with a Remove modpack button. The tab notes that a modpack isn't permanent and can be removed any time to go back to a normal server.

First start

The pack's server.properties sets level-type=TERRAIN_CONTROL. Do not change World type in the Config Editor.

Common problems

• Mod mismatch on join. The player's build differs from 3.1.1-CE. Update the client, or reinstall the pack there.
• The install window says "The backup didn't start, so nothing was changed". The window stays open, and the alert under that title gives the reason. If it is the game panel's limit on backups in 10 minutes, wait as long as it says, then hold Install and reinstall again. If every backup is protected or you are at your backup limit, open the Backups tab and delete a backup you no longer need, or remove the protection from one. Only the newest install backup stays protected: taking the next one lifts the protection from the earlier ones, so installs in a row no longer fill the slots. A backup you protected yourself keeps its protection. You can also untick Take a backup first and install without one, unless the window shows a note about your world: then the backup is required.
• The install says Technic has no server download. The pack's author may have changed or removed the link, or Technic did not answer. Nothing on your server changed, because the panel checks the download before it clears anything. Try again in a few minutes.