[Wesnoth-bugs] [bug #23749] Illuminates not working as advertised

URL: Summary: Illuminates not working as advertised Project: Battle for Wesnoth Submitted by: bob_the_mighty Submitted on: Tue 04 Aug 2015 03:10:54 UTC Category: Bug Severity: 3

[Wesnoth-bugs] [bug #23739] [event] in [side] doesn't work

Follow-up Comment #5, bug #23739 (project wesnoth): Currently (1.13.1) [event] inside [side] mostlikeley won't work because of this bug. And fixing this bug actually isn't that wasy. ___ Reply to this item at:

[Wesnoth-bugs] [bug #23739] [event] in [side] doesn't work

Follow-up Comment #4, bug #23739 (project wesnoth): It is barely related, but I would like to ask again for documentation about [event]. If I want to know if something like... [event] name=preload [/event] ...would work inside [side], I would have not clue about it by just reading wiki. I w

[Wesnoth-bugs] [bug #3657] Add index of map labels

Follow-up Comment #5, bug #3657 (project wesnoth): I think that https://gna.org/bugs/?13678 makes this unnecessary. Labels already show the team color, and that color cannot be overriden, so you can know who placed a given label from the color of that label. Fixing this for colorblind people may

[Wesnoth-bugs] [bug #23670] Language settings not persistent after exit BfW

Follow-up Comment #5, bug #23670 (project wesnoth): I cannot reproduce in Windows either. ___ Reply to this item at: ___ Message sent via/by Gna! http://gna.or

[Wesnoth-bugs] [bug #23739] [event] in [side] doesn't work

Follow-up Comment #3, bug #23739 (project wesnoth): This is likeley to be related to iceiceces refactor of game events: in 1.13 the game events are initialized after the starting unit are put on the map, so [event]s inside those starting units are ignored.

[Wesnoth-bugs] [bug #23739] [event] in [side] doesn't work

Follow-up Comment #2, bug #23739 (project wesnoth): I think it's because Konrad is stored and unstored in the 3rd scenario of HttT. Maybe the order of copying the [side][event] into leader's [unit] and of copying the [unit][event] into [scenario] has changed in 1.13, which led to this bug. _