Hardcore Questing Mode [FORGE/FABRIC]

Hardcore Questing Mode [FORGE/FABRIC]

16M Downloads

[1.11.2] Progression not saved

Terpo opened this issue ยท 5 comments

commented

Currently I'm testing the latest 1.11.2 version of hqm (HQM-New Heights-1.11.2-5.1.0alpha3) on a server / client environment.

I'm unable to create a team.
Client log for this: https://gist.github.com/Terpo/8cfea4535157951861620bf09b666b14
Server log for this: Nothin in latest and nothing in forge log at this timestamps

Also, without a team, when I'm finishing a quest and restart the server, all progression is reset.

Config on client:
sync with server: true
no quests when connecting first time

Config on server:
sync with server: true
has all quests

The syncronization itself works

commented

Does your client / server have edit mode on. Even if server has it disabled and client has it enabled. you will be unable to make a team. and visa versa.

commented
commented

I did some more testing with a completly fresh server<->client enviroment.
First: creation of teams does work, but the client has to disconnect and reconnect to the server to get synchronized data. After reconnect the player is in the team.

Second: The problem with not saving does not seem to be a problem of the mod itself, because with just JEI and HQM it is working as intended. All I can say at this point is, that one of my categories or quests is broken and for that, the server can't save the data. I start trying a new quest book on the whole modpack to see if it could be a cross-mod problem.

edit: Tested with my whole modpack and a new book --> everything works.
So this means that somewhere in my 200 quests is a problem with saving. I will try to find out which category works and which not.

One more confirmation: It is not a server<->client problem here. Just switch client to editmode false and tested the first quest. After reloading the world the quest was reset :/.

commented

Wow....I found the issue, finally! When migrating from alpha 2 to alpha 3 for the 1.11 version make sure to delete the old data.json file. This file was causing all my problems so far.