Mod causes resource pack distribution to fatally fail on Cytooxien

[Kichura]

When joining Cytooxien with this mod enabled, it causes the resource pack distribution system to completely fail and cause the player to get kicked because there was an validation error - this does not occur when excluding this mod from the fabric client.

Guessing cytooxien patched your mod after all? 🙃

[JustAlittleWolf]

Seems like it. For now I am not motivated enough to work on this, so it'll just like this on Cytooxien.

[Onako2]

I also could reproduce it with my own plugin which checks it (It just requires to have some strings that the plugin knows guranteed that they are present but aren't vanilla)

[JustAlittleWolf]

This should be fixed with the newest release 1.2.0

[linux-universe]

I still have the error

[JustAlittleWolf]

That is unfortunate, unfortunately Cytooxien has banned me so I am unable to check why the disconnect happens.

[linux-universe]

Is it somehow possible to blacklist cytooxien from joining with the mod installed to protect other users, i was just banned too...

[JustAlittleWolf]

I am not sure if that's the way to go, at that point you might as well uninstall the mod. For now I think that is also what you should do, to not use the mod. I'll put up a warning banner on GitHub and the download pages.

[Onako2]

Is it somehow possible to blacklist cytooxien from joining with the mod installed to protect other users, i was just banned too...

entirely banned? That's fucking shit

[linux-universe]

Is it somehow possible to blacklist cytooxien from joining with the mod installed to protect other users, i was just banned too...

entirely banned? That's fucking shit

i have sent a unban request. but yes permanent ban

[Onako2]

Should we inform the people behind Fabulously optimized that there is that issue?

[JustAlittleWolf]

Should we inform the people behind Fabulously optimized that there is that issue?

Great suggestion, I just informed them. Hopefully they'll take a look soon.

[1zun4]

Cytooxien has introduced a new check. They not only check for mod keybinds, but now also introduce keys themselves to block the fix from ModDetectionPreventer.

In my case it is for another mod - but it uses almost the same principle as ModDetectionPreventer.
I logged all the keybinds that are translated on this check - then I noticed... morecreativetabs.other and morecreativetabs.wurst. These make no sense at all, so I decided to whitelist them and... it is fixed.

[06:00:32] [Render thread/INFO] (Minecraft) [STDOUT]: morecreativetabs.other -> Other
[06:00:32] [Render thread/INFO] (Minecraft) [STDOUT]: morecreativetabs.wurst -> Sausage
[06:00:32] [Render thread/INFO] (Minecraft) [STDOUT]: pack.source.fabricmod -> Fabric mod
[06:00:32] [Render thread/INFO] (Minecraft) [STDOUT]: sodium.option_impact.low -> Low

There are now two ways:

• Block loading ModResourcePack to the TranslationStorage entirely - this only works for my use-case as I do not rely on their translation system.
• Instead of only whitelisting Vanilla keybinds and translations rather listen for additional entries to the Translation Storage from RPs (that are not ModResourcePack).

I have a question though, does anyone know if this is fixed with Minecraft 1.20.5?

[Onako2]

Cytooxien has introduced a new check. They not only check for mod keybinds, but now also introduce keys themselves to block the fix from ModDetectionPreventer.

In my case it is for another mod - but it uses almost the same principle as ModDetectionPreventer. I logged all the keybinds that are translated on this check - then I noticed... morecreativetabs.other and morecreativetabs.wurst. These make no sense at all, so I decided to whitelist them and... it is fixed.

[06:00:32] [Render thread/INFO] (Minecraft) [STDOUT]: morecreativetabs.other -> Other
[06:00:32] [Render thread/INFO] (Minecraft) [STDOUT]: morecreativetabs.wurst -> Sausage
[06:00:32] [Render thread/INFO] (Minecraft) [STDOUT]: pack.source.fabricmod -> Fabric mod
[06:00:32] [Render thread/INFO] (Minecraft) [STDOUT]: sodium.option_impact.low -> Low

There are now two ways:

* Block loading `ModResourcePack` to the `TranslationStorage` entirely - this only works for my use-case as I do not rely on their translation system.

* Instead of only whitelisting Vanilla keybinds and translations rather listen for additional entries to the Translation Storage from RPs (that are not ModResourcePack).

I have a question though, does anyone know if this is fixed with Minecraft 1.20.5?

It isn't fixed in 1.20.5/1.20.6

[Schluerfmann]

can you make a tutorial on youtube or smth? @Onako2