improve messages of unmet requirements

[abian]

The following changes may make tips on unmet requirements more consistent and oriented to quick decision-making (and, those that take up more than one line, also shorter).

before	after
Requires five Village Structures. Remaining: 5 entities of class Village	Requires 5 Village Structures.
Requires five Village Structures. Remaining: 2 entities of class Village	Requires 2 more Village Structures.
Unlocked in City Phase.	Requires City Phase.
Insufficient resources: [wood] 490	Requires more resources: [wood] 490
Insufficient population capacity: [population] 3	Requires more capacity: [population] 3

Consistency aside, "Insufficient resources: [wood] 490" concerns me because it doesn't make it clear enough for a beginner whether "[wood] 490" indicates what is still needed or what the player should have in total, whereas I think "Requires" clarifies it.

[Langbart]

• open tickets always have a milestone
  • setting it to A27 for now
• it will either be set to Backlog, dismissed as not worth changing, or it will get some traction and implemented as requested
  • can be argued either way, it's about semantics and not an actual bug

---

The chance of implementation increases if a patch is attached, and it complies with the wiki/EnglishStyleGuide.

[abian]

Thanks for the pointers! I'll submit a patch.

[phosit]

I think "Requires" clarifies it. I don't think it's because of the "Requires" but because of the "more".

[Langbart]

• back to A28, too many string changes

[Stan]

Push back