Results 1 to 2 of 2

Thread: Thoughts on a new way to define custom decks.

  1. #1

    Thoughts on a new way to define custom decks.

    Edited to fix some spacing issues in the xml & file list*
    I've been playing around with TableTop Simulator's custom decks lately and found its a pretty large pain to really customize the decks. Currently its all done with a simple atlas that TTS cuts up and lays the images on the cards. There is an app from another user that helps making build these atlases a lot easier, but I think a more robust way to define our decks would be very nice(if not essential). 12v Air Compressor

    Just to brainstorm a little, what about letting Unity handle building the atlas out of individual images and an XML file to define the deck?
    An example(in no way complete):

    An Example Deck:
    File List:
    /my deck/
    /my deck/deck.xml
    /my deck/Images/
    /my deck/Images/back_image.png
    /my deck/Images/card_image1.png
    /my deck/Images/card_image2.png

    Deck XML:
    <Deck Id="My example deck" Height="100" Width="100" Shape="Hexagon" Interlocking="True">
    <Image Id="BackImage" Location="./Images/back_image.png" />
    <Image Id="AttackImage" Location="./Images/card_image1.png" />
    <Image Id="DefendImage" Location="./Images/card_image2.png" />
    <Card Id="Attack!" FrontImage="AttackImage" BackImage="BackImage">
    <OnFlip Action="(card)=>"/>
    <Card Id="Defend!" FrontImage="DefendImage" BackImage="BackImage"/>
    <OnCreate Action="(deck)=> deck.shuffle()"/>
    <OnEmpty Action="(deck) =>"/>

    I think something along these lines would make it much easier for tools to create the decks AND
    for the engine to have a way to create specific decks without all the waste. The benefits of having all this extra information in XML means the developer can extend the format as they go along to expose an API for rules or just extra data the engine might use. It would also make creating tools for creating decks more capable as well. Also there is no atlas creation being done by the user, so we just scan a list of cards in and just build a simple xml file. Maybe even just zip the whole thing and rename it with .TTSD or something so it can all be easily downloaded and organized.

    Last edited by isoman; 07-14-2019 at 09:33 AM.

  2. #2
    I tried using the UI to draw data on my cards on the fly. It works, with some limitations. The UI data doesn't display in some circumstances, for example the top card of a face up deck fails. (not a problem for my mod)
    The UI inputs block access to the game UI elements. I have UI buttons on a game board, and the mod save/load interface is blocked wherever a UI input is behind it. I hope this will be corrected!

    So, a standard card with custom display.

Similar Threads

  1. New thoughts on Snaps: Pegs and Sockets
    By FoaS in forum Suggestions
    Replies: 11
    Last Post: 08-10-2018, 10:41 AM
  2. [DISCUSSION] Thoughts from me and my nephew
    By TheRaven81 in forum Scuttle!
    Replies: 0
    Last Post: 03-25-2017, 08:10 PM
  3. Some thoughts after 2 months of playing...
    By BrashFink in forum General Discussion
    Replies: 1
    Last Post: 03-11-2015, 01:33 PM
  4. Replies: 0
    Last Post: 06-20-2014, 10:20 AM
  5. Thoughts on a new way to define custom decks.
    By Nut in forum General Discussion
    Replies: 1
    Last Post: 05-03-2014, 10:05 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts