I don't know what's going on reupload. This is a new link https://mega.nz/file/yixCHIzJ#lIHcHAI6Ct7K3FEMPERFETPegP6PqYnPpTBUgPOo8ww
I did notice a similar Thing some Time ago, where a new File was uploaded short after the old one, but did use the same File Name as the older File. And the Browser seemed to detect it as already downloaded then. It's always a good Idea, to add the Version Number to the File Name, to make them different.
Maybe remove all the server mods referencing the old version. And always use an "odd" number for a final version. A track or a car should not use 1.56 in its usable version. It will have weird behaviour like we see here ... For an item in 1.55, the next version will be 1.57 with its new (or not) 1.56 base or no base. Weird but should be like that ... Maybe redo the 1.55 but don't use 1.56 as final version. For the game the 1.55 is a "major" version which should stay. The 1.56 is a "base" version that will never replace the 1.55 ... Most of that is my own guess just by experience ... and a few tutorial talk explicitly about the "odd" version that should always be used as final playable item (Upgrade or standalone item).
And that base/version mecanism is what make rF2 able to keep multiple versions with their base. Imagine an item with 4 versions installed. 1.01, 2.05, 2.07, 3.01 In game (single) you will only see the "last" 3.01 but if a server uses other versions it will work perfectly and you will be able to connect. In Installed folder you will have folders : 1.00, 1.01, 2.04, 2.05, 2.06, 2.07, 3.00, 3.01. At some point previously rF2 was able to keep older versions based on "residual" vmods and never uninstall them if the vmod was kept. Again pure facts seen by experience in older versions ...
