When 2 entries with the same name exist in the list, using the panel to update one will delete whichever comes later.
An example with this issue:
[{
"name":"Monster Spawn Highlighter",
"link":"http://bit.ly/Sw1AcJ",
"desc":"Highlights any blocks where monsters can spawn.",
"author":["Lunatrius"],
"source":"https://github.com/Lunatrius/Monster-Spawn-Highlighter",
"type":["Client"],
"dependencies":["Forge Compatible","ModLoader"],
"versions":["1.6.4","1.6.2","1.5.2","1.5.1","1.5","1.4.7","1.4.5","1.4.2"]
},{
"name":"Monster Spawn Highlighter",
"link":"http://bit.ly/Sw1AcJ",
"desc":"Highlights any blocks where monsters can spawn.",
"author":["Lunatrius"],
"source":"https://github.com/Lunatrius/Monster-Spawn-Highlighter",
"type":["Client"],
"dependencies":["Forge Required","LunatriusCore"],
"versions":["1.7.2"]
}]Dependencies are different.
In this case, updating Monster Spawn Highlighter to 1.7.10 will delete the second entry and cause incorrect data:
[{
"name":"Monster Spawn Highlighter",
"link":"http://bit.ly/Sw1AcJ",
"desc":"Highlights any blocks where monsters can spawn.",
"author":["Lunatrius"],
"source":"https://github.com/Lunatrius/Monster-Spawn-Highlighter",
"type":["Client"],
"dependencies":["Forge Compatible","ModLoader"],
"versions":["1.7.10","1.7.2","1.6.4","1.6.2","1.5.2","1.5.1","1.5","1.4.7","1.4.5","1.4.2"]
}]The core of the issue is due to the fact that there is no way to identify a mod apart from its name. The panel does not know which entry it needs to update, so the default behavior always prefers the first occurrence and removes the "redundant" data.
When 2 entries with the same name exist in the list, using the panel to update one will delete whichever comes later.
An example with this issue:
[{ "name":"Monster Spawn Highlighter", "link":"http://bit.ly/Sw1AcJ", "desc":"Highlights any blocks where monsters can spawn.", "author":["Lunatrius"], "source":"https://github.com/Lunatrius/Monster-Spawn-Highlighter", "type":["Client"], "dependencies":["Forge Compatible","ModLoader"], "versions":["1.6.4","1.6.2","1.5.2","1.5.1","1.5","1.4.7","1.4.5","1.4.2"] },{ "name":"Monster Spawn Highlighter", "link":"http://bit.ly/Sw1AcJ", "desc":"Highlights any blocks where monsters can spawn.", "author":["Lunatrius"], "source":"https://github.com/Lunatrius/Monster-Spawn-Highlighter", "type":["Client"], "dependencies":["Forge Required","LunatriusCore"], "versions":["1.7.2"] }]Dependencies are different.
In this case, updating Monster Spawn Highlighter to 1.7.10 will delete the second entry and cause incorrect data:
[{ "name":"Monster Spawn Highlighter", "link":"http://bit.ly/Sw1AcJ", "desc":"Highlights any blocks where monsters can spawn.", "author":["Lunatrius"], "source":"https://github.com/Lunatrius/Monster-Spawn-Highlighter", "type":["Client"], "dependencies":["Forge Compatible","ModLoader"], "versions":["1.7.10","1.7.2","1.6.4","1.6.2","1.5.2","1.5.1","1.5","1.4.7","1.4.5","1.4.2"] }]The core of the issue is due to the fact that there is no way to identify a mod apart from its name. The panel does not know which entry it needs to update, so the default behavior always prefers the first occurrence and removes the "redundant" data.