Loading...
  OR  Zero-K Name:    Password:   

Post edit history

sigh silly team colour

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
4/30/2012 6:19:13 PMUSrankCrazyEddie before revert after revert
4/30/2012 6:22:14 AMUSrankCrazyEddie before revert after revert
4/29/2012 8:26:56 PMUSrankCrazyEddie before revert after revert
Before After
1 mojjj: The people in the thread you posted weren't asking for simplified team colors, they were asking for global team colors - i.e. everyone sees the same color assignments instead of everyone seeing themselves as teal, allies as cool, and enemies as warm. 1 mojjj: The people in the thread you posted weren't asking for simplified team colors, they were asking for global team colors - i.e. everyone sees the same color assignments instead of everyone seeing themselves as teal, allies as cool, and enemies as warm.
2 \n 2 \n
3 Antelope: I don't think anyone - new or not - was asking for simplified team colors. So what we now have is a setting that nobody wants, on by default, which doesn't remember that you turned it off. 3 Antelope: I don't think anyone - new or not - was asking for simplified team colors. So what we now have is a setting that nobody wants, on by default, which doesn't remember that you turned it off.
4 \n 4 \n
5 Licho: Wouldn't it have been easier to include that feature when simplified colors was first implemented? Wouldn't it be easier for whoever wrote simplified colors to add that feature than for some arbitrary "someone" to dig into the code? Shouldn't "remember settings" be a basic feature included in any settable UI element before it gets released? 5 Licho: Wouldn't it have been easier to include that feature when simplified colors was first implemented? Wouldn't it be easier for whoever wrote simplified colors to add that feature than for some arbitrary "someone" to dig into the code? Shouldn't "remember settings" be a basic feature included in any settable UI element before it gets released?
6 \n 6 \n
7 (obtw: this doesn't affect me, because I don't use the Chili minimap, because it doesn't work with my graphics card.) 7 (obtw: this doesn't affect me, because I don't use the Chili minimap, because it doesn't work with my graphics card.)
8 \n 8 \n
9 Edit: Okay, "nobody wants" is an overstatement. Licho wants it. 9 Edit: Okay, "nobody wants" is an overstatement. Licho wants it.
10 \n 10 \n
11 Edit: Huh, I suppose I should try enabling the Chili minimap again, maybe it's fixed now. http://code.google.com/p/zero-k/source/detail?r=6245 11 Edit: Huh, I suppose I should try enabling the Chili minimap again, maybe it's fixed now. http://code.google.com/p/zero-k/source/detail?r=6245
12 \n
13 Edit: ZKL didn't automatically disable minimap projectile rendering, so I guess it didn't detect my ATI graphics card (HP Pavilion G6 laptop w/ AMD M880G with ATI Mobility Radeon HD 4250). Or maybe the revision I pointed to above hasn't been released yet? Anyway, manually deselecting the "Minimap projectiles" checkbox under the ZKL Settings tab did fix the display issues that had forced me to disable the Chili minimap. .... HOWEVER, I'm still not going to use the Chili minimap, because it doesn't seem to offer any substantial improvement over the other minimap, and the other minimap lets me see projectiles without hosing up my display.
14 \n