Collectible Card Game Headquarters

I've got an important hint: there is some conflict with Mok's patch for Deckbuilder. I've switched back the files from the MtG patch that you have provided and the ID changer did fix all decks. Using Mok's patch causes some cards to be messed up.

EDIT - It looks like Mok's database has something different, like one slot more or less. In fact, after succesfully converting all decks with previous version, I tried to re-add Mok's files for the new deckbuilder and all of my decks were screwed up again, without using the ID Changer.

You should use the last ID-Changer, the one a1z2s3x4 and Sarlack used.
The ones before had a problem with reading the manalink.csv (i did this with Microsoft.jet.odbc driver) and actually gave the wrong id-number when your new card-id > +-6700 (started from Akka Lavarunner)
Now i read the lines myself and all seems okay.

Dave, just to be sure, from which position should I get it? Have you uploaded it in your message posted in 07 Jan 2012, 23:11 ?
So, I'm supposed to run it with Moks' files.

Yes, that is the official one. You can see i edited for the last time at 00.23h.
As long as your manalink.csv is separated by semicolon, it doesn't matter which version you use.
I only read the first 2 columns separated by ;

Dunno about the special chars, they will still appear as not found i guess, but that's ok. All lines where i can't find a new id are written with their old id

Nope: I've re-installed Mok's Deckbuilder patch and your latest ID changer and I still get the usual bug. Please, may re-add right here the latest ID changer, just to prevent mistakes?

We need to be careful because there are currently 2 versions running:

- The one from the Patch thread which end with Mok xls_csv file

- The one from Deckbuilder which is at v2 with new deckbuilder but without latest Gargaroz fix

As Mok said :

ncluded Magic.exe/*.dat/*.dll are from latest xls update from Sonic but without the latest code from Gargaroz. Still it might work a bit better as I compiled the dll against the corrected order of card ids.

Post DB bugs here and I'll try to fix them if possible. Don't post card bugs from this version anywhere,

So to play "properly" the latest versions you need the patch one, if you want to debug the new Deckbuilder use the Deckbuilder one.

What a mess! Maybe it is better to wait next patch and to create only one single beta version with all updates.

0rion79 wrote:Nope: I've re-installed Mok's Deckbuilder patch and your latest ID changer and I still get the usual bug.

Which bug is that ?

I update the decks with the ID changer and part of the cards that I get are wrong. Here is a sample with the same deck with and without Mok's patch.

i checked those 2 decks, but they have different names for the same id's.
pe.: .10149 is Piranha Marsh in deck1 and .10149 is Pitfall Trap in deck2

When you run ID-changer and press only rebuild, it doesn't change any names. It only changes the id.

Dave, I know that those decks have different names! The one with Piranha Marsh is the one without Mok's files. The one with Pitfall Trap is what I get if I install them, even after running your ID changer. I've just saved it to show you a sample about which cards are changed and which are not.

After the ID-changer has run, do those strange id's match with those of manalink.csv?
If not -> i have to check ID-changer.
If yes -> i think the manalink.csv doesn't match with your .dat files

No, they don't match. I have checked a random wrong card that should not be in the deck, as Ember Hauler (11535): it is right after Elixir of Immortality (11534) that in fact should be in the deck.
Wonder why this is not happening without Mok's patch!

I'm getting confused here.
When you run id-changer now with deck1 and you open manalink and save the deck again, you get deck2 with Mok's deckbuilder-patch?
When you run id-changer now with deck1 and you open manalink and save the deck again and you don't use his patch, everything is fine?

if deck2 is the one with wrong cards, yes.
I also get wrong cards just by installing Mok's patch. At one point, there must be some card difference in the cards database by one slot.