• 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.

VaM 1.x var is not named with convention <creator>.<name>.<version>

Threads regarding the original VaM 1.x

Okachu

Active member
Joined
May 16, 2024
Messages
291
Solutions
1
Reactions
96
I know the error but what is wrong with these names?


creator.name_asset.1.1.var is not named with convention <creator>.<name>.<version>

c_creator.name_A.1.1.var is not named with convention <creator>.<name>.<version>
 
Last edited:
.1.1
should be .1
 
Upvote 0
Solution
If it's a package you're creating :
  • Avoid special chars at all costs for the package name, only use : lower or uppercase letters, eventually separator - or _
  • Numbers are ok if its the title, don't add the version number
  • I know I said non special chars, but out of safety : No accents ( àéè... ), no / \, no [ | ] and all that stuff.
  • If you're a cyrillic / asian person, avoid using your character set and stick to standard letters ( as these language encoding is not that stable )
 
Upvote 1
thx, the errors are gone! No, It's not a package from me.
I hope the files still working now. 😅

Ok, one left error:

creator.name77_name.var

should I rename it to creator.name_name.var

or creator.name77name.var

because numbers are ok in the title?
 
Upvote 0
Always : creator . packagename . version .var
... dots being mandatory.

So, these below are all valid examples :
  • hazmhox.mypackage.1.var
  • hazmhox.mypackage101.1.var
  • 666hazmhox.101mypackage.1.var
  • HazMhox.MyPackage.1.var
  • hazmhox.My_Package_101.1.var

These below are invalid:
  • hazmhoxbeds1.var
  • hazmhox.beds1.var
  • hazmhox.beds.test.var
  • [hazmhox].[beds].1.var
  • etc...
 
Upvote 0
Also, remember : if package is not named as expected, it will fail if it's used as a dependency.
 
Upvote 0
Also, remember : if package is not named as expected, it will fail if it's used as a dependency.
Ah this one had no version number, true.

But if I renamed the files, it's counting again? Or do I have to redirect the files?
 
Upvote 0
If the dep list looks "hazmhox.package.1.var" and you rename it "okachu.pack.2.var" it's gonna fail, no matter what.
 
Upvote 0
You're not responsible here ;)

If people rename files out of nowhere without knowing what it does and sharing that... you're definitely not the one to blame.
 
Upvote 0
Ho yes! blame me!

B07JtN.gif
 
Upvote 0
Back
Top Bottom