The actual [powerCap] and [shieldCap] should be rename [powercap] and [shieldcap]
This capital C is absolutely senseless and prevent fluid memorization of the tags since [power] and [shield] tags don't have any caps.
I didn't merge with T1307 - Content/typos part 2 because these typos aren't only concerning "Display Help" menu but impact the ingame interaction and can lead to that situation:
we discussed this a bit further
it should be decided by development
probably best for it to be not case sensitive at all.
so making PowerCap - POWERcap - powerCap basically the same and not breaking any already existing versions while at the same time give the user the choice on how to remember those tags best.
(especialy when there will be more of them in the future)
<replace this line with the file content>
<replace this line with the file content>
-rejected-
Maybe it doesn't make sense to you, but it does to me. I think in this case it's just personal preference that matters.
We may change it to lower case if we expand the display variables.
Ok but in this case why the generic [power] and [shield] instead of [Power] and [Shield] ?
Display variables should have only one way to be invoked. Crossbreed situation like this bring just confusion and doesn't facilitate memorization.
all caps = [Power], [Shield], [PowerCap], [ShieldCap] = 1 logic rule to apply = easy memorization (+ bonus easy to read & indentify concept)
no caps = [power], [shield], [powercap], [shieldcap] = 1 logic rule to apply = easy memorization (but less easy to read; i.e. powerregen if one day it show up)
crossbreed situation [power], [shield], [powerCap], [shieldCap] = no logic rule to apply, just a fact to memorize = with memorization not based on any rational rules it will inevitably be more difficult and less spontaneous to invoke variables properly "de tête".
-Confirmed-
we discussed this a bit further
it should be decided by development
probably best for it to be not case sensitiv at all.
so making PowerCap - POWERcap - powerCap basically the same and not breaking any already existing versions while at the same time give the user the choice on how to remember those tags best.
(especialy when there will be more of them in the future)
Glad to see that my remark wasn't meaningless. :) Your advocated solution sounds good since it should please all sides and preserve reliabitiy between old-new system.
With just 4 variables it's not really a big deal right now nor a developping priority anyway, it was rather in anticipation of possible new variables. A coherent name system is always better than a chaotic one.
A bit late to the party, but this isn't a chaotic naming system. It's using lower camel-casing.
First word has lower case letter, any subsequent first letters of other words are capitalized.
likeThisWouldBeLowerCamelCasing
I suppose not caring about caps at all makes more sense then, shouldn't result in any inconsistencies considering you need to put it between [ ] anyway.