Forge 01/17 (unofficial BETA) version

[apthaven]

Great. I've been missing out in the forums as of late, and its nice to see that there's a new version out.

A many thanks

The new visual themes add great eye candy to the already wonderful game.

The new vampire cards are good, vampire decks are now starting to become more of a possibility now especially with Worldwake coming out soon. (Hoping that Forge too could implement them)

[DennisBergkamp]

Some of the prompts are a bit non-standard, such as 'destroy' rather than 'choose' target creature or enchantment for Ethersworn Adjudicator. I haven't run into any actual bugs except for storm-related ones so far though (other than incomplete implementations, which I'm sure won't be for long ). You all rock!

EDIT: My blocked Treva, the Renewer with double strike but without trample still triggered, and Megrim sometimes seems to forget its job especially with Gerrard's Verdict. Still, those are extremely minor.

Ahh, I looked at the Gerrard's Verdict code, and I see what's going on. I coded that card a long time ago (before I knew what I was doing, really ), and it doesn't actually do any discards, it just directly moves cards from hand to graveyard

[freestorageaccount]

Ahh, I looked at the Gerrard's Verdict code, and I see what's going on. I coded that card a long time ago (before I knew what I was doing, really ), and it doesn't actually do any discards, it just directly moves cards from hand to graveyard

Oh, I see. Well, as people keep on playing eventually those ~0.01% of cases where the user can detect the kludge have to come up. Hopefully after the warranty's expired.

I ran into problems when trying to open my / deck for editing. The message is rather long, which is incidentally how I discovered this forum has a 60K-character cap per post; I think it dumped my entire card pool. Rather than triple-post, I placed it at http://pastebin.com/f8afa3c3 (the version date 10/01/01 about halfway through should in fact be 10/01/17 or else I wouldn't be writing in this thread).

Thankfully, the other decks are unaffected so far, but I backed my questData up anyway. Does anyone know what's causing that?

In case anyone here has as exciting a life as I do, the index (read in hex) of the pastebin posting is a prime. This fact is in no way whatsoever a subliminal message and does not warrant any investigation at all.

[DennisBergkamp]

Ahh, I looked at the Gerrard's Verdict code, and I see what's going on. I coded that card a long time ago (before I knew what I was doing, really ), and it doesn't actually do any discards, it just directly moves cards from hand to graveyard

Oh, I see. Well, as people keep on playing eventually those ~0.01% of cases where the user can detect the kludge have to come up. Hopefully after the warranty's expired.

I ran into problems when trying to open my / deck for editing. The message is rather long, which is incidentally how I discovered this forum has a 60K-character cap per post; I think it dumped my entire card pool. Rather than triple-post, I placed it at http://pastebin.com/f8afa3c3 (the version date 10/01/01 about halfway through should in fact be 10/01/17 or else I wouldn't be writing in this thread).

Thankfully, the other decks are unaffected so far, but I backed my questData up anyway. Does anyone know what's causing that?

In case anyone here has as exciting a life as I do, the index (read in hex) of the pastebin posting is a prime. This fact is in no way whatsoever a subliminal message and does not warrant any investigation at all.

The only reason I can think of is Culling Sun not being in your res/quest/rare.txt file. If it's not, add it and see if that fixes it.
But then again, I'm not sure if that has anything to do with it at all
Chris might know...

[Chris H.]

I think that he has an older, out of date set of rarity files and they are missing the card in question. I would suggest downloading the most recent set of rarity files and using them instead.

All Rarities 01-17.zip

[eljinete7]

Hi, guys (this is my first post here). I can't see large image of cards at bottom right on the screen. If I use resizable game area option, then the big picture of selected card looks corrupted. When I run this (01/17) version without resizable game area option then large image of cards is cropped at the bottom. Why I can to solve this? Should I wait until a new Forge version be released? Any help? Thanks in advance. Keep that good work.

PS: Sorry for my poor English.

[DennisBergkamp]

Wait for the new version... I assume you're on a Mac or Linux? Big images on the right hand side won't show up for those OSes in the 01-17 version (I broke it ).

EDIT: OR, you could get the latest SVN version if you have some SVN client (like Eclipse) and are able to compile java... http://code.google.com/p/cardforge/

[Chris H.]

And another possible explanation:

The card picture at the bottom right resizes as you increase or decrease the width of the card information panel. This at times can create an image which is somewhat distorted.

Try resizing the width until the picture appears to be readable.

[eljinete7]

Wait for the new version... I assume you're on a Mac or Linux? Big images on the right hand side won't show up for those OSes in the 01-17 version (I broke it ).

EDIT: OR, you could get the latest SVN version if you have some SVN client (like Eclipse) and are able to compile java... http://code.google.com/p/cardforge/

No. I don't use Mac or Linux systems. I'm trying last Forge version on a Windows XP SP3 PC machine. I suppose a lot of another people are in my same situation. Perhaps you could release a new 'big image bugfix' version for 01-17 Forge.

[freestorageaccount]

I think that he has an older, out of date set of rarity files and they are missing the card in question. I would suggest downloading the most recent set of rarity files and using them instead.

All Rarities 01-17.zip

Argh. I replaced the files in my \res and \res\quest, but the same error appears. The unsettling part is that the deck was loaded successfully many times and suddenly failed. Is this more file corruption or a bug?

[DennisBergkamp]

Ok, I don't know... I have no idea what's causing it. One thing I could do is edit the QuestData file and remove Culling Sun from the deck itself.

What about Culling Sun, is it in the list of cards when just opening the deck editor?

[DennisBergkamp]

Wait for the new version... I assume you're on a Mac or Linux? Big images on the right hand side won't show up for those OSes in the 01-17 version (I broke it ).

EDIT: OR, you could get the latest SVN version if you have some SVN client (like Eclipse) and are able to compile java... http://code.google.com/p/cardforge/

No. I don't use Mac or Linux systems. I'm trying last Forge version on a Windows XP SP3 PC machine. I suppose a lot of another people are in my same situation. Perhaps you could release a new 'big image bugfix' version for 01-17 Forge.

Yeah, I'll release something soon... sometime this weekend

[Chris H.]

Ok, I don't know... I have no idea what's causing it. One thing I could do is edit the QuestData file and remove Culling Sun from the deck itself.

What about Culling Sun, is it in the list of cards when just opening the deck editor?

`
I just did a search of the contents of the error report that was posted to pastebin. Culling Sun only shows up in the error message and I could not find it any where in the array.

I wonder if the array data for the card pool has a maximum size in the file. We may need to try replacing one of the basic lands, etc with a Culling Sun card.

[freestorageaccount]

I just checked this forum after rebuilding the deck. The problem seems to have disappeared for now, but I'm down one Culling Sun. Freaky.

[atar]

Hello all,i need help downloading the LQ pics,because when i'm trying to do that an error message appears:
An error has occured. You can copy/paste this message or save it to a file.
Please report this, plus what you tried to do, to:
viewforum.php?f=26
If you don't want to register an account, you can mail it directly to
mtgerror@yahoo.com


You must be connected to the Internet. Error downloading card:
Card name: mountain.jpg
URL: http://resources.wizards.com/magic/card ... d73958.jpg


Version:
Forge -- official beta: 10/01/01, SVN revision: 275

Detailed error trace:
java.io.FileNotFoundException: res\pics\mountain.jpg (The system cannot find the path specified)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(Unknown Source)
at java.io.FileOutputStream.<init>(Unknown Source)
at forge.Gui_DownloadPictures_LQ.run(Gui_DownloadPictures_LQ.java:207)
at java.lang.Thread.run(Unknown Source)

and the process crashes.Any suggestions?