[quote who="iboto1"]
- 1. ... text doesn't fit properly ...
- 2. [Influence] ... steal five planets ... and take *no* diplomatic penalty whatsoever.
- 3. The age system seems a bit contrived. ... It seems somewhat arbitrary. Perhaps some level of interdependencies between techs ...
- 4. Can we please make the resources more critical earlier in the game?
[/quote]
Thanks for the fresh eyes! Some of these issues have a bit of history, as Stardock navigates toward a solution.
1. Known font problem. This is at least iteration 2 (or 3?) of a new DX11(?) font that fixes some prior issues on some graphics cards. Obviously, it's not perfect yet (but it's better than it was, when the popups were totally blank for some players). It's on their list, and will surely be fixed.
2. Placeholder AI. The influence-flipping mechanism works
Diplomacy everything is basically in place, but untuned, with no brain. It'll come later.
3. The Age system is (as far as it's been explained/hinted to us, e.g. in dev stream comments) a compromise between being playable, fun, and feasible for their AI. The obvious goal was to prevent beelining to Planetary Invasion (which I guess was the uber-strategy that solved GC2). They know it's a bit of a wet rag for the player, but a strong AI is hard enough to devise even with this simplified mechanism. The "obvious" alternative of a tech graph with many branches and multiple criss-crossing prerequisites might be exponentially harder for an AI to think through (or for the AI developers to code, which is also a relevant cost consideration).
Stardock also sees Ages as a nice scaffold for racial differentiation. The way you encode a racial affinity for a tech branch is by pooching all techs in that branch leftward into the earlier Ages. If the default is that tech level 5 = Age of Expansion in every tech, then you can slide the level 6 techs into AoE to imply a bonus, or push level 5 into AoW to imply a penalty. The player of that race can choose to go for those higher tech levels earlier than other races.
Anyways, they know it's an issue (but it's useful to remind them every now and then, especially with fresh eyeballs). It's rather deeply tied into the entire design, tho, so there are no easy rip-and-replace solutions.
4. Placeholder resources
You're basically correct, and dev stream comments have acknowledged this issue. It's one of the Major(?) Design Features that are still open. Expect a big change in Beta 4+1 or so, when they tune everything.