translators
8,445
edits
Changes
Jump to navigation
Jump to search
Line 45:
Line 45: + + + + + + + + + +
Modding:Modder Guide/APIs/Update checks (view source)
Revision as of 03:37, 24 May 2020
, 03:37, 24 May 2020+ update subkeys in SMAPI 3.6
For example, let's say your mod has two versions available: <code>1.7.0</code> and <code>2.0.0-beta</code>. A player who has <code>1.6.0</code> installed would see an update alert for <code>1.7.0</code>, and a player with <code>1.6.1-beta</code> would see an update alert for <code>2.0.0-beta</code>.
For example, let's say your mod has two versions available: <code>1.7.0</code> and <code>2.0.0-beta</code>. A player who has <code>1.6.0</code> installed would see an update alert for <code>1.7.0</code>, and a player with <code>1.6.1-beta</code> would see an update alert for <code>2.0.0-beta</code>.
===Update subkeys===
{{SMAPI upcoming|3.6|content= 
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.
You can add an ''update subkey'' at the end of your normal update key after <code>@</code>:
<source lang="json">"UpdateKeys": [ "Nexus:2400@GeodeCrusher" ]</source>
When SMAPI fetches available versions from the page, it will only consider files that have <tt>@GeodeCrusher</tt> somewhere in the title or description. (If there are no valid matching versions, it will ignore the subkey and perform a normal update check.)
}}
===Disable update checks locally===
===Disable update checks locally===