[SCS Workshop Uploader] Mod compatible_versions[] on 1.28 [40117]

[Drive Safely]

Here is my versions.sii (I tried compatible_versions[]: "1.7.*" but no effect)

Code: Select all

SiiNunit
{
package_version_info : .temp_content
{
    package_name: "temp_content"
	compatible_versions[]: "1.29.*"
	compatible_versions[]: "1.5.*"
	compatible_versions[]: "1.4.*"
	compatible_versions[]: "1.3.*"
	compatible_versions[]: "1.2.*"
}
package_version_info : .universal
{
	package_name: "universal"
	compatible_versions[]: "1.6.*"
	compatible_versions[]: "1.28.*"
}
package_version_info : .info.downgrade.newer.game.versions
{
    package_name: "downgrade_info_package"
    informational: true
}
}

Sound Fixes Pack keeps running the temp_content package (SAFE MODE) on 1.28.0s even though I set the universal package to run on 1.28 and 1.6. But I want it to run the universal package on 1.28 though it doesn't seem to be registering.

How can it be falling to game version 1.29, 1.5, 1.4, 1.3, or 1.2... on 1.28.0 Must be a bug unless I'm missing something?

[Smarty]

It's incorrectly interpreting 1.28.0 as fitting "1.2.*". I've reported it a few minutes ago as QA 40117.

For now, either try putting your universal package above temp_content or removing compatible_versions[]: "1.2.*". Parsing errors are fun.

[Drive Safely]

@Smarty - Ah thanks so much. Had a feeling it would be a frustrating bug. Got v17.48 live now!

[Drive Safely]

This same bug returned when I was trying to update my mod for 1.31. I had to remove my 1.3 version of my mod...
This is really an annoying bug and completely wasted my time going back and forth between betas (since SCS Workshop Uploader doesn't keep mod validation synced with the game version). -.-

[SiSL]

Well, I'm discarding my pre-1.28 versions, hardly anyone bother to play back...

[Drive Safely]

Yes, but that doesn't solve a known bug. I use safe mode for Sound Fixes Pack (light version of the mod) for old game versions to save space but still let my mod work in older versions, but this parsing bug is gradually preventing that.

[Smarty]

Drive Safely: Could you post the contents of your versions.sii? I am not able to reproduce this issue on any of my workshop mods that use different packages for 1.30/1.31 and 1.3. I wonder if maybe you just have a syntax issue or something?

[Drive Safely]

@Smarty - Here is my previous versions.sii (before deleting compatible_versions[]: "1.3.*")

Code: Select all

SiiNunit
{
package_version_info : .temp_content
{
    package_name: "temp_content"
	compatible_versions[]: "1.6.*"
	compatible_versions[]: "1.5.*"
	compatible_versions[]: "1.4.*"
	compatible_versions[]: "1.3.*"
}
package_version_info : .universal
{
	package_name: "universal"
	compatible_versions[]: "1.31.*"
}
package_version_info : .130_content
{
	package_name: "130_content"
	compatible_versions[]: "1.29.*"
	compatible_versions[]: "1.30.*"
}
package_version_info : .128_content
{
	package_name: "128_content"
	compatible_versions[]: "1.28.*"
}
package_version_info : .info.downgrade.newer.game.versions
{
    package_name: "downgrade_info_package"
    informational: true
}
}

[Smarty]

Interesting. Afaik, 'best practice' is to always have your package_version_info units ordered by descending compatible_versions. The mod manager will always choose the first unit/package to match the current game version (excluding a proper universal package with no compatible_versions declared).

Here are some examples that use the correct package in 1.31, despite also having packages explicitly for 1.3:

The desired package for 1.31 is .latest (universal version, works correctly):

Code: Select all

SiiNunit
{
package_version_info : .latest {
	package_name: "scr_scot_a2hd"
}
package_version_info : .16.content {
	package_name: "scr_scot_a2hd_ats1_6"
	compatible_versions[]: "1.6.*"
}
package_version_info : .14.content {
	package_name: "scr_scot_a2hd_ats1_4_1_5"
	compatible_versions[]: "1.4.*"
	compatible_versions[]: "1.5.*"
}
package_version_info : .13.content {
	package_name: "scr_scot_a2hd_ats1_3"
	compatible_versions[]: "1.3.*"
}
/*
package_version_info : .12.content {
	package_name: "scr_scot_a2hd_ats1_2"
	compatible_versions[]: "1.2.*"
}
*/
}

The desired package for 1.31 is .current (non-universal, works correctly):

Code: Select all

SiiNunit
{
package_version_info : .latest {
	package_name: "scr_wheel_pack_too_new"
	informational: true
}
package_version_info : .current {
	package_name: "scr_wheel_pack"
	compatible_versions[]: "1.6.*"
	compatible_versions[]: "1.28.*"
	compatible_versions[]: "1.29.*"
	compatible_versions[]: "1.30.*"
	compatible_versions[]: "1.31.*"
}
package_version_info : .pre_1_6 {
	package_name: "scr_wheel_pack_1_2_2_2"
	compatible_versions[]: "1.2.*"
	compatible_versions[]: "1.3.*"
	compatible_versions[]: "1.4.*"
	compatible_versions[]: "1.5.*"
}
package_version_info : .too_old {
	package_name: "scr_wheel_pack_too_old"
	informational: true
	compatible_versions[]: "1.0.*"
	compatible_versions[]: "1.1.*"
}

}

However, the 1.3.* string should never match to 1.31.X.X, so I suppose there is still kind of a bug (sorry I doubted you!). You can probably solve the issue (for now) by moving the .temp_content unit below the .128_content unit.

[Drive Safely]

Now I'm having the same bug with my ETS2 counterpart. I recently moved temp_content to the bottom.

Problem: v18.11 (universal package) is running on 1.30! 130_content package is being ignored. This is a serious bug.

Code: Select all

SiiNunit
{
package_version_info : .universal
{
	package_name: "universal"
	compatible_versions[]: "1.31.*"
}
package_version_info : .130_content
{
	package_name: "130_content"
	compatible_versions[]: "1.30.*"
}
package_version_info : .temp_content
{
    package_name: "temp_content"
	compatible_versions[]: "1.32.*"
	compatible_versions[]: "1.29.*"
	compatible_versions[]: "1.28.*"
	compatible_versions[]: "1.27.2.*"
	compatible_versions[]: "1.27.1.*"
	compatible_versions[]: "1.26.*"
	compatible_versions[]: "1.25.*"
	compatible_versions[]: "1.24.*"
	compatible_versions[]: "1.23.*"
}
package_version_info : .info.downgrade.newer.game.versions
{
    package_name: "downgrade_info_package"
    informational: true
}
}

Is there a difference in having "current" package name than "universal"?

UPDATE: Also tried it in the alternative order but still I get the bug.

Code: Select all

SiiNunit
{
package_version_info : .universal
{
	package_name: "universal"
	compatible_versions[]: "1.31.*"
}
package_version_info : .130_content
{
	package_name: "130_content"
	compatible_versions[]: "1.30.*"
}
package_version_info : .temp_content
{
    package_name: "temp_content"
	compatible_versions[]: "1.23.*"
	compatible_versions[]: "1.24.*"
	compatible_versions[]: "1.25.*"
	compatible_versions[]: "1.26.*"
	compatible_versions[]: "1.27.*"
	compatible_versions[]: "1.28.*"
	compatible_versions[]: "1.29.*"
	compatible_versions[]: "1.32.*"
}
package_version_info : .info.downgrade.newer.game.versions
{
    package_name: "downgrade_info_package"
    informational: true
}
}