Page 1 of 1
Hello, thanks, & question
Posted:
30 May 2009, 17:08by brockfanning
Hi all, just wanted to say, wow, excellent work. I'm having a great time with quest mode. I have a newborn in my arms much of the time, so it's nice to be able to play magic without any time limits! Because of said newborn, I'm typing with one hand, so I'll keep this short. Just a quick question: in the deck editor, what does 'e' stand for, under rarity?
Again, great work, this is some awesome software.
Re: Hello, thanks, & question
Posted:
31 May 2009, 04:00by Rob Cashwalker
Hey, congrats on the newborn! Look into getting a sling, it does the holding for you, leaving both arms free. I've got a 6 yo girl and a 2.5 yo boy. I have begun teaching my daughter. I only occasionally get to play FNM and with a couple friends. This is the best part of MTGForge - no opponent required, just like playing solitaire, only much more interesting.
The e seemed to get added in the last update from mtgrares, I don't think there was a clear answer why it showed up.
Re: Hello, thanks, & question
Posted:
31 May 2009, 05:48by GandoTheBard
The E has shown up before this actually and while the significance isn't entirely clear it has something to do with an error I believe. (E for error?) Anyway clearly something needs to be refixed. :p Dennis?
Re: Hello, thanks, & question
Posted:
31 May 2009, 06:07by DennisBergkamp
Yeah I was wondering about that... I think it might have something to do with cards that are in the quest-common, quest-uncommon and quest-rare .txt files, but are not present in the regular rarities files. Since by default we're using your play-balanced rarities files, this might be causing the e's to occur, because there's probably cards in quest-common/uncommon/rare.txt that are not present in the balanced rarities.
To verify this theory, I'll try and copy your tweaked rarities into quest-common/uncommon/rare.txt tomorrow and see if the "e"s still show up.
Re: Hello, thanks, & question
Posted:
31 May 2009, 07:01by zerker2000
mtgrares wrote:The "e" stands for "error". Lets say that you use some set (common.txt, etc..) and you save you quest files. And later you change or update common.txt, etc... MTG Forge reads common.txt, etc... and doesn't find the card name that is currently in your file, so it shows "error" which is abbreviated to just e. Maybe MTG Forge should return c for common instead of e?
Re: Hello, thanks, & question
Posted:
01 Jun 2009, 17:38by mtgrares
e stands for error. If you changed the files common.txt, uncommon.txt, or rare.txt in the middle of the quest mode, when the computer reads your cardpool and it doesn't find it in common.txt, etc.. it returns error which is truncated (shortened) to e. Maybe it should just return c for common if the card isn't found.
Re: Hello, thanks, & question
Posted:
01 Jun 2009, 17:52by DennisBergkamp
But the weird thing is, I seem to be getting this whenever I start a new quest as well. It would be cool if it would return a c for common, u for uncommon and r for rare I suppose
Re: Hello, thanks, & question
Posted:
01 Jun 2009, 17:54by mtgrares
DennisBergkamp wrote:But the weird thing is, I seem to be getting this whenever I start a new quest as well. It would be cool if it would return a c for common, u for uncommon and r for rare I suppose
Well if you are getting that problem to begin with then it is a real problem. I'll look at my code. The quest code still is pretty simple so hopefully I can figure it out.
Re: Hello, thanks, & question
Posted:
02 Jun 2009, 02:29by zerker2000
DennisBergkamp wrote:But the weird thing is, I seem to be getting this whenever I start a new quest as well. It would be cool if it would return a c for common, u for uncommon and r for rare I suppose
Yes same here, when I start a quest cards have mostly blank or error for rarity.
Re: Hello, thanks, & question
Posted:
03 Jun 2009, 09:56by tchiseen
Ah, I was wondering what the 'e' was. It makes sense.
I see lots of them. lol.
There are also the standard rarities that show up too. And then 'n' for new cards. My only gripe is that when sorting, it doesn't separate the 'n's from the 'e's, so I have to wade through the 'e's to see my 'n's