Wesnoth 1.16.11

[Pentarctagon]

Wesnoth 1.16.11 is out!

Get on itch.io

Get on Steam

1.16 Release Notes

This is a regular maintenance release for the stable 1.16.x series, delivering bug fixes and translation updates. As is the norm for updates to the current stable series, this release is fully compatible with previous 1.16.x versions.

A full list of changes and new features added since version 1.14 can be found in the release notes for this series.


Downloads

Steam
The latest stable version of Wesnoth is published on Steam and regularly receives translation updates between releases.

Itch.io
The latest stable version of Wesnoth is also published on itch.io. A standalone portable download is also available.

Windows installer
SHA256 sum: 015433c95d27dace3ed9af71523d8c40d0130be44ea38143a91474848d89b5ae
NOTE: Due to how expensive it is, Wesnoth's installer is not signed. This often results in the installer being flagged as potentially dangerous by antivirus software because the publisher is unknown.

macOS package
SHA256 sum: 8cd4af79e180ae90fbdbf740d63f26b0ac05826230eddd96b88c895f59a6525f

Source code
SHA256 sum: 5761867f0346d554e63958b9680ad268385218a5547141310877837d3a2882db

Linux
All known Linux packagers have been contacted, and binaries for your distribution may have already been created. Information about where to get the respective binaries and how to install them, including via Flatpak, can be found on the Linux binaries page in the wiki.

Changes in this release

Read on for more details about the most notable fixes and additions since the previous stable release. A full list of changes may be found in our changelog.

[ Expand all ]

General

Fixes»

• Inspect dialog pagination
  Fixed a crash in the :inspect window when pagination is used.
• Add-on version check database
  Fixed the source of the error message: "Something is wrong with the add-on version check database supporting the multiplayer lobby". Note that this also required the host of the game to use Wesnoth 1.16.11.

Known Issues

New in 1.16.x»

General issues:

• OneDrive can interfere with Wesnoth’s user config/data directory set-up, leading to all kinds of different manifestations of the issue. There’s no fix available yet. The recommendation for the time being is to avoid syncing the Wesnoth user directory with OneDrive.

Carried over from 1.14.x»

General issues:

• Preprocessor errors corrupt cache (issue #1924). If this happens you have to wipe your cache. That can be done in Preferences → Cache.

⁂

If you find any bugs, do not hesitate to report them, but please read the instructions on how to report bugs first! As bug reports in the forums tend to be forgotten, you will get better results using our bug tracker. We require your help for finding and fixing issues, no matter how obvious, trivial, or complicated they seem!

Have fun!

[ObaniGarage]

This release doesn't run on the GNU/Linux version on Steam. the flatpak works fine, and running the game through Proton works fine, but for some reason it crashes without even rendering a window on the Steam linux version (Also, alt-tabbing in full screen crashes the game with the flatpak version)

[Pentarctagon]

It works fine on Linux+Steam for me at least.

[Atreides]

Also, alt-tabbing in full screen crashes the game with the flatpak version)

Seconded! (By alt tabbing I assume you mean switching desktops I don't have such a key setting, I use CTRL-F1-4 and it crashes sometimes (50% I'd guess))

[Pentarctagon]

Does it also crash when using the 1.17 flatpak (https://wiki.wesnoth.org/WesnothBinariesLinux#Flatpak)?

[Atreides]

Does it also crash when using the 1.17 flatpak (https://wiki.wesnoth.org/WesnothBinariesLinux#Flatpak)?

I've been trying hard to get it to and no, neither 1.14 flatpak nor any of the 1.17 flatpaks crash ever.

Best as I can tell is that it started around 1.16.10 (maybe earlier - I skipped from .2 to it or something close to that) and it isn't always a "crash" but what happens is the screen gets garbled (several ways, at first it just becomes random blotches and then when you send it the kill signal first time the screen goes blank except for a few pixels in the upper left corner until you send a second kill signal which finally stops it) and while the program runs fine (music still plays, sound effects etc.) it obviously has to be sent a kill msg.

So yeah, it's probably something that can just be worked around for the little while 1.16 has left to "live". LOL. I've turned on autosaves again (had them off) for when I forget to be careful and the rest of the time I'm just careful to monotask with 1.16.

In any case maybe this info will be of some use in case there's some deep underlying problem. Considering how unreproducible and inconsistent it is though there's no chance this could ever be fixed.