Enigmatica 9: Expert - E9E

Enigmatica 9: Expert - E9E

Modpacks
135k Downloads

[Mod Suggestion] Better Compatibility Checker

Kanzaji opened this issue · 8 comments

commented

URL

https://www.curseforge.com/minecraft/mc-mods/better-compatibility-checker

Why would you like the mod added?

I would say pretty useful QoL mod, that will definitely help with confusion on what version server is. Need to test how it functions if client version (aka: Any version below the update that adds this mod 😅) doesn't have it, but I'm fairly sure it will help in the future 😄

Was planning on suggesting it for Enigmatica 8 as well, but I don't think there will be a lot of updates to E8 at this point, so not sure if it would be useful at all there.

commented

Found one thing that would needed to be changed already Aizistral-Studios/No-Chat-Reports#343 (comment) , but that isn't a huge issue 😄

\config\NoChatReports\NCR-Client.json

  "verifiedIconOffsetX": -14,
  "verifiedIconOffsetY": 0,

bcc-common.toml

#General settings
[general]
	#The CurseForge project ID for the modpack
	#Range: > 0
	modpackProjectID = 632239
	#The name of the modpack
	modpackName = "Enigmatica 9"
	#The version of the modpack
	modpackVersion = "DEVELOP"
	#Use the metadata.json to determine the modpack version
	#ONLY ENABLE THIS IF YOU KNOW WHAT YOU ARE DOING
	useMetadata = false

Metadata function was created specifically for FTB, but we could technically use it as well.

commented

Also, this how this looks in-game:
obraz

For the older versions, the mod is just "disabled", it doesn't change the Forge prompt if the mod is not present on the server-side, I did ask if custom note for this case-scenerio could be possible tho 😄
nanite/BetterCompatibilityChecker#17

commented

Hmm, so I'll have to keep modpack version updated in the config? 😅

commented

Well, yea 😅But I would say it is worth it, and with Metadata, we could technically generate the file with version number on the release 😄

commented

Got any idea how the metadata approach works? :D

commented

Here is the metadata.json file from FTB modpack 😅

{"id":100,"name":"FTB StoneBlock 3","type":"Release","version":{"id":2308,"name":"1.5.0","type":"beta"}}

Would have to do a bit of research on the IDs, but everything else is pretty easy to understand 😄
The file itself goes into config folder.

Update:
Seems like Ids are not random. The first ID changes with FTB pack, and the second one changed for each version. It does also seems like the version ID is never the same, even between packs, what is... not a great mod design, if the option is available for use to anyone, but was made specifically for FTB >.>
Gonna experiment a bit if custom Metadata can be made, or is it required to be in the format FTB uses.

commented

Nah it's good, I'll just update the config with a script or something 😄 thanks for doing the research!

commented

Not a problem😄
However, after a bit of digging in the source code of the mod, it seems like metadata.json isn't actually something really fancy 😄
It is pretty much used to override values in the config file, so:

  • "id": -> Replaces projectID in the config
  • "name": -> Replaces the name in the config
  • "type": -> FTB Exlusive, this seems to not be even read by the mod 😅
    Version fields:
  • "id" -> Metadata Exclusive, not sure how is it used.
  • "name": -> replaces the version in the config
  • "type": -> Metadata Exclusive, not sure how is it used.

However, it seems that the comparison if server and client are on the same version is only using Name of the modpack and version number, so not even sure why the other fields are required 😅

  • 👍1