Descriptive Problem Summary:
atom.color and atom.alpha values set at compile-time are ignored when the world boots up.
if atom.color and alpha are not intended to be set at compile-time, it should produce a warning/error.
Otherwise, the atom's appearance at boot should take into account these values.
Numbered Steps to Reproduce Problem:
1. set turf/icon to icon containing a white square
2. set turf/color to "blue" or "#00F"
3. compile
4. run
5. it's still white
Code Snippet (if applicable) to Reproduce Problem:
Expected Results:
takes into account atom.color, or atom.alpha
OR
produces error/warning at compile-time
Actual Results:
values are ignored
Workarounds:
set values at runtime (atom/New or such)
ID:1377645
 Sep 15 2013, 11:55 am
|
|||||||||||||
Resolved
| |||||||||||||
|
Sep 16 2013, 9:46 am
|
|
Lummox JR
   |
Lummox JR changed status to 'Unverified'
|
I set a turf to red on the map and was able to see it just fine. I set an obj's alpha to 192 and that showed up properly as well. One of my obj types has alpha=128 in its type path definition, and those have shown up fine right along.
| |
If you'd like to try it:
http://puu.sh/4t7P3.zip (ignore the include.txt in there, a leftover from my test environment) Setting a mob's color works fine, apparently. Setting a turf's color doesn't. | |
I can reproduce this issue. mob's color works, turf's color doesn't work.
| |
Lummox JR resolved issue with message:
Setting alpha or color for a turf type, not for an individual turf in the map editor, had no effect when the map was loaded. | |