Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does it work with AtLauncher? #310

Open
Xiarno opened this issue Dec 19, 2023 · 3 comments
Open

Does it work with AtLauncher? #310

Xiarno opened this issue Dec 19, 2023 · 3 comments
Labels
bug integration Problems integrating between serversync and other products

Comments

@Xiarno
Copy link

Xiarno commented Dec 19, 2023

Does the sync works with ATLauncher?
By all means it should work. On the Server Side it says that it's connecting correctly but after doing nothing for a while it timeout.
If during that moment (Before time out), I force quit ATLauncher from the hidden icon on the taskbar, now it finish the syncing (Can see from the log server side). But it never finishes the sync as long as ATLauncher is opened and I don't understand why.

For the argument in AtLauncher, I have:
"$INST_JAVA" -jar ServerSyncClient.exe --progress but I also tried "$INST_JAVA" -jar serversync-4.2.0.jar --progress. It does the exact same thing.

On the server sync log, I have this each time I try to connect:

[Dec 19, 2023 11:54:01][ServerSync] INFO: Connection established with Socket[addr=/IPADDRESSHERE,port=50770,localport=38067]Dec 19, 2023, 11:54:01 AM
[Dec 19, 2023 11:54:01][ServerSync] INFO: Received message: SERVER_INFO, from client: /IPADDRESSHERE
[Dec 19, 2023 11:54:01][ServerSync] INFO: Sending server information
[Dec 19, 2023 11:54:01][ServerSync] INFO: Received message: 4.EServerMessage.GET_MANIFEST, from client: /IPADDRESSHERE
[Dec 19, 2023 11:56:01][ServerSync] INFO: Client connection timed out, closing Socket[addr=/IPADDRESSHERE,port=50770,localport=38067]
[Dec 19, 2023 11:56:01][ServerSync] SEVERE: Client: /IPADDRESSHERE, timed out
[Dec 19, 2023 11:56:01][ServerSync] INFO: Closing connection with: Socket[addr=/IPADDRESSHERE,port=50770,localport=38067]

And on the ATLauncher log, I have this:

[19/12/2023 12:01:05 p.m.] Using Java runtime java-runtime-gamma (Java 17.0.3) at path **USERSDIR**\runtimes\minecraft\java-runtime-gamma\windows-x64\java-runtime-gamma
[19/12/2023 12:01:05 p.m.] Running command: ""**USERSDIR**\runtimes\minecraft\java-runtime-gamma\windows-x64\java-runtime-gamma\bin\javaw" -jar ServerSyncClient.exe --progress"

The configs file for serversync-client.json looks like this:

{
  "general": {
    "refuse_client_mods": false,
    "sync_mode": 2
  },
  "connection": {
    "address": "IPADDRESSHERE",
    "port": 38067,
    "buffer": 65536
  },
  "rules": {
    "files": {
      "ignore": [
        "**/serversync-*.jar",
        "**/serversync-*.cfg",
		"mods/*OptiFine*",
		"*.disabled*",
		"resources/**",
		"scripts/**",
		"*options*",
		"mods/*clientside*",
		"mods/*client*"
      ]
    }
  },
  "misc": {
    "locale": "en_CA",
    "theme": "BLUE_YELLOW"
  }
}

So yeah. I really don't understand. Since it's working when I close it like I said above, then that means the ports are working correctly so it shouldn't be that.

By the way, isn't there supposed to be a GUI that opens when launching ServerSyncClient.exe? Nothing is opening for me.

I'd appreciate any help please. Thanks!

@Xiarno
Copy link
Author

Xiarno commented Dec 19, 2023

If I add a small .bat file in the instance folder where Serversync is located with the following command:

ServerSyncClient.exe --progress
pause

It works & sync perfectly fine.

@Xiarno
Copy link
Author

Xiarno commented Dec 19, 2023

I tried to instead launch the .bat file I did above and I managed to get it to launch, but we come back to the same problem. It seems as long as ATLauncher is opened, it doesn't want to connect. Why?

@rheimus
Copy link
Collaborator

rheimus commented Dec 26, 2023

The --progress mode does not currently have a GUI built for it, ideally it would have some kind of progress indication.

It would seem from your description that ATLauncher is either blocking traffic between SS client and server or it is slowing it down enough to cause a timeout, would need to spend a while debugging the stack in question.

@rheimus rheimus added bug integration Problems integrating between serversync and other products labels Dec 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug integration Problems integrating between serversync and other products
Projects
None yet
Development

No branches or pull requests

2 participants