This uses the new object API concept to provide a layer of indirection between
an object and others which might call() to methods on it. Example usage:
local playmatApi = require("playermat/PlaymatApi")
playmatApi.setLimitSnapsByType(tag, "All")
This uses the new object API concept to provide a layer of indirection between
an object and others which might call() to methods on it. Example usage:
local playmatApi = require("playermat/PlaymatApi")
playmatApi.setLimitSnapsByType(tag, "All")
- Saved old cards have a different structure for uses (single vs. array) making the change breaking. Code was assuming an array, breaking any loaded objects with the old structure
- Uses spawn loop was setting the values only, resulting in only the last item being spawned
- Upkeep checks were embedded incorrectly, leading to logic errors in certain circumstances
- If uses had multiple entries, tokens were spawning on top of each other and exploding, probably due to the yPos shift in playmats. Added an offset to spawn the groups in different places to avoid this, which is prettier anyway
I was trying to use a scoped require, which the tooling didn't like and
TTS doesn't respect anyway. Removed the extra structure and changed the
require() to a simple one.
The current way of tracking bonded cards to spawn them in the right zone
didn't play well with the default zone method being in Zones. Since
it's really a deck loader-only functionality anyway, moved it to the
loader.
