Forge version 1.5.43 or 1.6.0
Tentative target release date: August 14 2015.
High Quality Resources for Collectible Card Games and Home of the CCGHQ Team
https://www.slightlymagic.net/forum/
https://www.slightlymagic.net/forum/viewtopic.php?f=52&t=17528
"Name a card" type cards would be slightly less trivial to implement custom sorting for, especially given most deal with your opponent's cards rather than your own and we shouldn't be revealing information about the opponent's deck via a custom sort. We'd probably have to make card specific sorting logic. Is that something we could maybe include in the card script?friarsol wrote:This sounds similar to the requested feature for Cursed Scroll to sort cards in your hand to the top of the list...
Yea I think that's the only way to do it. Sort by alphabetical by default, and if the script defines a specific sorting method use that. Not sure if it's possible to use the "Valid" property scheme to do this, or if we'd need to specifically name sorting algorithms. viz: "ValidHand Card.YouCtrl" vs "CardsInYourHand"drdev wrote: We'd probably have to make card specific sorting logic. Is that something we could maybe include in the card script?
We shouldn't use "Valid" because that restricts the list, whereas with Cursed Scroll you're technically allowed to choose a card name that's not in your hand even if there's usually no good reason to do so.friarsol wrote:Yea I think that's the only way to do it. Sort by alphabetical by default, and if the script defines a specific sorting method use that. Not sure if it's possible to use the "Valid" property scheme to do this, or if we'd need to specifically name sorting algorithms. viz: "ValidHand Card.YouCtrl" vs "CardsInYourHand"drdev wrote: We'd probably have to make card specific sorting logic. Is that something we could maybe include in the card script?
I wasn't saying filter by Valid. I was saying sort by it.drdev wrote:We shouldn't use "Valid" because that restricts the list, whereas with Cursed Scroll you're technically allowed to choose a card name that's not in your hand even if there's usually no good reason to do so.
We'd probably need to create a new script identifier for this. Are there other cards of this sort that would benefit from some custom sorting on a prompt it shows?
This isn't true. Cursed Scroll doesn't affect only your cards. Cursed Scroll allows you to choose any card name (allowing you to bluff) Typical use case is to choose a card in your hand, but there's certainly times when if you have two cards in your hand (say both random card draw) you can name "Counterspell" and then when a Divination is revealed your opponent thinks he just got lucky, but now also thinks you have a counter readied.Phoenix wrote:For cards like Cursed Scroll, that affect only YOUR cards:
Just take alle cards or card names of your deck on top of the list. You should know your own deck.
That sounds way too complicated for minimal gain. I'm not sure we really should be aiding the player in memorizing which cards he "might" know about.So maybe there should be a new flag showing if a card is known to player 1-x. Then a sorting algorithm can access the omniscient list of all cards in play and choose all cards known by the specific player.
But doesn't "Valid" normally filter the options? I feel it'd be confusing to make that property sometimes do sort and sometimes do filter. Better to introduce a new script keyword named "Sort" with the same types of inputs as "Valid".friarsol wrote:I wasn't saying filter by Valid. I was saying sort by it.drdev wrote:We shouldn't use "Valid" because that restricts the list, whereas with Cursed Scroll you're technically allowed to choose a card name that's not in your hand even if there's usually no good reason to do so.
We'd probably need to create a new script identifier for this. Are there other cards of this sort that would benefit from some custom sorting on a prompt it shows?
If X is a valid name, sort it higher in the list. If X is not a valid name, leave it in the normal alphabetical spot.
I.. think we are mostly agreeing and you aren't understanding me? It doesn't make that much difference, I was mostly saying if we can use Valid to sort all the "Priority" names higher than we should since it will allow us to reuse that code. Of course the actual name of the script key would be it's own thing, it would just hook into the hasProperty portion of the code that already exists and is well defined. Honestly, I don't even know if we can, since hasProperty is for game objects, and we might just have a list of strings.drdev wrote:But doesn't "Valid" normally filter the options? I feel it'd be confusing to make that property sometimes do sort and sometimes do filter. Better to introduce a new script keyword named "Sort" with the same types of inputs as "Valid".
Chris H. wrote:Tentative target release date: August 14 2015.
