when i try join a local server running a server software other than mcg using webclient, it shows "reconnecting".

webclient is hosted on a local static server (eja) (parses query String in client itself : Here)

I'm not interest in running c# apps so I looked for alternatives (dazed-sheep in js

and project obsidian in python)

But I couldn't connect to both of them using webclient. It says "invalid packet" (unknown? bad? i dond remember).

But I could join using the downloaded one.

I could join mcgalaxy with zero issues.

I disabled classicube auth in mcg and dazed.

I'm hosting webclient on my own as the og one has client side one.

Btw im running all (eja and node/python/mono) on termux, android 9, 3gb ram

Edited Friday at 05:20 PM2 days by tbapknoob12mc

The reason why the web client is only able to connect to MCGalaxy is because MCGalaxy supports clients connecting over a WebSocket layer. dazed-sheep doesn't implement WebSocket support so it doesn't understand incoming WebSocket connections.

Server software/libraries which support WebSocket clients include:

• MCGalaxy (C#)

• classicborne-server-protocol (Node.js, JavaScript)

• thirty (C)

• ProCraft (C#)

I am not aware of server proxies which support WebSocket.

Edited Saturday at 07:30 PM1 day by BunnyNabbit
use Clear Communication

9 hours ago, BunnyNabbit said:

The reason why the web client is only able to connect to MCGalaxy is because MCGalaxy supports clients connecting over a WebSocket layer. dazed-sheep doesn't implement WebSocket support so it doesn't understand incoming WebSocket connections.

Server software/libraries which support WebSocket clients include:

• MCGalaxy (C#)

• classicborne-server-protocol (Node.js, JavaScript)

• thirty (C)

• ProCraft (C#)

I am not aware of server proxies which support WebSocket.

Thanks a lot, brother.

Idk if some1 can glue that classicborne protocol with dazed sheep.

(Nvm I found a workaround for making standalone mcg builds in termux and now I can save 250 mb as seen Here)