#```lua

1 messages · Page 1 of 1 (latest)

cunning current
#

But also, that's (probably) an indicator that baseDiscardPile is nil at that point?

#

So you should make sure that cardTable[1] is non-nil, just in case

#

For example, I believe it can still be nil if castFindings is empty

#

But I'm not sure how Lua handles unassigned indices on tables so maybe this is wrong

#

There might also be some subtle differences between what happens with the || lambda syntactic sugar and fully writing out function() ... end

#

Might just be me being superstitious though

timber pier
#

yes, good point. in my efforts to troubleshoot this, cardTable[1] has always been non-nil. and baseDiscardPile always seems to be non-nil as well

#

my theory is that by "changing" baseDiscardPile by adding things to it, it creates the problem. but I do this exact same procedure with other cards/decks and do NOT have this problem

cunning current
#

You could always change it to baseDiscardPile != nil and not...

#

Or whatever the right syntax is for that

timber pier
#

yeah, ill try that. i feel like i did try it at one time, but won't hurt to try again