translators
8,437
edits
Changes
Modding:Modder Guide/APIs/Update checks (view source)
Revision as of 18:52, 15 July 2020
, 18:52, 15 July 2020→Update subkeys: update for SMAPI 3.6 release
===Update subkeys===
===Update subkeys===
SMAPI assumes each mod page is about a single mod, so the highest file version is the latest one. That means having multiple mods on the same page can cause false update alerts. For example, let's say you have one Nexus page with two different mods in the downloads: ''Geode Crusher'' (version <code>1.0.5</code>) and ''Diamond Crusher'' (version <code>2.1.0</code>). If a player has the latest version of ''Geode Crusher'' installed, they would always get update alerts for version <code>2.1.0</code> even though that's a different mod.
SMAPI assumes each mod page is about a single mod, so the highest file version is the latest one. That means having multiple mods on the same page can cause false update alerts. For example, let's say you have one Nexus page with two different mods in the downloads: ''Geode Crusher'' (version <code>1.0.5</code>) and ''Diamond Crusher'' (version <code>2.1.0</code>). If a player has the latest version of ''Geode Crusher'' installed, they would always get update alerts for version <code>2.1.0</code> even though that's a different mod.
* If no files match the subkey, SMAPI will ignore the subkey and perform a normal update check.
* If no files match the subkey, SMAPI will ignore the subkey and perform a normal update check.
* For mods on CurseForge, SMAPI won't see subkeys in the file description since that's not available through the API.
* For mods on CurseForge, SMAPI won't see subkeys in the file description since that's not available through the API.
===Disable update checks locally===
===Disable update checks locally===