This is going to be a thing for sure. I think my initial plan will be to tackle it with classes of "rules" which are triggered by "conditions". Rules classes put into an array that is traversed for card plays makes sense to me at first blush.In a simple game like Uno, there are only a handful of possible keywords ("reverse", "skip", "wild card", etc.) which could be relatively easy to implement, but in a more complex game like Yu-Gi-Oh, there are so many potential card effects that require information about other cards or affect other elements of the game ("if you have card X in your [graveyard], [banish] it so [summon] Y", "if you have X amount of [life points] [more] than your opponent, do Y", etc.).
Code: Select all
function run(keyword, arguments)
if keyword == 'increase' then
increase(arguments[1], arguments[2], arguments[3])
elseif keyword == ... then
...
end
end
Code: Select all
function run(keyword,arguments)
if keyword == 'checkphase' then
checkphase(arguments[1], arguments[2], arguments[3], arguments[4], arguments[5])
elseif keyword == 'increase' then
...
elseif
...
end
end
function checkphase(phase, keyword, argument1, argument2, ...)
if gamePhase == phase then
run(keyword, argument1, argument2, ...)
end
end
Code: Select all
HandlerTable['increase'] = function(args)
-- put logic in here
end
function HandleKeyword(keyword,args)
local entry = HandlerTable[keyword]
if (type(entry) == "function") then entry(args) end
end
