Looks Jinx

[OniEkohvius]

OniEkohvius submitted a new resource:

Jinx - Slogan, catchphrase, tagline!

View attachment 94178

LoL - Jinx
The Loose Cannon

View attachment 94179​

Package includes:

• Full Morph
• Textures
• Outfit
• Hair

Part of the February batch of launch models for Patrons. This has been done before but I was asked to port it nevertheless.
I'd very much appreciate your support if you've enjoyed my models in the past and want me to continue...

Read more about this resource...

 

[OniEkohvius]

OniEkohvius updated Jinx with a new update entry:

Free - Out of Early Access

February launch models now available to all. March launch models now available for early access!

View attachment 102238

Read the rest of this update entry...

 

[charlestone]

Is the version with her top pulled open missing? I can't find it

 

[charlestone]

Still no update with the second revealing variant of the top?

 

[OniEkohvius]

OniEkohvius updated Jinx with a new update entry:

1.2 Missing top (exposed) added.

Finally getting around to updating this with the missing exposed variant of the top. I'd gotten a lot of PMs about this, sorry for the delay!

The .var is named slightly differently due to not having the old .var at the time of packaging. Feel free to manually delete the old one to save yourself some space.

Read the rest of this update entry...

 

[Sally Whitemane]

Hey OniEkohvius,

not sure if this was a mistake - you seem very professional:
Partial versions like 2.1 are not supported for packages.
Keep the package name the same with only one version number.

OniEkohvius.Jinx.2.var to OniEkohvius.Jinx_v2.1.var
VAM only uses the last number before the last dot as package version. The 2.1 is a read downgrade to version 1. This breaks user customized looks based on 2.var. In this case it's assumed to be a completely different package anyway because the names changed with the "_v2."-part.

An update from OniEkohvius.Jinx.2.var to OniEkohvius.Jinx.3.var would still load old custom looks build with version 2 even if it gets deleted. VAM detects 3 as latest version then and uses that one.

I think you accidentally left a temp copy of the scene in the package too. (in case you want to re-up)

 

[OniEkohvius]

Hey OniEkohvius,

not sure if this was a mistake - you seem very professional:
Partial versions like 2.1 are not supported for packages.
Keep the package name the same with only one version number.

OniEkohvius.Jinx.2.var to OniEkohvius.Jinx_v2.1.var
VAM only uses the last number before the last dot as package version. The 2.1 is a read downgrade to version 1. This breaks user customized looks based on 2.var. In this case it's assumed to be a completely different package anyway because the names changed with the "_v2."-part.

An update from OniEkohvius.Jinx.2.var to OniEkohvius.Jinx.3.var would still load old custom looks build with version 2 even if it gets deleted. VAM detects 3 as latest version then and uses that one.

I think you accidentally left a temp copy of the scene in the package too. (in case you want to re-up)

Hey,

Yeah, I acknowledged the different name of the package in the update info. The solution would have been to redownload it first and then package but updating this was a bit of an afterthought after working on another model for a while and wanting to finish up so I just went ahead and renamed it.

The temp scene file is just a way for me to package up additional clothing without the need to search for it in VAMs directory thing. Usually I delete it but looks like I forgot in this case, thanks for the heads up.

 

[bluebirdie88]

Do you take requests? I have a LoL champion I want in Vam but don't know where to start. I would rather pay someone to make it.