• Hi Guest!

    We have posted a new VaM2 dev log on Patreon, starting a monthly cadence of written progress updates between Beta releases. Highlights include the new Gizmos System, Selection Carousel, and Modes System with Context-Specific Editing. Beta1.2 is 15 of 21 items complete.

    Read the full post on Patreon, or follow progress on the public Trello roadmap.

Auto reject uploading incorrectly named packages

RandomVAMUser

Well-known member
Joined
Dec 21, 2020
Messages
703
Solutions
13
Reactions
753
Imo this could improve overall quality of hub-hosted content.
In the past unaware users removed version or renamed entire package.

So if user is trying to upload .var format that doesn't follow correct naming scheme: <creator> . <package name> . <version> . var
automatically reject it. This should auto reject packages like package.var, creator.package.var, creator.package.1(1).var

Maybe go few steps further:

-reject fake .vars without meta
-check expected creator & package name from meta inside package, reject if creator and package name are not the same
-reject/prevent uploading same version again as resource update (if creator and package names are the same)
-auto reject uploading archives that contain .var before extension? creator.package.1.var.zip, xxx.var.rar, xxx.var.7z, etc...
-auto reject .vac files (when comparing to vars, old vac packages by nature create more mess inside client and most (if not all) users are on version 1.19+ to support vars)

Some examples:
kmsktx.Simple_Headband.var (no version) --> broken reference link https://hub.virtamate.com/resources/nadia.4900/dependencies

Wishfullsoul.bath.var (no version)

THICC.Valencia_K.2.var.zip with THICC.Valencia_K.2.var folder inside

fake var package (no meta.json)

I couldn't find any examples of fully renamed packages, I have seen them before.
 
Here's another. This is actually a "naked" scene file renamed and posted as a var. Copied into saves/scene, it actually works.
 
Back
Top Bottom