Sky Factory 3 tpisland broken

  • 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
V

vsbmeza

Guest
Title Sky Factory 3 tpisland broken

Launcher Type Server

Modpack Sky Factory 3

Modpack version 3.0.7

Have you modified the pack? Yes

Link to log file

Details of the issue I have sponge + luckyperms + griefprevention + nucleus + enjin installed

The same setup worked perfectly with 3.0.6

Now after the update, the /tpisland command has no autocomplete, and when issued with a player, this is what happens:

http://pastebin.com/rdeCt3Ji
 
Last edited by a moderator:
V

vsbmeza

Guest
So apparently the update overrides the islands.json, and I'm not sure how to fix it. I've replaced it from backup, but it gets overriden
 

grandrolf

Global moderator
Team Member
Global Moderator
Trusted User
Aug 29, 2014
2,658
246
133
sweden
How did you do the update (did you remove the folder config and replace it with new?
(if yes, you need to put islands.json back from your backups, or just leave it there)

How did you replace it?
(did you stop the server first and then replace the file?)
 
V

vsbmeza

Guest
Yeah, apparently the way the mod works has changed, and since there were no changelogs with this version, it was hard to know.
Apparently the island.json now lives in the config folder (which is odd, given it's world specific), and at every boot, it overwrites the one in the world save folder.

So me replacing the one in the world folder wasn't enough, I had to overwrite the one in the config folder.
 

grandrolf

Global moderator
Team Member
Global Moderator
Trusted User
Aug 29, 2014
2,658
246
133
sweden
It's always been in the config folder, I did the same thing when I updated first time.

But I agree, it shouldn't be located there.

But you've solved the issue, right?