@Per - Could these changes be made to research objects....?
1. Rename .name field to .id as what's in there is the id from research.txt, not it's name
2. Add a .name field that contains the human-friendly name (untranslated) for the research from names.txt
For example, an object describing supercrete will have:
.id = R-Defense-WallUpgrade04
.name = Supercrete
So the .id is from research.txt, the .name is from names.txt. This will make research objects more consistent with droid/structure objects (in terms of how they use their .id and .name fields).
3. If the tech enables a structure, could a .structure property be added - it would contain the id of the structure that I can build after researching that tech? If tech doesn't give rise to a structure then the .structureid property will have a value of null. (for example, the .id=R-Defense-HardcreteWall technology allows me to make .structure=A0HardcreteMk1Wall)
.name property on research objects
.name property on research objects
"Dedicated to discovering Warzone artefacts, and sharing them freely for the benefit of the community."
-- https://warzone.atlassian.net/wiki/display/GO
-- https://warzone.atlassian.net/wiki/display/GO