You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I will admit that I'm doing some unusual things here. I added movable: false as well as a parent and fixedParent directly into the cardDefaults. That being said, when I tested this removing what I mentioned in the previous sentence, the odd pile creation was still happening.
Example of it happening here: QuickDownload without assets 2024-09-02 1736 - Unnamed copy.zip
The text was updated successfully, but these errors were encountered:
I don't think setting a parent in cardDefaults is going to work.
Also, alignChildren, dropLimit, dropTarget, dropOffsetX, and dropOffsetY are a properties of holders, not cards.
I would also suggest using text and a border rather than images for the cards.
The issue seems to be related to those properties in cardDefaults. I'm not 100% sure what you're trying to accomplish with those settings, but if you can explain that, then I will try and help.
If I were to guess, I'd guess that what you want to do is make map_anchor a holder, put properties on that holder, and put your deck in that holder - but that is just a guess.
I don't really remember the specifics from this project, I ultimately did what I wanted somehow and completed it.
It looks like I wanted cards that are also holders to be held by a map anchor, so that the map and all these cards to move together. Then have a different set of cards that are held by the first set, these being movable by the players.
I will admit that I'm doing some unusual things here. I added movable: false as well as a parent and fixedParent directly into the cardDefaults. That being said, when I tested this removing what I mentioned in the previous sentence, the odd pile creation was still happening.
Example of it happening here: QuickDownload without assets 2024-09-02 1736 - Unnamed copy.zip
The text was updated successfully, but these errors were encountered: