Log in
Register
  • Hi Guest!

    We are extremely excited to announce the release of our first Beta1.1 and the first release of our Public AddonKit!
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. For access to the Public AddonKit you must be a Creator tier member. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.
  • Hi Guest!

    VaM2 Resource Categories have now been added to the Hub! For information on posting VaM2 resources and details about VaM2 related changes to our Community Forums, please see our official announcement here.

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

Threads regarding the original VaM 1.x
O

Okachu

Active member
Joined
May 16, 2024
Messages
239
Reactions
70
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:
Sort by date Sort by votes
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
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
You must log in or register to reply here.

Similar threads

H
  • Question
Question file not named with convention - can i just rename the file in the folder?
Replies
2
Views
1K
atani
atani
T
  • Question
Solved Clothing Texture Set Naming Conventions
Replies
10
Views
1K
Origin69
Origin69
T
  • Question
Question Scene name location after scene is opened?
Replies
2
Views
615
Toddy
T
G
  • Question
Solved Creator Key not working
Replies
4
Views
6K
Origin69
Origin69
O
  • Solved
Question Name of slightly older space scene with rogue android?
Replies
2
Views
413
Krab
Krab
Back
Top Bottom