When I updated Fuji and Topeka to v1.01 each I didn't spend much thought on how it would affect vmods. Since I created another full version it requires 1.00 to be uninstalled which in turn seems to mess up the vmods. For Fuji so much changed an update-only version would not have made much sense and I dislike to have people download v1.00, then v1.01, then v1.02, then v1.10 etc. and rather provide them with one full download. I seem to have misread the packaging tutorial though and overestimated the size of the potential update so I might try the update version next time around. Questions: - if I had instead used an update version that does not require an uninstallation of v1.00 before installing v1.01, would that allow the vmods to keep functioning after installing v1.01? - if the answer is negative, what does that mean for track updates? Each time we update we mess up the vmods. That will get quite frustrating for those maintaining vmod collections of popular mods. Or can this be explained by rfmods being used differently than what it was supposed to be - namely they're currently used as a stopgap measure to somewhat recreate the rF1 multiplayer environment when they are meant to be league/event/server-specific - what does updating tracks mean for the automatic downloads? If someone wants to join a server running Fuji v1.01 I suppose his Fuji will automatically be updated to v1.01. What happens if the same person then tries to join a server running Fuji v1.00? Is his track getting backdated to v1.00?