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

Server is marked incompatible #10

Open
H0bbitBaron opened this issue May 8, 2021 · 4 comments
Open

Server is marked incompatible #10

H0bbitBaron opened this issue May 8, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@H0bbitBaron
Copy link

Hello! Server with telegrambridge is marked incompatible. Log from client console:

[22:34:27] [Netty Client IO #1/INFO] [ne.mi.fm.cl.ClientHooks/CLIENTHOOKS]: Server has additional mods that may be needed on the client: [email protected]

Full log here.

May be related to this:

//Make sure the mod being absent on the other network side does not cause the client to display the server as incompatible
ModLoadingContext.get().registerExtensionPoint(ExtensionPoint.DISPLAYTEST, () -> Pair.of(() -> FMLNetworkConstants.IGNORESERVERONLY, (a, b) -> true));
@LionZXY
Copy link
Member

LionZXY commented Jul 21, 2021

For what you want use it only on client-side?

@LionZXY
Copy link
Member

LionZXY commented Jul 21, 2021

Could you, please, describe what you expect?

@LionZXY LionZXY added the enhancement New feature or request label Jul 21, 2021
@Eric-01
Copy link

Eric-01 commented Aug 31, 2021

I think the problem here is that Telegram Bridge is a server-side-only mod, so it shouldn't be installed on the client side as well. But when this mod is not installed on the client side, the red X shows up in the Minecraft server list, see:

mod-list-red-x

People, when seeing this, may get confused and start to think that they installed Telegram Bridge incorrectly, and to fix it they need to install this mod on the client side as well (which is not true, they do not have to do so).

This is because sideness handling in Forge for 1.13+ is much different than in previous versions. For more information on what to do to fix this issue, you can read for example either:

@LionZXY
Copy link
Member

LionZXY commented Sep 1, 2021

Wow! Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants