Release Notes 1.15.4

From The Battle for Wesnoth Wiki
Revision as of 19:00, 17 August 2020 by Hejnewar (talk | contribs) (Changes To Existing Content)

Instructions

This page is for documenting changes made between the 1.15.3 and 1.15.4 releases that are especially important or otherwise notable to players and-or UMC authors. The description of changes added here should be more verbose and detailed than what would be included in the regular changelog on github, and most importantly, should be written with the intended audience being non-developers - no prior knowledge or knowledge of Wesnoth's inner workings should be needed in order for players to understand the entries added here.

New Content

Addon titles and descriptions made translatable

It's now possible to add translated titles and descriptions to your addons, so they will show up in the target language when browsing the in-game addon manager. The original English title is also displayed below and can be searched for in addition to translations. If you want to add a translated title and description to your addon, follow the wiki page https://wiki.wesnoth.org/PblWml#.5Btranslation.5D .

Changes To Existing Content

Balance changes

Drakes

Drake Burner line and Armageddon Drake cold resistance changed from -50% to -40%.

Knalgan Alliance

Dragonguard hp changed from 59 to 63.

Dwarvish Steelclad hp changed from 55 to 57.

Poacher hp changed from 32 to 33.

Loyalists

Heavy Infantryman cold resistance changed from -10% to 0.

Northerners =

Troll Rocklobber hp changed from 49 to 51.

Rebels

Merman Hunter hp changed from 30 to 33.

Shaman ranged damage changed from 3 to 4.

Wose cold resistance changed from 10% to 0.

Undead

Banebow hp changed form 50 to 52.

Bone Shooter hp changed from 40 to 42.

Ghost cost changed from 20 to 19.

Monsters

Various changes to Wyvern, Wyvern Rider, Roc, Falcon and Elder Falcon.

Fixes

Graphics engine memory leak fix

An issue dating back to version 1.13.13 was found in the game’s graphics engine that would result in large memory leaks over time, particularly evident after performing a few save-reloading or game initialization (Campaign mode, Multiplayer, Map Editor) cycles. On Windows and other systems running 32-bit builds of the game, this could eventually result in a game session crashing due to reaching platform-mandated memory limits. Furthermore, either 32-bit or 64-bit systems with small amounts of available RAM could perceive substantial performance degradation during long game sessions, or even crashes in other running software.

General/Misc

Newly Introduced Issues