by PikWik » 04 Oct 2016, 03:35
with a standard HD, and average processor, ~10 minutes (5200RPM)
probably less with a 7200RPM; guessing ~9 minutes
these are how long both of my systems take.
one is a SBC with the SSD and a rather dated laptop with the 5200.
by Agetian » 04 Oct 2016, 05:01
by Agetian » 20 Nov 2016, 15:30
by Rooger » 20 Nov 2016, 18:03
I have a little problem to report though. I was trying to move around the folder so that my forge doesn't load all the decks but have it inside the forge folder to grab a few decks when needed, however windows gave me an 0x80004005 unspecified error and I wasn't able to move the folders. I tried to delete the folders so that I could unzip the file where I needed but that gave me the same error. Turns out it is because some folders end in a "." like "Extended\Eventide\Big Extended - Praha 18.1." and i guess windows kind of freaks out because of it i'm not sure why. I'm also not able to open the directory, because it is not available.
Is it possible for the script to check if the last character of a created folder is a . and if so delete the character?
by Agetian » 21 Nov 2016, 05:23
As for the issue you've mentioned, here are two packs where the final period symbols have been removed from directory names. Please see if using these packs helps you resolve the issue you're having. Note that deck names and event names may have some other weird symbols in them, and at such big numbers (180000+) it's very difficult to predict what exactly may go wrong in one OS or another. Unfortunately, I don't have a Windows system installed on any of my PCs, and haven't had one for years, so I can't personally test how well this would work on it. I do remember from my past experience with Windows that it's a lot more restrictive when it comes to naming files and it won't let you move, delete or rename files that had any characters that Win considered odd/unsupported for one reason or another, and I also remember that it did not play nearly as well with UTF-8 characters either (not really a problem on *nix systems).
If worst comes to worst and you're still having issues with the packs below, I'd recommend searching for the decks you want inside the archive and then selectively unpacking them, possibly without recreating the folder structure itself to avoid issues with naming.
P.S. If these packs *do* help you though I'd be happy to integrate the extra step of removing the final period symbols from directories into my further releases.
by Rooger » 28 Nov 2016, 13:31
You are right windows can be very picky sometimes and in this case I believe the culprit was winrar. While unpacking the files it doesn't check if the files/folders are "windows ready".
In case anyone was getting the same problem as I did I've found a solution to delete the folders with the period at the end.
-Open a CMD with Administrator Rights
-Type in and press enter: rd /q /s "\\?\[path]\Problematic Folder."
rd /q /s "\\?\C:\Documents and Settings\User\Desktop\Problematic Folder."
This should delete the folder and everything in it so make sure you double check the path to avoid deleting files you don't want to delete.
You can check more info on this here its for Win 7 but the same applies for 10.
by Agetian » 02 Jan 2017, 18:39
Some of the decks have been auto-identified as Frontier, which is apparently a new "modern modern" kind of format: http://mtgsalvation.gamepedia.com/Frontier
There is some underlying change in the technology used for parsing these decks:
1) The folder names with the period in the end should now be auto-renamed not to contain the final period, which should help things on Windows machines.
2) The decks now use the standard Forge comment symbol ("#") for unsupported cards, which should make working with unsupported decks in Forge easier and glitch-free.
Please note that you need a recent SVN build of Forge to enjoy all of these decks.
Enjoy! And my best wishes for all of you in 2017!
by Agetian » 08 Jan 2017, 07:58
In addition to that, there's now a new pack of AI-playable decks that are playable with caveats. Here's the description:
The "AI (Limited) Playable Decks" is a new pack that contains additional decks from MTGDecks.net that have one or several cards in them that are marked as "AI unplayable" in the code base but which are known to be played relatively well given a properly constructed deck and which were used before, for example, in quest decks. IMPORTANT: with these decks, you will get a warning that there are one or more AI-unplayable cards in the deck. However, you can expect relatively good quality of AI gameplay with these cards because they were "tested" in the AI's virtual hands before in quest decks or in other circumstances. You have to expect the lower overall quality of AI with (most of) these decks, however, you should not experience any AI rule violations (at least that's the hope) or serious errors such as crashes. This pack, all in all, adds an additional 10299 decks that can be tried by the AI.
by Agetian » 08 Jan 2017, 12:56
by Agetian » 12 Feb 2017, 19:15
NOTE: Mtgdecks.net no longer provides event information metadata in the deck files, so new decks (after January 8 ) will not be sorted by event, only by set. If Mtgdecks.net restores event information in their metadata, those decks will be resorted in the next update.
Who is online
Users browsing this forum: No registered users and 1 guest