Support ['specials'] in abilities except plagues, heal_on_hit and swarm, which emulate the weapon specials with [affect_adjacent] in option and the possibility to affect all weapons filtered (used with 'Initiative' in HttH or 'Formation' in UtBS). (Don't put filter_weapon in 'filter_self/opponent' like in true weapons specials.)
Closes#3630Closes#3620
The error message was, upon opening the page:
```
Parse error when parsing help text: 'Error when parsing help markup as WML: 'Unexpected characters after variable name (expected , or =)
at <unknown>:2''
```
The <bold> tag in question can be seen on old_master_20181015 here:
71a6daf961/data/core/help.cfg (L199)
this controls whether during the next turn start the game will
heal units. I feel like 'game_config' is not a that good place
name for this but it is afaik the only place for those variables.
On the third and subsequent playthroughs of Endless Night, Mal Keshar
has learned from the ending of SotA, and can leave the book to be
taken by the foolish hero's army. This text doesn't handle the unit
that picks up the book being the hero themselves, but the hero seems
to be using the normal boss AI of staying near the castle so that
probably won't happen anyway.
He learns how to lichify level 3 necromancers at the start of the
first playthrough, which fits better with the backstory of the book.
The png icon for this is copied from SotA.
This would close issues #3165 and #3167.
[ci skip]
it now keeps a unit_ptr to the unit to make sure the unit is not deleted
during whatever lua code the battle_context constructor calls. This can
be done because since the unit ctor refactor all unit objects are owned
by a unit_ptr (created by unit::create).
It might also be possible to refactor out the "unit * c_ptr" member of
lua_unit.
the old code didn't work well for mp campaigns that dynamicially set the
next scenario in endlevel. The new code just shows all scenarios that
belong to the same addon, since this is a debug command it better to sho
a little too much than not to show all scenarios of the campaign.
these come closer to their actual meaning and also are not lua keywords
which might come in hand later, in particular we can now replace the
f_and, f_or,f_terrain, with f.all, f.any, f.terrain if we want.
