Talk:Combat system

The official GemStone IV encyclopedia.
Jump to: navigation, search

Didn't you want \cdots and not Xs? Spaces are also much easier to read. VANKRASN39 (talk) 13:36, 6 October 2016 (CDT)

I tried a few ways of formatting these formulas and prefer this over the alternatives, and it has to do with the multi-word variable names.

  • While Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle a \cdot b + c} is better than Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle a \times b + c} , I don't think Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle \mathrm{VeryLongVariableName} \cdot \mathrm{AnotherVariableName} + \mathrm{YetAnotherVariableName}} is necessarily more intuitive, and since the reader won't mix up Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle x} with Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle \times} if all the variables are long words it's fine to let stand.
  • Subscript scoping makes more sense in non-spaced variables. Compare: Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle \mathrm{ShieldSizeModifier}_{\mathrm{Ranged}}} vs. Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle \mathrm{Shield\ Size\ Modifier}_{\mathrm{Ranged}}} : it's more obvious in the first case that the subscript applies to the entire variable name.

ZHOUY1 (talk) 13:52, 6 October 2016 (CDT)

How about only bunching when there's a subscripted part? It's really rough to read. I also really prefer brackets instead of double parentheses [( ... )] vs (( ... )). VANKRASN39 (talk) 14:27, 6 October 2016 (CDT)
Is it better with brackets around the variables? Failed to parse (MathML with SVG or PNG fallback (recommended for modern browsers and accessibility tools): Invalid response ("Math extension cannot connect to Restbase.") from server "https://api.formulasearchengine.com/v1/":): {\displaystyle [\mathrm{Shield\ Size\ Modifier}]_{\mathrm{Ranged}}} ZHOUY1 (talk) 14:31, 6 October 2016 (CDT)
Yes, that's much better. VANKRASN39 (talk) 14:39, 6 October 2016 (CDT)
I'll make the changes and also restore the \quad spacing edits. ZHOUY1 (talk) 14:52, 6 October 2016 (CDT)
Sure :) I put the \quads in there because I was trying to figure out why there was an extra space before Base Value. I have no clue. VANKRASN39 (talk) 14:59, 6 October 2016 (CDT)