As the name suggests, an audit log to keep track of what mods/resourcepacks/datapacks/configs/etc. you've downloaded/removed/modified/etc. would be IMMENSELY helpful to have especially for diagnosing crashes and other issues that might appear in a modpack you create or modify.

Nobody likes having to track the changes they make to a pack, it's tedious, annoying, and especially hard for people with ADHD like me to do since we tend to forget stuff almost immediately after we think about them, even if we're on meds.

Feature Requirements:

-Add an "instance_changes.cflog" file into every modded Minecraft instance that tracks and stores info as readable text anyone can understand.

-Make the "instance_changes.cflog" file keep track of the name, directory, date, and time a file was being added, moved, modified, updated, downgraded, or deleted.

Note: The ".cflog" file extension would just be encoded is a normal text file but it would have a layout not too dissimilar from Forge's "debug.log". The reason for why the file extension is being made custom instead of a generic ".txt" file is to allow for custom syntaxing in programs like Visual Studio Code.

I KNOW this feature will be a MASSIVE quality of life improvement for modpack makers AND mod developers when sourcing the cause of a bug or incompatibility. I make modpacks all the time for myself and have always wished that my computer could just track the changes made for me in a nice big list instead of me having to type out that list AND remember all the things to write down in the first place, all just so I can figure out why an unknown mod was having a stroke on game launch (I'm looking at you outdated Create addons, ya'll make me run in circles for 30 minutes).