The Battle for Wesnoth Forums

There's only one or two who might not have known - everyone else would've either been included in the developer group ping about it on Discord or I've otherwise seen them mention it so I know from that they're aware.

It means that player's client tried to send data to other clients when it isn't supposed to, which almost certainly means there is or soon will be out of sync issues.

From where?

April is added.

Also would need a way to limit how much disk space such saves could take up.

It's just because the executable isn't signed. It's fine to download.

Just in case - AI art isn't currently allowed.

The skull is definitely what threw me off - it definitely looks better/clearer with the whiter color. The staff being more elven makes sense though, I'd say.

It looks like we'll need to drop out - calculated the timezone difference between us backwards, so it turns out the only time I can play is in the middle of the night for Skyend.

It's close enough to flesh-colored that it's not immediately obvious that it's a skull - even I had to look closely at it to notice.

See https://wiki.wesnoth.org/ScenarioWML#Th ... rio.5D_tag

Thoughts: Urza said "get em boys" and then didn't recruit anyone or have any already existing units on the map, which was funny but seems unintended? The image used when talking about ToD is very small. It's easy to miss the text in the upper left corner changing, though I don't have a bet...

Based on the responses received to the previous thread , the candidates to be the Project Manager for the 1.18/1.19 development cycle are: Pentarctagon Vultraz Those eligible to vote are: celtic minstrel charles dang (vultraz) doofus-01 elvish_hunter gfgtdf gunter labes (Soliton) hejnewar jonathan-k...

Sounds like a lot of good changes and a lot of improvements to make the campaigns more interesting

One question: are there any plans to have another MP campaign now that LoW is going back to being single player, or is that not something that really fits well anywhere?

It's a known side effect of the rendering overhaul that was done during 1.17: https://github.com/wesnoth/wesnoth/issues/8728