When updating a mod, its dependencies are not shown in the panel.
For example, with this mod:
{
"name":"Not Enough Items",
"other":"(NEI)",
"link":"http://bit.ly/UvpH6y",
"desc":"NEI is ...",
"author":["chicken_bones"],
"type":["Universal"],
"dependencies":["Forge Required","CodeChickenCore"],
"versions":["1.7.2","1.6.4","1.6.2","1.5.2","1.5.1","1.5","1.4.7"]
}Updating it to 1.7.10 will not show CodeChickenCore as a dependency in the panel form, and must be re-added manually.
The issue is that the submission form only supports the requirement of Forge, namely Forge Required, Forge Compatible and Not Forge Compatible. This data is saved as a string, instead of an array, and the panel prefers the submission data over the already known data.
Ideally, this data should be separate from the dependency field, as the real dependency should be Forge, LiteLoader, etc.
When updating a mod, its dependencies are not shown in the panel.
For example, with this mod:
{ "name":"Not Enough Items", "other":"(NEI)", "link":"http://bit.ly/UvpH6y", "desc":"NEI is ...", "author":["chicken_bones"], "type":["Universal"], "dependencies":["Forge Required","CodeChickenCore"], "versions":["1.7.2","1.6.4","1.6.2","1.5.2","1.5.1","1.5","1.4.7"] }Updating it to 1.7.10 will not show CodeChickenCore as a dependency in the panel form, and must be re-added manually.
The issue is that the submission form only supports the requirement of Forge, namely Forge Required, Forge Compatible and Not Forge Compatible. This data is saved as a string, instead of an array, and the panel prefers the submission data over the already known data.
Ideally, this data should be separate from the dependency field, as the real dependency should be Forge, LiteLoader, etc.