this sort of makes Dark Forecast passable for 2 player mode. Initially, it was only passable if it was one-player-mode as one player could have 11 villages active and could get a good army built prior to the final wave.
2 player suffered from lack of resources to replace losses and would be unwinnable in some cases.
Only 2 cases where it was won in 2 player mode was when the players were of exceptionally high skill level but average skill-levelled players have yet to even win.
This is the only widget in mainline using GUI2's [draw][circle] tag. I'm
currently working on a change to the C++ text_shape class, and want to
be able to regression-test the placement of [circle]s after that change.
I'd be okay with deprecating both [circle] and [round_rectangle] as neither
seems to be used elsewhere, but this close to feature-freeze I'd prefer to keep
them in 1.16 rather than suggest removing them now.
To see the widget, start the game with `wesnoth --clock`, and then click the
button underneath "Quit" on the main menu.
This adjusts to the change in e7b5996e988747c2b590852b4b461abe48857526.
The micro ai itself is unchanged, it's still controlled by `tusker_type` and
`tusklet_type`, it simply needed the new unit ids to be used in this scenario.
The single-character insertion seems unlikely to be used in future. While
pango_text isn't a singleton, a few shared instances are created and then used
in a singleton-like way, with each caller assuming that it received it in an
unknown state and always calling set_text(), set_font_size(), set_font_style(),
etc.
This allows passing an explicit path on Mac (instead of using the automatic -p xcode option), since the binary is not named "wesnoth" on that platform.
SUPPORT.md was a small subset of CONTRIBUTING.md, and CONTRIBUTING.md no longer has a TOOD section and so should be moved to where more people will see it.
Adjusted the weather change effect from side 3 turns to side 1 turns. Side 1 is never empty so it would bypass the side 3 as empty cheat which impeded weather changed.
The log handler does some kind of per-line sorting of these, so a single deprecation warning ends up with the detail line first and the message line second (line order reversed). When there are multiple deprecation messages, their detail lines and message lines get jumbled together. This seems to be tied together with how it detects repeated instances of the exact same error/warning, so putting both the message and the detail on the same line is much simpler than tinkering with that.
