Snarvid wrote:Thanks Micbran!
I don't know what to make of "fake and mp"
The construction is a variant on the C-like ternary operator, and the actual statement is:
This works because of Lua's weird definitions of the binary operators 'and' & 'or'.
'And' has higher precedence, so resolves first. It doesn't resolve to a boolean in Lua, instead, it resolves to the second argument if the first argument is non-nil-non-false, otherwise it resolves to the first argument.
'Or' also doesn't resolve to a boolean, instead, it resolves to first argument if the first argument is non-nil-non-false, otherwise it resolves to the second argument.
Since we're passing
mp as a parameter, it's probably not nil or false, so this resolves as:
Did we pass
fake as true? If so, the first argument to the 'or' operator resolves down to
mp. Since
mp is never meant to be false, the 'or' operator will resolve to
mp without calling self:mindCrit(
mp). So, if this is a fake call to the function, just return the normal 'expectation' stat for the summon without any code overhead.
If we pass
fake as false, the first statement resolves to false, and "false or self:mindCrit(mp)" resolves to the second argument, calling self:mindCrit(
mp). So if this is a real call to the function, meaning we're actually summoning something, then we roll for mindcrit and resolve out the critical multiplier accordingly.
A summoner with 280% critical multiplier is going to get a pretty terrifying fire drake...