Version 0.11.2.4: Changes To Mod Management & Uploads
Everyone loves modding! However, it's easy to break things if you're not cautious and change things like mod or asset IDs. It's also easy to glance over documentation.
Unfortunately, I had to deal with ID conflict issues in the past two days where mod creators have unknowingly broken their mod compatibility with older dungeons because they did not account for making asset IDs backwards compatible.
This new update introduces two new safety measures which will prevent those mod compatibility issues in the future:
[h2]1. Manual Mod Version Increments[/h2]
The "Version" property in your Mod.yaml no longer defines what game version the user requires, but rather denotes the version of your mod.
It's recommend to start your mod at version "1.0.0.0" when you first upload it to the workshop.
If you want to update your mod after making changes, you have to manually increment the version number, let's say to "1.0.0.1". If you leave the mod version unchanged, the mod will not be updated in the workshop.
This change makes the mod creator's intent more clear and will also allow me to version mod's in the engine itself.
[h2]2. Asset Key Validation[/h2]
From now on, when uploading or updating a workshop mod, all asset keys are added to the workshop item's metadata.
Let's say you have a tree entity with the id "MyTree" and your mod ID is "MyCoolMod".
The mod asset reference of that asset is "MyCoolMod:MyTree", and the asset key would be "MyTree".
The ID is optional, but it's recommended to explicitly set it, otherwise it uses the file name as the ID, which is more prone to accidental breaking.
When attempting to update a workshop mod, the game checks to see if all the asset keys that the metadata contains are still valid in your updated mod.
If that is not the case, that means you have made a breaking change which in theory would prevent users from loading their dungeons, in case they have used your mod in the past.
Generally I don't encourage changing IDs, however if you need to do so, make sure to use the Alias property to make your assets backwards compatible.
You can have as many aliases as you need.
[h3]Happy Modding![/h3]
Unfortunately, I had to deal with ID conflict issues in the past two days where mod creators have unknowingly broken their mod compatibility with older dungeons because they did not account for making asset IDs backwards compatible.
This new update introduces two new safety measures which will prevent those mod compatibility issues in the future:
[h2]1. Manual Mod Version Increments[/h2]
The "Version" property in your Mod.yaml no longer defines what game version the user requires, but rather denotes the version of your mod.
It's recommend to start your mod at version "1.0.0.0" when you first upload it to the workshop.If you want to update your mod after making changes, you have to manually increment the version number, let's say to "1.0.0.1". If you leave the mod version unchanged, the mod will not be updated in the workshop.
This change makes the mod creator's intent more clear and will also allow me to version mod's in the engine itself.
[h2]2. Asset Key Validation[/h2]
From now on, when uploading or updating a workshop mod, all asset keys are added to the workshop item's metadata.
Let's say you have a tree entity with the id "MyTree" and your mod ID is "MyCoolMod".
The mod asset reference of that asset is "MyCoolMod:MyTree", and the asset key would be "MyTree".
The ID is optional, but it's recommended to explicitly set it, otherwise it uses the file name as the ID, which is more prone to accidental breaking.When attempting to update a workshop mod, the game checks to see if all the asset keys that the metadata contains are still valid in your updated mod.
If that is not the case, that means you have made a breaking change which in theory would prevent users from loading their dungeons, in case they have used your mod in the past.
Generally I don't encourage changing IDs, however if you need to do so, make sure to use the Alias property to make your assets backwards compatible.
You can have as many aliases as you need.[h3]Happy Modding![/h3]
Choose from a large selection of tracks, including modded tracks.
Play music conditionally!
Out of sight, out of mind.
Nini is in da house.
The new Entity type is super flexible.
Modded entities show up in the "Mods" group in Gizmos.
Doesn't that look good?
"We have new bosses at home." The new bosses at home:
