jeremiahwinsley / actually-compatible

actually-compatible

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

The Problem

Know this annoying big red X even when your client has exactly the same mods as the server?

incompatible

  • Well, this is because there is a size limit in minecraft on how much data can be sent for compatibility checks.
  • On top of that forge put a hard limit on the amount of maximum mods that can be checked for compatibility (so you do not hit the packet limit and crash)
  • If you have any more mods than 160, the compatibility check automatically fails. This is in forge >= 36.1.32.

 

The Solution

  • Actually Compatible increases the compatibility check packet size significantly. (from 32KB to 100KB by default)
  • You can also provide your own new packet size in the config file.
  • And last but not the least, the mod removes  the hard 160 mod limit put in by forge.

 

All of the fixes mentioned above, together fix the compatibility checks.

You will receive proper list of incompatible mods in your client logs.

And, once you have actually compatible list of mods, the big red angry X turns into the happy green

check

 

Compatibility

The same fix is being used in my modpack Starpack Titan with 600+ mods and it gives perfectly accurate checks.
If you discover an issue, please report from the issues tab above.

 

About

actually-compatible

License:Creative Commons Zero v1.0 Universal


Languages

Language:Java 100.0%