Granting Human Deck in Quests
 Posted: 22 May 2013, 12:10
Posted: 22 May 2013, 12:10Hey Max,
Thanks for some of the cleanup with the Quest Challenge stuff, one thing I noticed however is you changed intended functionality here. I used a nullable boolean for a reason for forceAnte, since if the user isn't using Ante I wanted to ability to FORCE them into or out of Ante. "OverrideAnte" may have been a slightly better name.
So if useAnte is already true (because that's what my preferences say), and the Quest says Force Ante is false, ante will still be used. In this case, that is different then the functionality I want. Because I'm granting the user a temporary deck they don't actually own there is no risk in playing for ante, so they shouldn't be able to gain cards through ante.
Conversely, we can't use an &= operator here because if useAnte is false (because that's what my preferences say) and the Quest wants you to have to Ante something for some reason (thematically), ante will not be used when it should..
I (correctly) used a nullable Boolean, so when forceAnte isn't null, it will override useAnte for the match. Otherwise, we'll fall back to the user's preference.
			Thanks for some of the cleanup with the Quest Challenge stuff, one thing I noticed however is you changed intended functionality here. I used a nullable boolean for a reason for forceAnte, since if the user isn't using Ante I wanted to ability to FORCE them into or out of Ante. "OverrideAnte" may have been a slightly better name.
- ForceAnte | Open
So if useAnte is already true (because that's what my preferences say), and the Quest says Force Ante is false, ante will still be used. In this case, that is different then the functionality I want. Because I'm granting the user a temporary deck they don't actually own there is no risk in playing for ante, so they shouldn't be able to gain cards through ante.
Conversely, we can't use an &= operator here because if useAnte is false (because that's what my preferences say) and the Quest wants you to have to Ante something for some reason (thematically), ante will not be used when it should..
I (correctly) used a nullable Boolean, so when forceAnte isn't null, it will override useAnte for the match. Otherwise, we'll fall back to the user's preference.