[Issue]

[liampearson96]

Mod version

BetterCompatibilityChecker-1.0.7-build.22+mc1.16.5.jar

Forge mod loader version

forge-1.16.5-36.2.9

Repeatable?

• [X] Yes

Link to log files

https://paste.mozilla.org/7Jj6f6AS

Steps to reproduce the issue

1. Downloaded mod and put into mods folder
2. Started server
3. Stopped server and edited BCC config.
4. Started server.

Description of the issue you are having

For some reason it doesn't display any information other then 'incompatible Vanilla server' Please let me know if i am doing something wrong?

Information

• [X] I have provided as much information as possible

[Gaz492]

Looks like the link to the logs is invalid, would you be able to upload them again?

[liampearson96]

https://paste.mozilla.org/i441168M

@Gaz492 This one should be good

[Gaz492]

Thanks, the logs show that it loaded the config without any issues the only thing I can see is, I'm not sure if the server started fully, this would cause the server to show that it's a vanilla server. Are you able to connect to the server at all?

[liampearson96]

Thanks, the logs show that it loaded the config without any issues the only thing I can see is, I'm not sure if the server started fully, this would cause the server to show that it's a vanilla server. Are you able to connect to the server at all?

Yes the server is connectable. I can load into the server mine, place ect just fine.

[Gaz492]

Thanks, the logs show that it loaded the config without any issues the only thing I can see is, I'm not sure if the server started fully, this would cause the server to show that it's a vanilla server. Are you able to connect to the server at all?

Yes the server is connectable. I can load into the server mine, place ect just fine.

Ok, would you be able to upload the debug log? It may contain more information as to whats going on.

[github-actions[bot]]

This issue is stale because it has been open 5 days with no activity. Remove stale label or comment or this will be closed in 2 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 2 days with no activity.