Wesnoth 1.15.7

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

Moderator: Forum Moderators

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

Wesnoth 1.15.7

Post by Pentarctagon »

Wesnoth 1.15.7 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 (460.6 MB)
SHA256 sum: 2410ef3eac29066c54b08d972b54a2ec394421e8e6359e26e881cd6d861b9f59
Windows installer (64-bit) (427.5 MB)
SHA256 sum: 921bd8cd2b1b4ef56aef9d8b03a10c09a74eda3caaa39a4a1c851c02e3b93c2f
macOS package (459.9 MB)
SHA256 sum: 763083d797de2363c9b173c66ed92c204f31c192f8612f3826c693254a8a893b
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
  • View Help In Multiplayer Lobby
    It is now possible to use the F1 key to view the in-game Help in the multiplayer lobby.
  • Add-ons Manager
    It's now possible to install or switch to any version of an add-on if it is available on the server using the new dropdown list in the add-ons manager UI.
  • Replay Chat
    It is now possible to set the Chat Lines preference to 0. This will prevent any of the game chat from showing up while watching a replay.
  • Unit Balancing
    • Dune Rider: XP changed from 42 to 47.
    • Sunderer line: Defense on hills changed from 60% to 50%.
    • Scorcher: Gold cost changed from 23 to 25.
    • Dragoon: Gold cost changed from 27 to 28.
    • Elvish Rider: Gold cost changed form 32 to 28.
  • Scepter of Fire: Scenario 4
    A bug introduced in 1.15.3 prevented players from winning because the gold deposit that should have been collected to finish the scenario was never spawned. It can once again be completed by collecting all resource deposits on the map and returning them to the starting castle.
  • Unit Statuses
    In previous 1.15 releases, unit statuses like Poisoned and Slowed were no longer being shown in the game sidebar. This has been fixed and statuses will once again be shown.
  • Dismissing A Unit When There Are None
    In previous releases it was possible to cause Wesnoth to crash by clicking the Dismiss button in the Recall Unit dialog when there were no units possible to recall.
  • Editor Crash When Switching Scenarios
    When switching from a scenario in the editor that has more sides than the scenario being switched to, it was possible for the editor to crash back to the main menu. This has been fixed.
  • Editor Crash When Dragging Labels
    In previous releases, attempting to drag and drop a label in the editor could result in a crash. This has now been fixed.
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 to compile Wesnoth is now 5.4.
Windows:
  • Windows 7 is now the minimum supported version.
  • The stand-alone download from SourceForge is now 64-bit, and we expect the Steam version to also become 64-bit in the near future. As such, 32-bit versions of Windows will no longer be supported.
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 irc.freenode.net 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
Post Reply