Mod compatibility check fix

[Atrik]

This mod allow ignoring the file structure in determining if a mod is compatible or not. 

I'm making this after desperately not understanding what is going wrong with @Emacz mod classical-warefare-aea-main.
With this mod I'm finely able to join his hosts easily.

Anyone making a incompatible mod could use this to make players joining each other easier without having to skip compatibility check.

compatibilitycheckfix.zip

Edited 15 hours ago by Atrik

[guerringuerrin]

Isn't it unusual to allow the same mod to have a different file structure for two different users? Couldn't that generate false positives?

Aside from my question, this seems like a rather forced solution aimed at solving a problem that doesn't really exist. Modders should provide a simple way for users to obtain their mods. Besides, it doesn’t seem like a serious issue. It’s just a matter of learning how to properly create a .zip/.pyromod and providing clear instructions to the end user.

[Atrik]

44 minutes ago, guerringuerrin said:

Isn't it unusual to allow the same mod to have a different file structure for two different users?

I've done a mod that change 0AD icon and I'm trying to distribute it.

1. On my machine
   
   ModImWorkingOn/
   ├─ mod.json
   ├─ fileIgnoredByGitIgnore.@#$%
   └─ art/
      └─ 0ADIcon
   

2. A user cloning my git
   
   New0ADIcon/
   ├─ mod.json
   └─ art/
      └─ 0ADIcon
    
3. A user downloading from my git
   
   New0ADIcon-master/
   ├─ mod.json
   └─ art/
      └─ 0ADIcon
    
4. A user downloading from mod.io
   
   New0ADIcon/
   ├─ mod.json
   └─ New0ADIcon.zip
    

1 hour ago, guerringuerrin said:

Couldn't that generate false positives?

Yes, 1000x harder for the modder to fck up and generate false positive then generating false negative thoughts. Being on the responsibility of the modder rather then the user is also obviously desirable.

I think that also invalidate your remarks about this being a solution for a problem that doesn't exist. Which you would have a high chance of being wrong about since I don't think you ever use incompatible mods (yes you use and distribute compatible ones but they don't have this problem. For now, anyways).
I don't know the original cause of the problem I faced with @Emacz, and others using his mod. But this isn't the first time I'm facing troubles with mods trying to use compatibility check, and this fix would have probably solved past cases.