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
Some of the more glaring issues with the deck builder interface:
The popup box where you select your game type is a really rough implementation. Ideally this would be selectable within the interface, and if the user changes game type, it would clear the current deck contents. (Prompt user to save first)
Labeling the different subdeck areas (missions pile, seed deck, draw deck)
Properly hide controls when they're not relevant (for example, the 1E interface probably doesn't need to sort or filter by Tribble power / Tribble value)
Prevent user from putting a card in a subdeck where it wouldn't be allowed (for example, putting a personnel in the missions pile)
Remove the "my cards" / "trophies" dropdown box (this ties into player-specific card collections; this likely won't be included in the initial release)
Remove the LotR wiki link
Make top left icons larger and label them better
Review Import Deck feature to see if it works
Some "would be nice" / long-term items:
Right-click on card objects to pull up a menu of ways you can interact with it (add to deck, remove from deck, change art, move to different subdeck, etc.)
More subdecks (will need to coordinate with back-end updates)
Warnings when cards are put in subdecks where they're legally allowed, but typically wouldn't go (for example, putting a dilemma in your draw deck)
Interface for zooming/scrolling through the card collection that is closer to what you'd see in most websites / apps
Drag cards between subdecks
Overall UI overhaul
The text was updated successfully, but these errors were encountered:
Top left icons need to be larger and better labeled
Remove Import Deck since it probably doesn't work?
Longer-term:
I have a bunch of scribbled UI designs for Deck Builder that I will run past my UX person and then turn into mockups; we can plan to have a discussion about those mockups once I get that complete. Ideas welcome, of course.
Import Deck should work in theory, but with the limited card pool users won't get a lot of use out of it. I coded and tested something when I was starting that would accept a deck list with the same syntax as the Trekcc website export.
Some of the more glaring issues with the deck builder interface:
Some "would be nice" / long-term items:
The text was updated successfully, but these errors were encountered: