scorives

I think this is a bigger issue than just Maltiez's. The whole ModDB needs some better rules and regulations and more oversight as well. I have uploaded a post last month to the Mod DBforum for the devs in regards to changes I Think should be implemented along with others that are not listed. Here is a link if interested:

Hey devs, First off, huge appreciation for all the work on Vintage Story—the modding community is easily one of the best parts of the game. That said, the current state of mod distribution, versioning, and compatibility is becoming a massive headache for server hosts and players alike. Right now, the ecosystem suffers from a few glaring pain points: Uncontrolled Forking: When a popular mod goes stale, multiple players create separate forks to patch it. We end up with 3–4 different "band-aided" versions floating around ModDB, each breaking different things. Cascading Breakage: Because there’s no unified standard for handling cross-mod dependencies or updates, fixing one incompatibility with a unofficial fork frequently breaks two other mods down the load order. Database Clutter: Searching for a functional version of a core mod often means wading through duplicate uploads, obsolete re-uploads, and conflicting patches with minimal versioning clarity. Proposed Solution: An official ModDB Metadata & Compatibility Standard enforced or recommended by the team would go a long way: Strict Version & Fork Tagging: Require forks to be registered as "Derivatives" or "Patches" attached to the main mod page rather than standalone uploads, or enforce strict semantic versioning tags. Standardized Dependency/Incompatibility Schema: Expand the modinfo.json standard to clearly declare explicit soft/hard incompatibilities and recommended load orders directly readable by the game launcher. Abandonware/Transfer Policy: A formal workflow for community-maintained updates so official mod pages can be handed off or updated rather than splintering into endless new ModDB entries. Having a clean, standardized system will save players from constant crash logs and let authors focus on building instead of resolving duplicate bug reports. Would love to hear the team's and other modders' thoughts on establishing cleaner ModDB guidelines for this!