Alrighty guys...
Me and a mate did some testing tonight and here is what we discovered.
H
1) An individual CANNOT create the same content virtual mod with the same name using different MODID.....good.
2) 2 Different accounts CAN create the same content virtual mod with the same name using different MODID......bad.....potentially.
What does this mean....
If a vMOD is released by someone and call it MOD1.
The contents of this MOD1 is X Track and Y Car. They release it and all is good.
I come along and I want to make rF2 hell for people.
I go and create the same MOD call it MOD1 include X Track and Y Car. I release it and here is where the fun starts.
If we both call it the SAME file name for the rfmod think about the issues.
ISSUE 1 - You copy the file into your packages folder and it replaces the file.....nothing major there, contents the same etc etc...will stall call poroblems for the unitiated but not as bad as the next issue.
ISSUE 2 - I circulate the second mod (differnt MODID) under the guise its the same as the first mod. Mr Gamer gets mine and installs it. He tries to join a server with my circualted mod and it goes "computer says no". From there he gets hold of the Server admin (somehow) and the admin says you need this mod and file. This poor guy goes...yeh I have that. After a bit of stuffing they check the properties of the mod by right clicking on the mod in the MOD INSTALLER. The ONLY information that will look different is the MODID.
Confusion city.
Just though I would post this little gem for you to mull over.
A fix you say...well...one way would be to limit the production of the MODID to MOD NAME as well....but bollox I cry. The name of the Mod in the MOD INSTALLER is taken from the rFM....so again...it still looks the same.
Not sure on what ISI have in store for that one