Wesnoth 1.15.16 (1.16 Beta 3)

[Pentarctagon]

Wesnoth 1.15.16 is out!

Get on Steam

This new release in the 1.15.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.15.x series, but for others we depend on contributed patches from volunteer coders like you!

Downloads

Source code (471.8 MB)
SHA256 sum: e4c3d8d362e0ef38b8c23fdb6d6dd688a7ad616dfdd810a19a521fa3a36a1da7

Windows installer (64-bit) (441.4 MB)
SHA256 sum: 1566096c0a955545a41a0e81f89a3f754c7656709478f771489484265b1394b4

macOS package (486.4 MB)
SHA256 sum: 44b823b08992f29514b1c2599ce92dd913efd28debfa7744ccf6a7abb7de5e65

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.15.x option from the drop down.

Itch.io

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»

• Unit graphics
  Improved defense animations have been added for trolls.
  Additional animations have been added for the Naga Shield Guard and Naga High Guard units.
  Attack and defense animations have been added for the Naga Ringcaster.

Changes To Existing Content»

• Campaign selection HiDPI
  The campaign selection dialog now scales to be better displayed on HiDPI monitors.

Fixes»

• Tutorial out of sync error
  The character choice dialog is no longer shown when watching the replay of the first scenario of the Tutorial. If it was shown and the watcher chose a different option than the original play through did, this would result in out of sync (OOS) errors to occur as the replay continued.
• Secrets of the Ancients (SotA) out of sync error
  The zombie recruit dialog is no longer shown when watching replays of SotA. If it was shown and the watcher chose a different option than the original play through did, this would result in out of sync (OOS) errors to occur as the replay continued.

Important changes since 1.14.x

Minimum Requirements»

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

General

• The minimum required version of GCC is now 7.
• Wesnoth no longer depends on SDL_ttf 2.0 for building and the option to use FriBidi for right-to-left (RTL) text rendering has been removed in favor of using Pango. It is worth noting that RTL language support in general is currently broken (#5600), and there are no active RTL language translations either.

Windows:

• Windows 7 is now the minimum supported version.
• Wesnoth now supports only the 64-bit versions of Windows.

macOS:

• Wesnoth now uses the app sandboxing feature, which means there is a new location for saves. All saves will be migrated during first launch automatically. For info about backwards compatibility see here.
• Starting with 1.15.5, the minimum required version of macOS is 10.11, and the recommended version is 10.14.

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!

[vghetto]

Hi!

When you have a long list of [message][option], it will default to starting on the 3rd entry for some reason. This didn't happen in 1.15.15.

When you have one or two options, by default it will highlight the first entry. But when you have three or more entries, by default it will highlight the third entry.

Was this an intentional change?

Code: Select all

        [set_variable]
            name=selected_options
            value=3
        [/set_variable]

        [while]
            {VARIABLE_CONDITIONAL selected_options greater_than 0}
            [do]
                [message]
                    speaker=harry
                    message=_"A list of options..."
                    [option]
                        label=_"option 1"
                        [command]
                            {VARIABLE_OP selected_options sub 1}
                        [/command]
                    [/option]
                    [option]
                        label=_"option 2"
                        [command]
                            {VARIABLE_OP selected_options sub 1}
                        [/command]
                    [/option]
                    [option]
                        label=_"option 3"
                        [command]
                            {VARIABLE_OP selected_options sub 1}
                        [/command]
                    [/option]
                    [option]
                        label=_"option 4"
                        [command]
                            {VARIABLE_OP selected_options sub 1}
                        [/command]
                    [/option]
                    [option]
                        label=_"option 5"
                        [command]
                            {VARIABLE_OP selected_options sub 1}
                        [/command]
                    [/option]
                    [option]
                        label=_"quit. ($selected_options| left)"
                        [command]
                            {VARIABLE selected_options 0}
                        [/command]
                    [/option]
                [/message]
            [/do]
        [/while]

        {CLEAR_VARIABLE selected_options}

[Pentarctagon]

It was not an intentional change. Can you open an issue for it on Wesnoth's github?