What are the coding practices for making FNF mods compatible with other mods and base game?

[MAZ12211]

At which point base game detects a mod confliction with other mod(s)? so, I can avoid it as not a whole lot is told in the official documentation

[Trofem]

Now, mod conflicts are not handled that good (at all) in game, loaded mods are alphabetically sorted.
for more mods compatibility, not as much, but anyway, i suggest:

• using _merge if possible, when changing original files;

• when creating (for example) song, creating separate week (without showing in story mode) and making songs in it, instead of fully overriding existing week song;

More in details:

• _merge helps with creating variation, mixes songs data, with using it, mods can add (for example) multiple song variations at the same time. But in some mods now are used rarely, so if mod is alphabetically higher and isn't using it results in it rewriting everything that needed. In wiki now is described good enough

• this thing helps with not creating song that would use and operate in already-existing song.
  For example - you created remix of blammed, and when you override existing (bf) player - after playing, score is not correct with og song. It could have incorrect current max score / percent completion ratio.

devs probably will use and demonstrate more techniques

[MAZ12211]

So far:

• for modules and every script I've been changing the id to mod's-name-moduleName (i.e extra-events-cameraRotateEvent, it's a song event but you get the idea) instead of just the module name as the id to decrease the chances of file conflictions
  Pretty much like RPG Maker plugins

• For creating recharts and any file that is a json file (like the credits file) I make a json patch instead of overwriting the original file

I don't know if that's everything

[Trofem]

yep those are good ways.
i think it will be cool if docs would have some of general modding style guide for fnf.
like style-guide, but for modders.

[Lasercar]

In the event of a conflict, it's first come, first served based off the file name (there's nothing for detecting script class conflicts... yet...).

Best practices would be to make modding libraries out of things that can be used for other mods, and then to allow them to be used for other mods, to keep incompatibility to a minimum (basically like how many other modding communities do it). Direct conflicts caused despite that would still have to be resolved manually by either or mod and modder.