
Team Sync issues in SevTech
TexanMD opened this issue ยท 28 comments
I'm having issues on a private server with 2 users.
If I'm on the server alone, my advancements work fine. As soon as my teammate joins the server, I can no longer unlock any advancements, but when my teammate unlocks them we both get them.
I've attempted the following issues with no change:
- leaving the team (I still can't get them)
- disbanding the team and reforming it
- switching which account creates the team
- kicking the other team member out
On all of the above I'm left unable to do any advancements while the other person is on the server.
I see nothing that looks useful info in the server or client logs, but can provide if you'd like. I'm a developer (but not minecraft mods) and Darkosto mentioned seeing what I can do to help out. If you have a debug build or some other way I can create more detailed data to help debug please let me know.
Sorry, should have mentioned, I have done that. Our advancements don't appear to be out of sync... but I cannot unlock them with both of us on the server.
And just in case it comes up, I'm on SevTech 3.0.6 and my TF is togetherforever-1.12.2-1.0.7-13.jar
I have added a ton of debug, try to replicate the issue and get me the logs if possible.
togetherforever-1.12.2-1.0.7.jar.zip
Logs attached. Logs.zip
Server is the server
TexanMD is my account which cannot seem to get advancements
Mylen is the account which does get them
Thinking through this test it seems maybe its an issue with the Advancements and not synchronization of them, but will have to find a way to do more testing.
I logged Texan in, created a channel which should have triggered an advancement, nothing happened. I dropped it on the ground and picked it up, nothing happened.
I then logged Mylen in and had Texan drop the item on the ground where Mylen would pick it up. That triggered the Advancement for both of us.
I then logged both accounts out, and exited the clients and shutdown the server.
The latest.log that you gave me starts at [00:07:46] and ends at [22:29:56] which it should not be possible
sigh Sorry. Those were the server logs from before I added it. Grabbed the wrong zip. Correct logs attached.
Those logs show me that it literally doesnt trigger for you, like the event doesnt exist for you.
The advancements that you need to complete show as 1/2 steps completed in the name in your side?
Yeah they do. I looked through the advancements log json for both players and they seem to be identical (minus some time stamp variations)
Thats definitely causing my issue. Just managed to complete two different advancements that involved breaking or placing blocks that i never could previously
Exactly. Both the dung (stage 1) and lapis (stage 2) advancements wouldn't work for me. I de-op'd myself and re-logged and both worked when I placed / broke the required block
Now as a final test I added more debug, can you try the same issue with OP
togetherforever-1.12.2-1.0.7.jar.zip
Yep. Give me a couple minutes. I'll revert the server to the same state as the last test too
Here are the server logs, are you interested in the player logs? I forgot to purge the directory before hand and will need to compress them more before github will let me upload them
Got the client logs to work:
ClientLogs.zip
Player logs arent helpful as everything goes server side, the advancement didnt trigger for you either this time?
Correct, but did for Mylen. I crafted the channel, dropped it, picked it up and attempted to place the dung pipe. Then logged Mylen in, tossed both over and placed the dung pipe. The channel one fired on pickup for Mylen
TBH, I dont know how to fix it because there isn't even an event fired for you, if not having OP works, I will go with that.
Yeah I think we can close this. It definitely looks like the events are syncing... I'll have to dig in more on why they aren't firing for me.
Its not a you case, it happened for some people too, but its very hard to find where the issue
Yeah. Really appreciate your help with the custom builds. Later on I have one other idea I might try. I'm getting my server pack from AT Launcher which I just realized is not the same as the server pack from Curse.
I'm taking a wild guess that there could be some difference there that causes the issue to manifest on ATLauncher servers and not Curse servers