With the current setup it becomes hard to see where the flag-name begins and ends, and where its description begins and ends.
Example:
Effect - Flags
Kill means that any unit targeted by this effect is instantly killed irrespective of it's current shield and life
Live prevents this effect from reducing the target unit's life below 1
No Absorb Energy (Unknown)
No Absorb Life makes the effect do no damage to life.
No Absorb Shields makes the effect peirce shields (ignores them)
Possible solution 1:
Effect - Flags
Kill means that any unit targeted by this effect is instantly killed irrespective of it's current shield and life
Live prevents this effect from reducing the target unit's life below 1
No Absorb Energy (Unknown)
No Absorb Life makes the effect do no damage to life.
No Absorb Shields makes the effect peirce shields (ignores them)
Possible solution 2:
Effect - Flags
Kill means that any unit targeted by this effect is instantly killed irrespective of it's current shield and life
Live prevents this effect from reducing the target unit's life below 1
No Absorb Energy (Unknown)
No Absorb Life makes the effect do no damage to life.
No Absorb Shields makes the effect peirce shields (ignores them)
Possible solution 3:
Effect - Flags
Kill means that any unit targeted by this effect is instantly killed irrespective of it's current shield and life
Live prevents this effect from reducing the target unit's life below 1
No Absorb Energy (Unknown)
No Absorb Life makes the effect do no damage to life.
No Absorb Shields makes the effect peirce shields (ignores them)
I think that option 3 would be the best method to handle such lists but it might take up too much space...
We might be better off with option 1 then option 3 in that case...
I'm open to suggestions including which one you think would be best to use, or other options.
1, but with a colon at the end of the bold word. Then the word is repeated in the definition. So like...
Kill: Kill means that any unit targeted by this effect is instantly killed irrespective of it's current shield and life
Live: Live prevents this effect from reducing the target unit's life below 1
and so on. I feel that individual items should not be color coded. Instead, entire sections should be color coded. For example, anything that explains a particular type of flag is in green. Everything that explains another type of flag is in red. Other fields will be defined in other colors, so that if someone is looking at a large article, and want to find something fast, they can find it with the color.
Other than that, I think that the colors would only be distracting.
not gonna do section coloring, cause that is more distracting and usually painful to the eye. But a simple color shift could be helpful in seeing the difference between some text in the explanation which happens to be bold and at the start of the line, compared to the flag terms.
like in a somewhat more grayer hue orso.... (eg #f0f0f0 instead of #ffffff)
some color tests:
grey set:
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
color set 1:
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
color set 2:
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
color set 3:
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
color set 4:
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Kill: Kill Description Second line when long description
Right, that was what I was getting at. The bold word would be colored, and indicate the category that it fits into. I don't think that using color just to show where a new definition begins is a good idea. I think, like I said, there should be some purpose to it. I have no idea what the categories would be. Personally I think that color might be overdoing it, but if you are going to use colors, this is how I would do it.
Keep all the definitions the standard white text, like you said.
Nothing too bright, but I would have them organized by importance. Have orange, because it seems to be the theme of the site, out of the flags. Then have blue, purple, green, and maybe yellow. Have important terms highlighted in red or yellow, but otherwise stick to the darker colors.
I don't think it matters what flags are set to what color, as long as it remains consistent.
Also, don't have like a dark green. If you look at the standard color for excel and word, those colors are really good. There has actually been a study about how blue and green are easier to read and process than other colors, behind black and grey of course. Can't really remember why though. And then purple is okay too, but it needs to be a deep but low alpha color. Grey is good for everything else.
With the current setup it becomes hard to see where the flag-name begins and ends, and where its description begins and ends.
Example:
Effect - Flags
Possible solution 1:
Effect - Flags
Possible solution 2:
Effect - Flags
means that any unit targeted by this effect is instantly killed irrespective of it's current shield and life
prevents this effect from reducing the target unit's life below 1
(Unknown)
makes the effect do no damage to life.
makes the effect peirce shields (ignores them)
Possible solution 3:
Effect - Flags
means that any unit targeted by this effect is instantly killed irrespective of it's current shield and life
prevents this effect from reducing the target unit's life below 1
(Unknown)
makes the effect do no damage to life.
makes the effect peirce shields (ignores them)
I think that option 3 would be the best method to handle such lists but it might take up too much space...
We might be better off with option 1 then option 3 in that case...
I'm open to suggestions including which one you think would be best to use, or other options.
-
View User Profile
-
View Posts
-
Send Message
ModeratorsI believe it is possible to colour text that might be a solution. Else go with solution 1.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
@DrSuperEvil: Go
I vote solution 1, with color.
so basicly making the flags colored and bold... what color would be good to use?
1, but with a colon at the end of the bold word. Then the word is repeated in the definition. So like...
and so on. I feel that individual items should not be color coded. Instead, entire sections should be color coded. For example, anything that explains a particular type of flag is in green. Everything that explains another type of flag is in red. Other fields will be defined in other colors, so that if someone is looking at a large article, and want to find something fast, they can find it with the color.
Other than that, I think that the colors would only be distracting.
Great to be back and part of the community again!
@TacoManStan: Go
not gonna do section coloring, cause that is more distracting and usually painful to the eye. But a simple color shift could be helpful in seeing the difference between some text in the explanation which happens to be bold and at the start of the line, compared to the flag terms.
like in a somewhat more grayer hue orso.... (eg #f0f0f0 instead of #ffffff)
some color tests:
grey set:
Second line when long description
Second line when long description
Second line when long description
Second line when long description
Second line when long description
Second line when long description
color set 1:
Second line when long description
Second line when long description
Second line when long description
Second line when long description
Second line when long description
Second line when long description
color set 2:
Second line when long description
Second line when long description
Second line when long description
Second line when long description
Second line when long description
Second line when long description
color set 3:
Second line when long description
Second line when long description
Second line when long description
Second line when long description
Second line when long description
Second line when long description
color set 4:
Second line when long description
Second line when long description
Second line when long description
Second line when long description
Second line when long description
Second line when long description
-
View User Profile
-
View Posts
-
Send Message
ModeratorsI like No. 5 From Set 1
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
@Helral: Go
Right, that was what I was getting at. The bold word would be colored, and indicate the category that it fits into. I don't think that using color just to show where a new definition begins is a good idea. I think, like I said, there should be some purpose to it. I have no idea what the categories would be. Personally I think that color might be overdoing it, but if you are going to use colors, this is how I would do it.
Keep all the definitions the standard white text, like you said.
Great to be back and part of the community again!
@TacoManStan: Go
any preference for a color to use for the flags? I've included a grey set with options. or you can suggest a color yourself.
@Helral:
Nothing too bright, but I would have them organized by importance. Have orange, because it seems to be the theme of the site, out of the flags. Then have blue, purple, green, and maybe yellow. Have important terms highlighted in red or yellow, but otherwise stick to the darker colors.
I don't think it matters what flags are set to what color, as long as it remains consistent.
Also, don't have like a dark green. If you look at the standard color for excel and word, those colors are really good. There has actually been a study about how blue and green are easier to read and process than other colors, behind black and grey of course. Can't really remember why though. And then purple is okay too, but it needs to be a deep but low alpha color. Grey is good for everything else.
Great to be back and part of the community again!
I used these Unit flags as example for the coloring.
this coloring is done with the 5th one from 1st set. I think it is a bit too bright.
Perhaps it should more be like the last of the 3rd or 4th set.
-
View User Profile
-
View Posts
-
Send Message
ModeratorsLooks ok to me but that is just an opinion.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg