URL:
<http://gna.org/bugs/?23629>
Summary: Non-mainline [side] color= not handled correctly
Project: Battle for Wesnoth
Submitted by: shadowmaster
Submitted on: Mon 01 Jun 2015 08:04:32 PM CLT
Category: Bug
Severity: 5 - Blocker
Priority: 5 - Normal
Item Group: WML
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 1.13.0, 1.13.0+dev
Operating System: *
_______________________________________________________
Details:
On 1.13.0 and 1.13.0+dev (not 1.12.x), if a [side] color= attribute specifies
any color range other than the 9 default color ranges (red, blue, green, etc.,
and their numeric equivalents), it will be processed as if color=0 was passed
instead, possibly due to some intermediate step converting the color attribute
to a number. Since no color range with the name '0' exists, this results in a
default-constructed color range (RGB #000 for all four values) being used for
team color and ellipses.
Steps to reproduce:
* Add color=orb_lightred to the first [side] declaration in HttT scenario 1.
* Start the campaign, get to the objectives screen.
* Use :inspect and click on "team 1" under the Type list.
* Notice the color=0 attribute in the Contents panel.
This is suspected to be caused by the SP/MP unification patches.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?23629>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
