[❔]: How to disable a module by modifying the everycompat_hazardous.properties file ?

[libu2333]

Question

How to disable a module (e.g. Chipped module) by modifying the everycompat_hazardous.properties file ?

Optional: Details

I just visited this and I saw a mention about disabling a module by modifying the everycompat_hazardous.properties file. I would like to ask: How can I modify this file to completely disable a module, so that no blocks related to it are registered at all?

[Xelbayria]

simply change true to false. That should disable the module from generating new blocks.

[libu2333]

I just opened the file but it is empty. Must I fully start the game?

[Xelbayria]

Yes. you must launch the game for the content to be generated.

one thing to note:
If you are going to join a server with disabled module for Chipped. The server required Chipped module. Not a good idea.

There is a reason why the file has "hazardous". If you are playing in Singleplayer world, then all is good

[libu2333]

Thanks. I'm just use the cilent

[libu2333]

Another question. Is the file generated after the wood blocks is registered?

[Xelbayria]

I believe the answer is yes. I'll check with MehVahdJukaar

[libu2333]

It isn't generated at all after I started the game

[libu2333]

I opened the file and it only contains this text:

#Hard disable entire modules. Use at your own risk and don't ask for support if you use this
#Thu Jan 09 16:06:03 CST 2025

[Xelbayria]

Strange. I'm waiting for the response from MehVahdJukaar about 👇🏻

Is the file generated after the wood blocks is registered?

Apparently, I wondered the same thing. i even loaded the world and nothing got generated.

[libu2333]

Apparently, I wondered the same thing. i even loaded the world and nothing got generated.
I also did the same thing.

[Xelbayria]

He said

Config is loaded before
Obviously
Otherwise it would not work. Its whole point is to prevent block registering of it was loaded after and read before it would crash

only thing uncommon with it is that it will generate the file just once
and its content is always null. you just add modid to boolean

I had my guess of the last part. he confirmed it.

you just need to add to that file: chipped and it will be disabled. I've tested it. it's working as it's intended