Age of Engineering server crashes when starting up with a world is already available

  • Tech Support section is for getting help with FTB related problems. If there's a repeatable issue that can be labeled as a bug, then please use the issue tracker for the pack or the app at GitHub issue trackers - If there's no repository for a pack that means that the pack is old and/or will not be updated. Bugs for older packs will not be fixed, unless they are critical.
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
P

PorcoDio4316

Guest
Title Age of Engineering server crashes when starting up with a world is already available

Launcher Type Twitch Desktop App

Modpack Age of Engineering

Modpack version 1.1.2

Have you modified the pack? No

Link to log file https://pastebin.com/raw/MHkBnV8H

Details of the issue So I've tried settings up a server for age of engineering by downloading the right version of forge, launching the jar and installing the server in a folder and then copying the "mods", "configs" and "scripts" folders from my AoE installatrion to the server folder.

This is because there's no ready-to-use server for AoE. You have to create it yourself.

It was working at first but when we restarted the server it crashed on startup.

So thought about deleting the "world" folder and that worked, the server was starting up correctly. But then again, restarting the server made it crash again.

It looks like the server is fine when creating a new world but can't load one.
 
Last edited by a moderator:

grandrolf

Global moderator
Team Member
Global Moderator
Trusted User
Aug 29, 2014
2,658
246
133
sweden
You're also using a server wrapper "Multicraft" - first make sure you get the server run on your local machine, and then upload to the multicraft server
(If it works on your local machine with restarts without crashing, then you know the issue is Multicraft, and you can focus on fixing that - and if the issue is still there when you run in local - then you know the issue is with the server pack you made)

Post new log and explain what you tried/did if you need more help.