MArcomage

Free multiplayer on-line fantasy card game

Please log in

Fithz Hood on 10:19, 30. Oct, 2008
could you add a "no rarity filter" option in the first filter of the deck building page. I want to see all the cards togheter, not divided in common, uncommon and rare. thanks.
Mojko on 17:20, 30. Oct, 2008
That's a problem. Our take-and-return card system in the deck section, kind of need to know what card class you are currently transferring. That's why the class filter is always active.

To change it would mean to do some untrivial changes. It this really so impornant to see all cards in one huge list?
Progressor on 21:34, 31. Oct, 2008
I don't think this is required for the filter. Perhaps add something like "All current cards" @ Webpage (funny, Firefox points out that we have Web page misspelled (missing space)), like there is a section 'Modified cards' right now. Problem might be compared to ex. 'Modified cards' you don't want to add just the changes, but keep it up to date constantly.
In favour of this is that you can overview more cards at once then is possible @ Decks.
Mojko on 23:07, 31. Oct, 2008
I had a section designed called "Card gallery", but was never implemented. It was meant not to construct a deck, but to browse through the cards and just see them, compare them get to know them and print them if needed (this feature was mentioned in the "Next major goal" thread).

Is it necessary to do this, when we have similiar functionality in the deck section?
Progressor on 11:34, 1. Nov, 2008
Necessary: no
Fun: yes, well maybe
I would probably take a look at it from time to time to get new deck idea's. But really use... You can overview more cards at once, and that's the only reason it would have some use.
Fithz Hood on 09:50, 3. Nov, 2008
My request wasn't that simple after all. By the way I think it can be useful for building "keyword based" decks. for exemples if i want to put in the deck all the "undead" cards, with the "no rarity filter" it will be 3 times faster then with the currently filter. but it's just a minor thing so if it is not implementable it's not a big problem.
dindon on 16:44, 20. Sep, 2010
I like the fact that in the Cards section, one of the filters is 'any'. Why can't we have that in the deck section as well? When I'm making, say, a soldier deck, it would save me from having to separately search for common soldiers, then uncommon soldiers, then rare soldiers.
Lord Ornlu on 01:50, 21. Sep, 2010
Maybe implement this option on rarity filter but only allow it to be enabled when there is another filter in use (i.e. Show all rarity Holy cards, or show all-rarity wall-building cards). However a second filter will be enabled in such cases, which will tell the system which rarity you are filling up in your deck. i.e. Fitz has all Holy cards independent of rarity, but he will be allowed by the system to only fill up his common cards, and then he will have to change the filter manually in order to be allowed to fill up his uncommon cards.

Another idea would be to implement a second line of cards, where the same idea of rarity selection filter will exist, but the player won't be able to select cards from it. Rather the player will be able to see all Holy cards for example, independent of rarity, but will have to use the first line of cards in order to find and pull the cards he wants into his deck. basically what I suggest here is to fuse the Cards section into the Deck building section

I think that would satisfy Fitz's wish and would keep the
Mojko on 08:40, 24. Sep, 2010
I've been doing some research on this matter and here are some interesting results:

The card rarity filter actually isn't important. If you tell the system to add a card into your deck he takes the card rarity information from the card itself, not the card rarity filter. So if we add the option to show any card rarity the system would be able to handle it just fine.

Unfortunately, there is a different problem. When you allow to select any rarity option the system will have to load all of the cards. Unlike Cards section, the card list is not segmented into pages. With so many cards the horizontal scrollbar malfunctions and AJAX functionality (dynamic manipulation of cards in deck) will work only for the first N cards in the list, where God knows what N is (probably an AJAX constant though).

Actually, I already noticed the AJAX malfunctions occurring when you select enough cards (for example all uncommon cards). So we already have this problem (in a smaller variant), regardless of the "any rarity" option in deck filter. What we need is the card list segmentation into pages - something similar to the cards section. After the segmentation is done the "any rarity" option can be added right away.

The question is: How to do it. There are two basic ideas:

1 - without horizontal scrollbar

This will segment the card list into pages where one page contains so many cards as can fit in the deck width (about 10).

2 - with horizontal scrollbar

This will segment the card list into pages where one page contains so many cards as they can be without causing the malfunctions. So this is probably the mysterious N what I talked about. I think the value can range from 150 to 200.

I think 1 is the better option to choose. Note that any of these two options will cause the loss of the one solid horizontal scrollbar which allowed you to seek a portion of the card list you wanted. You'll need to use the filters more often to get to desired cards.

With growing number of cards this change will be necessary sooner or later.
dimitris on 08:52, 24. Sep, 2010
Mojko wrote:

one page contains so many cards as can fit in the deck width (about 10).


Basically, this is relative to browser window width :)
Concerning pagination somthing like this might help.
Mojko on 12:20, 24. Sep, 2010
We could also try a totally different approach - let the card pool expand to entire screen. We would have expand/collapse card pool buttons.
Fishguy2 on 14:46, 24. Sep, 2010
Mojko wrote:
We could also try a totally different approach - let the card pool expand to entire screen. We would have expand/collapse card pool buttons.


If I'm understanding you correctly, this seems to be the best option to me so far.
DPsycho on 14:48, 24. Sep, 2010
If it means showing them tiled rather than in a single line, I too approve.
Mojko on 15:24, 24. Sep, 2010
Yes, because it seems that the source of the problem is the incredible long card list. If this would be displayed in a normal table, there would be no problem. So instead of cards listed in one single line, you would have the option to show/hide entire card pool table.
Mojko on 16:21, 25. Sep, 2010
We prepared a testing prototype of the new deck editor. Please try it out and share your thoughts ;-)
Fithz Hood on 17:33, 25. Sep, 2010
The first impact it's quite impressive, I mean, there are so many cards!
Building a deck it's more easy than before using the filters because you can see all the cards you were searching at the same time. I like it more than the single line we have now.

What about adding a "sort" menu? so that you can see all the cards sorted by keyword, cost type or other. I mean, something more practical than alphabetic order.
Mojko on 08:06, 26. Sep, 2010
Please describe "cards sorted by keyword, cost type..." in more detail. Since card can have multiple keywords and many different cost types I'm not sure how to sort such cards.
Fithz Hood on 08:31, 26. Sep, 2010
Yeah, right, the sort by keyword it's impossible becasue cards have more than one keyword sometimes.
But still it's possible to sort by cost type: first cards will be bricks only cards, then gems only, recruits only, mixed cost and zero cost. another possible sort is by date of creation, or even a order that follows statistics.
By the way as it is now it's fine, using filters is already a good way to build quickly a deck.
DPsycho on 16:07, 26. Sep, 2010
Just don't change the default to anything other than alphabetical.
dimitris on 16:14, 26. Sep, 2010
It's good but I'd prefer the card pool to be initially empty or hidden.

EDIT: Also, I think the width of the card pool needs some reworking because a) in high resolutions like 1920X1080 there's much needless space left & right and, most importantly, b) in low resolutions like 1024X768 a horizontal scrollbar appears in the browser window.