Open wake42 opened 2 years ago
If we can get it into something like this then being sorted by name after localization doesn't matter. I'm not sure how to go about this in html/css though:
I also had another idea to fix this. If we let the item name be translated to whatever, but require an english name as well, then the actual item name will be shown in the compendiums etc, but we could use the data.en-name to know which rune it is. Haven't thought this through though...
Yes, I think we need some absolute way to reference the runes if we're going to use absolute positioning or something like that to place them on that image in the right place. Maybe all we need to do is put the rune value and the rune experience check box in the right place and then actually localize the underlying image. Or we can use that image and take out the text and replace it with the localized name of the rune. Regardless we need a way to know for sure which one to put where.
Problem of referencing runes would be solved by #199. Leaving only to solve the layout if some runes are missing.
Also keep in mind that Actors might get "extra runes that don't fit in the layout shown above. Like if you gain the Infinity rune or Dragon rune, or if you're an elf and have Plant <> Man in opposition. I think a list of any extra runes below this layout would be fine.
The Man <> Beast Form Rune opposition going through the Power Rune Affinities is cool, but it would be neat if we could make it so that you could change the runes in the layout, so an elf could have Plant <> Man there instead, for example.
Also Illumination allows you to unlink opposed Runes. It think it would be cool if those runes stayed where they were and the line between them simply went away.
And NPCs might not have the full compliment of runes. It might be nice to have just a simple "List View" as an option that you can switch to instead of the full layout.
Don't look too hard at the screenshot above, the starter set runes have a different look. And I think we should implement something that works well on screen – not blindly copying the paper character sheets. And yes, the layout should be able to dynamically handle "missing" runes as well as different combinations like man<->beast & man<->plant etc.
The layout of the rune tab is currently hard coded to the rune names. This doesn't work if the names are translated. It also works badly if not all runes are there since opposed runes look bad if the opposed is missing.
Loose ideas: It would be nice if the runes were drawn from the opposed / minor data...
Blocked by