[Q/A] How to disable the logging?

[Unknown78]

As the the title said, how to disable modloeader.log from being created?

There should be a setting in the modloader.ini file, but I couldn't find it.

[thelink2012]

You can find the option in modloader/.data/config.ini (not the .ini.0). The option is EnableLog. Em qua., 16 de set. de 2026, 05:24, Unknown78 ***@***.***> escreveu:

…

*Unknown78* created an issue (thelink2012/modloader#150) <#150> As the the title said, how to disable modloeader.log from being created? There should be a setting in the modloader.ini file, but I couldn't find it. — Reply to this email directly, view it on GitHub <#150?email_source=notifications&email_token=ABNGVTNU5OR6MZKFJLQT2P35PJE2VA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NJUG4ZDAOBUG42DRJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNGVTJGN6XCAPK26TBH2DT5PJE2VAVCNFSNUABEKJSXA33TNF2G64TZHMYTINBWGIYTSNZ3JFZXG5LFHM2TINZSGA4DINZUHCQXMAQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Unknown78]

modloader.log

========================== Mod Loader 0.3.10 ==========================

Game version: GTA VC 1.0 UNK_REGION
Using Mod Loader folder "C:\Rockstar Games\Grand Theft Auto Vice City\scripts\modloader\"
Loading basic config file .data/config.ini
Logging is disabled. Closing log file...

It is still being created.

Seems like bootstrap paradox or circular dependency or something like that is happening.

[thelink2012]

It won't stop being created, it will just close early and no longer log. Can you explain your use case? Em qua., 16 de set. de 2026, 08:24, Unknown78 ***@***.***> escreveu:

…

*Unknown78* left a comment (thelink2012/modloader#150) <#150 (comment)> modloader.log ========================== Mod Loader 0.3.10 ========================== Game version: GTA VC 1.0 UNK_REGION Using Mod Loader folder "C:\Rockstar Games\Grand Theft Auto Vice City\scripts\modloader\" Loading basic config file .data/config.ini Logging is disabled. Closing log file... It is still being created. Seems like bootstrap paradox or circular dependency or something like that is happening. — Reply to this email directly, view it on GitHub <#150?email_source=notifications&email_token=ABNGVTO7KAIZAJA43CFM2K35PJZ5BA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNRZGY3DINZTGAY2M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5696647301>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNGVTOJJONEMR24AXHXLV35PJZ5BAVCNFSNUABEKJSXA33TNF2G64TZHMYTINBWGIYTSNZ3JFZXG5LFHM2TINZSGA4DINZUHCQXMAQ> . You are receiving this because you commented.Message ID: ***@***.***>

[Unknown78]

I just want the log file being created if I need it.

The current implementation is rather awkward, in my opinion.

I mean, instead of creating the log file saying that the logging is disabled.
Wouldn't it makes sense and be better to not create the log file if it is disabled in the first place?

[thelink2012]

I don't think so, because in that case the oldest generated log would stay in place, and when diagnosticing a issue the user would send up an unrelated log file rather than the log of the latest run saying the user's log was disabled. Em qua., 16 de set. de 2026, 20:09, Unknown78 ***@***.***> escreveu:

…

*Unknown78* left a comment (thelink2012/modloader#150) <#150 (comment)> I just want the log file being created if I need it. The current implementation is rather awkward, in my opinion. I mean, instead of creating the log file saying that the logging is disabled. Wouldn't it makes sense and be better to not create the log file if it is disabled in the first place? — Reply to this email directly, view it on GitHub <#150?email_source=notifications&email_token=ABNGVTN7MQ67GZQOKKGVBR35PMMRBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNZQGU4DCOJUGU3KM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5705819456>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNGVTJ2WSUW2RIPRK5NFMT5PMMRBAVCNFSNUABEKJSXA33TNF2G64TZHMYTINBWGIYTSNZ3JFZXG5LFHM2TINZSGA4DINZUHCQXMAQ> . You are receiving this because you commented.Message ID: ***@***.***>

[Unknown78]

I don't think it's possible for a user to sent an unrelated log file, considering that LogEnable by default is true.
If a user deliberately set it to false, then the user must've known beforehand the consequences of it.

Furtermore, I've just tried some workaround methods

1. Create a folder named modloader.log.
2. Create a file named modloader.log and set it to Read-Only.
3. Changing the Security of the modloader.log by removing the Write and Modify access.

At the startup of the game, it will pop up a message box window titled Mod Loader with the message of Failed to open the log file.

An awkward implementation and an awkward workaround.

How to disable the pop-up error window?

Not sure what are the proper ways to handle this.