From 5 to 4. Makes moving them from one water body to another somewhat less tedious. Likewise makes merfolk units a bit more viable on maps with separated waterways.
* Fix wmllint translation mark errors
* Added wesnoth-help domain
* Try to give better labels for the WC map generator settings which are now marked for translation.
Co-authored-by: Wedge009 <wedge009@wedge009.net>
* Give Shyde and Sylph unwalkable flight
With the same unwalkable terrain movement and defense as the Quenoth versions of these units. Makes them behave as true flying/floating units as their wings, movetype name and other statistics suggest, while opening up interesting game play possibilities.
* revise I-type terrain codes so they can be filtered with wildcard
* update the few MP maps using these I-type codes
* update the few campaigm maps using these I-type codes
* stone border revision
* corner case transitions
* add MP example scenario/map for elevated terrain
* simplify the floodfill
* change ravine from ^Qhx to ^Qhux, for better filtering
* reorganize images
From [this post](https://forums.wesnoth.org/viewtopic.php?p=675918#p675918)
Simplify speech style
Simplify objectives
Lore books give experience to their discoverer
Cuttlefish advance to Krakens
Add Storm Daemon
Rebalanced Normal difficulty mode to be easier
Rebalanced Difficult difficulty mode to be harder
Rebalanced Nightmare difficulty mode to be more self consistent
Intendants now have normal loyal trait
S1: Add a further dialogue hint that oases heal
S4: Dialogue hints for strategic weaknesses of each mermish commander
S6: Give player a couple level 2 clashers
S9: Critical fixes for bugs that could make this scenario unwinnable
S10: Fix bug preventing gryphons from spawning after dwarf tunnels collapsed
New macros:
* SCREEN_FADE_OUT - to replace FADE_TO_BLACK in most cases
* SCREEN_FADE_IN - to replace FADE_IN in most cases
* SCREEN_FADE r g b duration
- convenience wrapper for [screen_fade] with 255 alpha
* SCREEN_UNFADE duration
- convenience wrapper for [screen_fade] with 0 alpha
* FLASH r g b actionWML
- like FLASH_WHITE etc but takes a colour
* FLASH_LIGHTNING actionWML
- flashes an appropriate colour and plays lightning.ogg
Modified macros:
* FLASH_WHITE/RED/GREEN/BLUE}
- these now use [screen_fade] not [color_adjust]
Using colors to make relevant information stand out at a quick glance.
The six attack type icons are recolored using the six equidistant hues cyan, green, yellow, red, magenta and blue, with the same saturation and lightness as the old icons. The images are optimized with woptipng.
Resistances and movement costs are colored using a gradient from red to green, like the defense values.
The resistance table in the help browser now also shows the attack type icons.
Previously, the resistance table was always ordered alphabetically by their original English names (not their translation, unlike the terrain modifiers). Now, the order is set to blade - pierce - impact - fire - cold - arcane.
These changes are made in all relevant areas, including the help browser, tooltips, the sidebar and dialogs.
Missing icons are handled by replacing them with a blank image scaled to the same size.
Re-created hotkeys file.
Borrows heavily from https://r.wesnoth.org/t41525.
Most of the common commands now have single keystrokes on the keyboard in addition to their currently defined keystrokes. Almost everything remains the same, except the following has changed:
* 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`
Many items where the effect does not make sense (or looks especially
bad) were passed over and will appear on top of water as previously.
This could use more definition by using submerge values other than
0 and 1 (numbers from 0.0 to ~2.5 work as it multiplies the base
unit submerge value) however there is a bug with blitting transparent
textures so it will not appear correct for the submerged part.
It does the same thing as PLACE_IMAGE except the created item may
use the same submerge code as units. If not placed on water there
will be no submersion effect. If placed on water it will be submerged
to the same level a unit would be submerged to. In general physical
items placed into water should use this, whereas items placed on top
of water should use PLACE_IMAGE.
The new macro has been applied to the merfolk cages in the Bay of Pearls
scenario in HttT.
