This impacts wesnoth.transform_unit, [effect]apply_to=type, and
[effect]apply_to=variation. If desired, the poisoned state can still
be explicitly set for immune units; this change only affects default
behavior, making it correspond better to the core rules.
This is actually simpler to implement and is more consistent with the
[transform_unit] tag. Plus, the wiki documentation for
wesnoth.transform_unit() does not state that the hit points definitely
will be changed (it's a bit vague on that point), so this is
consistent with the existing documentation.
They are trivial wrappers for the wesnoth.lock_view() function in Lua.
Neither takes any parameters.
There is no wrapper for wesnoth.view_locked() yet until I decide on its
name and usefulness factor.
...to the [scroll_to] and [scroll_to_unit] WML actions
When immediate is set to a true value, the display code will instantly
warp to the chosen location regardless of the scroll speed setting in
Preferences.
No deprecation needed since it defaulted to the 'default
objectives' already. They are used for a side in case that that side
doesn't have side specific objctives set. Use a SSF which matches
no sides or all sides to set the default objectives, if a subset
of all sides match, the side specific objectives for these are set.
2010-07-18T15:21:41Z!guillaume.melquiond@gmail.com
The hack causes problems now, since I want to load helper.lua previously
already and the comment says that it should be removed in 1.11.
I *think* the reason for the hack was to avoid loading wml-tags.lua twice
in case that a replay and/or (perhaps) savegame is loaded which was
created with a BfW version previously to 2010-07-18T15:21:41Z!guillaume.melquiond@gmail.com,
since those replays/saves seemed to have recorded the commands for
loading the core lua files, which is no longer the case since back
then. Those replays/saves are no longer relevant, so everything hints
that I can safely remove this.
Searched all *.lua and *.cfg (embedded lua) files in data/ for occurences
of the deprecated stuff mentioned in
http://www.lua.org/manual/5.2/manual.html#8.2
The currently compiled-in define LUA_COMPAT_ALL appears to work
like so that both the old and the new syntax work at the same time
(without errors or warnings), while the old one will be an error after
removing it.
If the tag is used to modify the type= of several units at once,
it looks better to not kill the old units until the modified one
gets unstored, so that units don't disappear for the time of processing.
reported in the forum: http://forums.wesnoth.org/viewtopic.php?p=519174
