Follow-up Comment #1, bug #9267 (project wesnoth):
After looking at the scenario file, I'd venture a guess that "team-name" keys
had been edited, and "user-team-name" keys left unedited, and thus incoherent
with the real situation.
I can't say _how_ the consistent relationship between user visible names and
internal team definitions can be enforced, but it really _should_ be made
harder (I won't say impossible...) to create confusion by this trick.
Maybe only allow *exactly one* ("per .cfg-file") definition of any one
*team-name / user-team-name relationship*, at the beginning of the scenario
file, and then only use the team-name key in single _side_ definitions? If
you can also disallow (throw an error) using an _identical_ user-team-name
definition for two _differing_ team-name keys, that would definitely be
good.
Ps. I had to convert underscores in the key-names to dashes because of how I
think gna treats underscores.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?9267>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
