Re: Manalink BETA update : 2000 limit NO MORE !
Posted: 13 Jan 2012, 19:57
Well, I did That's why I'm reporting!
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=85&t=6031
I thought the missing 100/100 P/T were an error on my part. As the ERRORS file had been reporting a mismatch in the P/T values of Clone and Vesuvan Doppelganger, and a few other cards which originally had 100/100 entries.Mok wrote:I'll edit Sonic's manalink.xls and correct the aura subtypes so they are recognized properly (and revert the 0/0 creatures back) and restore ct_all to the version from Gargaroz (with copied names column) so some undesired changes are reverted (like Ghostfire color etc).
The asterisks were removed when the card names were imported from the Oracle file.Aswan jaguar wrote:@Sonic about images everything is great except the * aproximation asterisk that is missing from aproximately made cards.
My fault for calling the log "Errors.txt" and not something like Warnings.txt. It helped in squashing a lot of the typing mistakes that were originally in card_data but not all warnings mean the data is wrong, these currently showing are harmless. For example P/T values in manalink.xls are used for display only while P/T in CT_all is used by the engine. So a 0/0 creature might have */* in ct_all just so the AI won't consider the card useless etc. Ghostfire has a red cost but it's colorless and the log shows only results of dumb comparison. Besides with the huge pile of hacks in C code overriding various things in the engine I prefer leaving all ct_all changes to Gargaroz (and other people writing C code).Sonic wrote:I thought the missing 100/100 P/T were an error on my part. As the ERRORS file had been reporting a mismatch in the P/T values of Clone and Vesuvan Doppelganger, and a few other cards which originally had 100/100 entries.
Not sure on the Ghostfire. The ERRORS file was reporting that Ghostfire was missing a value in the 'Color Red' entry of the ct_all.csv file.
Did nothing to the 'Sub type' entries though.
Does it happen in the new version of DB that I just posted in the development forum? I believe I fixed that bug but if not, please tell me exact order of buttons pressing to reproduce it.0rion79 wrote:EDIT - Ah, some more generic bugs: if you try to enable or disable cards type buttons (creatures, enchantments ecc.), and leave only lands button active and play a bit with the other buttons, you will see that the first land in Legends, Dark and Antiquities sets will disappear leaving an empty "hole". Such cards are Hammerheim, City of Shadows and Mishra's Factory.
The same bugs repeats with other cards categories: I've just seen that the same happens with Artizan of Kozilek but, even if the cards is not visibile in the lower part of the deck editor, by double-clicking on it, it will still be included in the decks.
That's because Rules Engine is incorrectly set in Manalink.xls. It should have expansion type of 1000h like any other effect instead of 200h. Easy to fix. Thanks for the information.0rion79 wrote:No, I didn't see that. Now everything works great, including creatures filters that I love so much. The only defect that I can find is that Rules Engine is still among the selectable cards.
It's different that the one posted by gmzombie here as revised and that is already included in the new version of db? If so, give me the link to it.In the final version, please remember to include my hi-res recontruction of the classic skin for decbuilder.
Yes, a little bit but I've just seen that they were included as "revised" and I didn't recognize them! They are like the original ones, just a bit more fancy and they also use some of Mathusalem's arts shifted in Blue tonality to better fit with the original background.Mok wrote:It's different that the one posted by gmzombie here as revised and that is already included in the new version of db? If so, give me the link to it.
Sure, you can try your own just by replacing existing files or making a new skin subdirectory. The filenames must be the same, that's all, you can use your .bmp files without problem after renaming them to .pic. The changes are: yellow.pic -> white.pic, gray.pic -> black.pic, eight.pic -> other.pic, and 2 dialog backgrounds that were previously used from another magic art directory are now called infobkg.pic and filterbkg.pic (you can copy them from any other skin). In case you want to skin the 3 big buttons, the file is called BtnBkg.pic. All other names are unchanged. So it's easy to make your custom skin to work with new version of db.0rion79 wrote:The nice thing is that those arts now may be combined as players like it more: eg, I suggest to replace "my" background (the arts that stay over the cards in the deck) with the same file from the "dark" version of deckbuilder.
Yes, but is it so hard to edit 1 line in manalink.ini and then run deck.exe and see how it looks? I mean it's not like there's a hundred of skins there0rion79 wrote:yep! But it would even easier if each folder had jpg preview of each file, since not all of us have pic file readers and windows does not read them by default.