Wesnoth 1.17.7

[Pentarctagon]

Wesnoth 1.17.7 is out!

Get on itch.io

Get on Steam

This new release in the 1.17.x development series sees various changes and improvements in various areas.

As this is a development version, we would like to remind everyone how the testing and feedback process works for these:

• If you download Wesnoth stand-alone, make sure to keep the latest stable release around in case the game breaks and you find yourself unable to get your daily fix of Wesnoth.
• Playtest the game, and make sure to report any bugs you find! Even obvious bugs can be left unfixed if everyone assumes someone else has already reported it.
• For any bugs found, or to request new features to be added, check out bug tracker here. First though, please read our instructions for reporting bugs on the wiki, which will give your bug report or feature request the best chance of being addressed.
• Near the end of the release notes below you will find a list of the most important bugs known at the time of the release. Some items are due to be fixed in future releases of the 1.17.x series, but for others we depend on contributed patches from volunteer coders like you!

Downloads

Steam
Development versions of Wesnoth are available on Steam through our beta channel.
In your Steam library: right-click on Battle for Wesnoth, select Properties, go to the Betas tab, and select the 1.17.x option from the drop down.

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

Windows installer (64-bit)
SHA256 sum: 88ba7bdd0920a31bf384aa74cfd52833a38fb44fc2a915c0c7be9fe38f82dc42
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: a7b9abd598ca233708433a8920dfadd0adf3e815bc7f64f66ea2adc7f1302dd8

Source code
SHA256 sum: c6d0c46a296394a619eba5875124cc151e53e21a0c284c41fde24e87ccb42f1a

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 development release. A full list of changes may be found in our changelog.

[ Expand all ]

General

New Content»

• Additional icons for unit stats
  In the in-game help, unit descriptions now have icons for attack types as well as show visually how many hexes a unit can move over particular terrain.
• Lowered terrain
  It's now possible to make terrain appear visually lower than other hexes.

Changes To Existing Content»

• Hotkey changes
  The default hotkeys for some actions have been updated:
  • Continue is now `C` instead of `T`
  • Go to Leader is now `K` instead of `L`
  • Kill Unit is now `DEL` instead of `X`
  • Undo is now `Z` or `CTRL + Z` instead of `U`
  • Redo is now `SHIFT + Z` or `CTRL + SHIFT + Z` instead of `R`
  • Planning mode is now `ALT + P` instead of `P`
  • Delete Action (Planning Mode) is now `BACKSPACE` instead of `H`
  • Suppose Dead (Planning Mode) is now `X` instead of `I`
• Add-on downloading progress bar
  The progress bar shown when downloading and installing an add-on now more correctly displays how much work remains to be done.

Fixes»

• Text overly bold
  On Windows text was being displayed as "bold" without changing the spacing between letters, making reading said text more difficult. This has been fixed.
• Flying units with leadership
  Fixed flying units with leadership not being displayed correctly when on a water tile.
• Various issues when using zoom
  Multiple issues with displaying units when zoomed in or out have been fixed.

Miscellaneous improvements»

• Logging
  On Steam, for Linux users, Wesnoth now logs to a file so that errors and warnings can be viewed more easily.
• Packaging
  The minimum Pango version is now 1.44.
• Credentials file encryption
  The credentials file used to store multiplayer server passwords is now using a different encryption algorithm to secure them. As such, when switching between 1.17 and other branches, you will need to re-enter your password when connecting to the multiplayer server.

Important changes since 1.16.x

Minimum Requirements»

This information applies to all 1.17.x development releases unless specified otherwise.

General

• Webp support is now required for SDL2_image.

Known Issues

Carried over from 1.14.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.
• Preprocessor errors corrupt cache (issue #1924). If this happens you have to wipe your cache. That can be done in Preferences → Cache.

New Contributors and Developers

Do you want to help shape the future of Wesnoth? You are always free to join us in the #development Discord channel or #wesnoth-dev IRC channel on libera.chat to ask for help with getting started!

⁂

The multiplayer and add-ons servers for this development series are up and running. Because development versions are a moving target, the development multiplayer server only accepts the latest version in the series. Add-ons may break due to changes to the WML and Lua APIs throughout development series — any problems involving them should be reported to the respective add-on maintainers.

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!

[Temuchin Khan]

I played 1.17.7 a few times, and it seems to crash frequently. More precisely, it makes the screen freeze up and I have to restart the computer.

[Pentarctagon]

Without more information it's unlikely we'll be able to track down the issue, though freezing your entire PC is definitely unusual. Is there anything in the logs?

[Temuchin Khan]

Without more information it's unlikely we'll be able to track down the issue, though freezing your entire PC is definitely unusual. Is there anything in the logs?

Right now, I don't think I have anything. I'll see if it happens again.

EDIT:. Actually, it might not have crashed the computer. I was in full screen mode, so even if just Wesnoth crashed, I had no way to quit out of it.