Fixes#6898. The issue is that non-WML events added through the new events API
always disable undo with no equivalent of WML's `[allow_undo]`. The long-term
fix is to add a way to do that; however until that's available then listeners
for `moveto` need to use the old `on_event` API. The old `on_event` API can't
be deprecated yet, and this is enforced by our unit tests (the build fails if
there are unexpected deprecation warnings during the tests).
Reverts most of 7e234f8833282424b3535b9c334c751748f7222b. Does not revert files
that only listen for non-undoable events such as `die` or `new turn`.
Reverts the deprecation part of #5663's 8cd133263058a5df85f64988e348d2cf54d13a48.
* 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
1. Added a new multiplayer survival scenario.
2. Lua (similar to Dark Forecast one) code used for the enemy waves and weather change events
3. Comes with 6 weather conditions
4. Default difficulty is set at "0"
5. Has 1p/2p modes
6. 5 final waves
7. 8 difficulty levels, ranging from -30 to +60, with +60 being catered especially for veteran/skilled players.
This should probably be changed into a table of GUI2 widgets, but this commit
is an improvement on what was here before. It removes the broken conjunct list
formatting for 3-way ties. However, it also means that there are 5 lines per
language to translate again.
Fixes#4274.
this sort of makes Dark Forecast passable for 2 player mode. Initially, it was only passable if it was one-player-mode as one player could have 11 villages active and could get a good army built prior to the final wave.
2 player suffered from lack of resources to replace losses and would be unwinnable in some cases.
Only 2 cases where it was won in 2 player mode was when the players were of exceptionally high skill level but average skill-levelled players have yet to even win.
Adjusted the weather change effect from side 3 turns to side 1 turns. Side 1 is never empty so it would bypass the side 3 as empty cheat which impeded weather changed.
- get_terrain and set_terrain replaced with direct indexing operations
- get_map_size mostly replaced with either the iterator or an on_board call.
Only a few cases really needed to know the size of the map for some other purpose.
- shroud and fog operations, village owner, time areas, and location filters
- get_terrain_info replaced with terrain_types table
- Map generation functions create_map and create_filter
https://github.com/wesnoth/wesnoth/pull/5481 removed the check that made
wmllint: display on and wmllint: display off necessary.
This PR removes now redundant wmllint comments.
find ./data/ -name '*.cfg' -exec sed -ri '/^ *# *wmllint *:? *display *(on|off) *$/d; s/ *# *wmllint *:? *display *(on|off) *$//' '{}' ';'
"../../data/multiplayer/maps/6p_Team_Survival.map", line 2: warning, fog or shroud in map file
"../../data/multiplayer/maps/Dark_Forecast_drought.map", line 2: warning, fog or shroud in map file
"../../data/multiplayer/maps/Dark_Forecast_firstsnow.map", line 2: warning, fog or shroud in map file
"../../data/multiplayer/maps/Dark_Forecast_secondsnow.map", line 2: warning, fog or shroud in map file
closes#1149
The difficulty slider is in fact the gold setting.
bob_the_mighty suggest setting it to 75, though for new players 100 might be better.
I think the best we can get from this situation is to have it by default on 100,
but to tell players about changing the gold setting if the scenario becomes too easy for them.
[ci skip]
It's having a few more glitches, but it may cause less glitches elsewhere,
as it are »real« castles, and the player can build castes adjacent
[ci skip]
