Search options (Page 16 of 116)

Yeah, deck pages were not designed to support thousands of entries. All changes to any card re-render the whole listing (for totals and statistics and stuff), even though that would not be necessary (or should be cleaned up and optimized). But the idea was that a deck is something small(ish), and not made to be paginated, like big collections.

I think when we finally have tags for inventories a large number of usecases that people use decks for will move to use that instead. (except gigantic cubes)

Yep, true. It's a bug actually, the "normal" edition / collector number ordering was supposed to be used there. Fixed now!

You mean the ordering of the printings in the "details" dropdown in the deckbuilder, right?

I did deploy a large update of backend upgrades yesterday, might be the problem. Can you send me a screenshot to support@deckbox.org please?

Just another issue I have with the user-settable etched flag: pricing will need significant work for that to work. Right now the normal foil is the only "special case" there, and adding a second "special case" is going to be a non-trivial amount of work.

I'm still leaning towards having them as separate printings (as they are in real life) somehow. Perhaps a separate edition that has a distinct edition icon is still the cleanest way to go, despite the explosion in editions...

It's clear by now that wizards is not stopping the explosion of special "editions" they produce, quite the contrary. So I do need to find nicer UIs for a "we now have a huge amount of editions" problem anyway, along with updates to the edition icon handling that is now cumbersome and old (cumbersome to add special icons for editions i mean, as evidenced by the "ribbon" everywhere and extras having same icon as main set etc).

So if I have to do it anyway, perhaps adding a separate edition for etched is not that big of a deal....

Not sure, I did not yet deploy the changes on live.

I'll make a post in announcements when I'm sure about the deploy.

Still here, just not vocal .

Working on some infrastructure updates, bringing the backend framework updated to current-day versions. Db updates and other info was waiting for this stuff, which as usual way exceeded the initial estimation .

Regarding the flags meldon44, I'm currently leaning in favor of what scryfall is doing, making the collector numbers strings instead of integers and adding those printings in parallel. I think that might be the cleanest way...

Sorry about that guys, a memory leak and crash on the db then the appserver did not properly reconnect after restart. All good now.