Wesnoth 1.15.15 (1.16 Beta 2)

Get help with compiling or installing the game, and discuss announcements of new official releases.

Moderator: Forum Moderators

Locked
User avatar
Pentarctagon
Project Manager
Posts: 4824
Joined: March 22nd, 2009, 10:50 pm
Location: Earth (occasionally)

Wesnoth 1.15.15 (1.16 Beta 2)

Post by Pentarctagon »

Wesnoth 1.15.15 is out!

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.6 MB)
SHA256 sum: 2ee2f68a11cbeebb67d30638f1d56ba66799430b3f34baf9c0754427862d700f
Windows installer (64-bit) (441.0 MB)
SHA256 sum: 4b67fb56804263d8cf814ab2f8bff5b0f1314d686124cf2e10f51efae55820a2
macOS package (486.3 MB)
SHA256 sum: 0068c996563f8b09b4eb1e6d83e20ff4ac35b9b6ac51588b40e1d344bcf82243
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.
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.
General
  • Unit graphics
    Attack animations have been added to the Jinn.

    The standing animation for the Fire Guardian and Fire Wraith have been updated.

    The attack animations for the Scarab have been updated.
  • Data migration
    When starting a new major version of Wesnoth for the first time - ie: 1.15 vs 1.14, not 1.15.14 vs 1.15.15 - an option will be shown to migrate your preferences as well as attempt to automatically redownload any add-ons you had on the old version that also exist for the new version.
  • Invalid translation text crash
    Translations that contain the "vertical tab" character will no longer cause Wesnoth to crash.
Important changes since 1.14.x
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
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!
99 little bugs in the code, 99 little bugs
take one down, patch it around
-2,147,483,648 little bugs in the code
User avatar
Ravana
Forum Moderator
Posts: 2533
Joined: January 29th, 2012, 12:49 am
Location: Estonia
Contact:

Re: Wesnoth 1.15.15 (1.16 Beta 2)

Post by Ravana »

Notable change in this version is that [store_time_of_day] is working now.
Zolm
Posts: 27
Joined: May 18th, 2012, 1:30 am

Re: Wesnoth 1.15.15 (1.16 Beta 2)

Post by Zolm »

Hello guys. Didn't log for a while, so I jumped from 1.12 straight to 1.15. A small question about the upkeep tag in singleUnit: has it been modified in the newer versions? The page doesn't have any new notes for it (https://wiki.wesnoth.org/SingleUnitWML), it still has the values I remember, full, free, loyal, and the integer number. However, it seems the "integer number" now behaves as "natural number", since it's ignoring negative upkeeps and instead using the unit's level as default upkeep.

For example, This is a screen from 1.12; I quickly edited a scenario from an existing campaign and inserted an extra unit in the code with a -30 upkeep cost:

Image

So the unit, by itself, would have no upkeep, and can hold up to 30 units' levels by itself on this extreme example. I intended to use this feature in a campaign of mine, but the fact is I will never finish it, so it's no big deal anyway. In 1.15 this doesn't work anymore.

Just curious if the behavior was changed throughout the versions and the page wasn't updated, or if it's a bug from new versions (didn't download 1.14 to confirm).
User avatar
Pentarctagon
Project Manager
Posts: 4824
Joined: March 22nd, 2009, 10:50 pm
Location: Earth (occasionally)

Re: Wesnoth 1.15.15 (1.16 Beta 2)

Post by Pentarctagon »

My guess is that it was just never updated to specify that the upkeep can't be negative.
99 little bugs in the code, 99 little bugs
take one down, patch it around
-2,147,483,648 little bugs in the code
User avatar
Ravana
Forum Moderator
Posts: 2533
Joined: January 29th, 2012, 12:49 am
Location: Estonia
Contact:

Re: Wesnoth 1.15.15 (1.16 Beta 2)

Post by Ravana »

When relying on feature which other people might not see as important, it can be useful to create test for it so people dont unintentionally break it https://github.com/wesnoth/wesnoth/blob ... grades.cfg
Locked