In Consideration Text file Commander decks import in backwards zones

Firedrake

MTGO Regular
This is how it's always worked for me; Commander has to be at the bottom with a blank line above it. I always surmised that was how the client recognized it was a Commander deck.
 

Neo001992

Community Team
This is how it's always worked for me; Commander has to be at the bottom with a blank line above it. I always surmised that was how the client recognized it was a Commander deck.
Correct, which is why I originally made this report since the client is exporting commander deck txt files in a way that they will not load back into the client, that just created said file, in a way that the client would even select the right format automatically.
 

Firedrake

MTGO Regular
Sorry, I missed the part in the OP that the client was exporting this way. I just exported a Commander deck to TXT, and it put the Commander at the bottom as expected. Re-imported it, and it imported fine as a Commander deck. Not sure where the difference lies, but since it's not affecting me, I'll bow out of this conversation. Again, sorry I misinterpreted.
 

Neo001992

Community Team
This is currently intended behavior, but upvotes might change our mind here.
I would like to try to persuade you that this is not expected behavior. I went and exported 92 of my commander decks as txt files, and of those 92 decks all but 8 of them export in the expected manner. The only obvious relation the 8 commanders in question seem to have is that they're all somewhat recent precon leads, but when 8/92 decks export incorrectly that would hopefully point towards it being a bug in the export function somewhere.
 
Top