I haven't had a lot of opportunity to sit down and really work on this, but I have been thinking about it quite a bit. I should have a comprehensive list made by the end of this week. However, the one thing that might slip through is if the same button gets used with two different file names. For example, Barracks and Garrison use the same icon, but they have different file names and so the only way we can tell they are the same is by an eyeball search.
I think there a few duplicate icons that I'm not going to change.
First, there are several unit class icons (Melee, Mounted, Siege, Gunpowder) that also use the same button for the anti-class promotion (Shock, Formation, Charge, Pinch). Since BTS did this, I think this is okay. It also helps make the icons MORE recognizable by giving a visual cue to what the promotion is supposed to do.
The other is that Automate Worker and Automate Missionary/Executive use the same button (the four arrows pointing to the corners). Again, BTS did it first, and I don't think there is any room for confusion. Worker units, Missionary units, and Executive units all have one purpose and having a single Automate button (do what you are built to do) is fine. Furthermore, Automate Missionary/Executive is one mission in the XML, and I wouldn't want to create separate missions for both.
I think there a few duplicate icons that I'm not going to change.
First, there are several unit class icons (Melee, Mounted, Siege, Gunpowder) that also use the same button for the anti-class promotion (Shock, Formation, Charge, Pinch). Since BTS did this, I think this is okay. It also helps make the icons MORE recognizable by giving a visual cue to what the promotion is supposed to do.
The other is that Automate Worker and Automate Missionary/Executive use the same button (the four arrows pointing to the corners). Again, BTS did it first, and I don't think there is any room for confusion. Worker units, Missionary units, and Executive units all have one purpose and having a single Automate button (do what you are built to do) is fine. Furthermore, Automate Missionary/Executive is one mission in the XML, and I wouldn't want to create separate missions for both.