...to test if the whiteboard is a good replacement."
by gabba, 2010-08-15T04:17:49Z!gabrielmorin@gmail.com
1. The whiteboard is obviously still way not ready to be a replacement.
2. It has been requested by several users (and by me and Gambit).
3. For real multiplayer, the whiteboard is too complicated in
comparison to delay shroud.
4. We need time and testing before 1.10 to remove possible problems
interfering with this old code which can have been introduced in the
time since it was disabled.
All forest now aliased to base,forest (and snow if appropriate)
Best defense, worst movement
mounted move_type has forest defense capped at 30%
-> maintains old behaviour for mounted units over flat terrain
-> mounted units now have 30% defense on forested hills
-> naga myrmidons now have 50% defines on flat forest
-> all other units/terrains appear unaffected
fixes bug #18216
I do not want such workarounds to be added. shadowmaster's campaign
was still functional nevertheless. If there's an annoying bug
and nobody has the time or knowledge or energy to fix it then we must
just accept that it lingers around any annoys us.
Remove duplicate storing, which was clearing the already stored
unit from the gamestate variables again. Silene forgot to delete
the line in 2010-08-06T17:31:14Z!guillaume.melquiond@gmail.com.
The unparsed vconfig from the [unit] tag is passed to the unit
constructor and filter_recall and event tags are taken from it.
[side][unit] did already no variable substitution, wesnoth.put_unit does
it only if passed a vconfig userdata to describe the unit.
The preferences entry name and tooltip are not the same as the patch in
the tracker, as we discussed on IRC that this doesn't exclusively affect
mainline units nor does it need to. I also changed the tooltip wording
to fit as much as possible in my 1280x800 screen without changing the
font size (works on 800x480 with a smaller font size).
The behavior in question was apparently put in place to avoid a
segmentation fault due to unchecked access to a vector's first element;
ensure there'll always be a first element instead.
