Page 9 of 9

Re: Bug reports for v0.7.1a

PostPosted: 07 Jul 2011, 03:54
by gumgod
MageKing17 wrote:
gumgod wrote:I can convert images, I just thought it was odd. Thanks for the tip.
Convert and resize, unless you happen to have a bunch of 200x285 (or whatever the hell dimensions it is) pictures that didn't come from Wizards' site.
Yea. I got that part too. ;) I didn't have any problems getting an image to load in the game that way, but I'm curious why multiple cards from the starter set don't load. (I only really tested two cards Goblin Settler and Stream of Acid).

Re: Bug reports for v0.7.1c

PostPosted: 16 Jun 2012, 04:31
by MageKing17
I, uh, found a bug in v0.7.c; two of the most recent additions to MemoryVariables.py, battlefield_tracker and cast_from_graveyard_tracker, weren't added to the __all__ variable, so you can't actually use them (unless you manually import them, which is silly). I've already fixed this in my local repository (and added a new variable called land_record, which is a counterpart to spell_record, recording all the lands played during the turn), but I don't want to make a v0.7.1d release just to fix that one bug; hasn't anybody else found something wrong with v0.7.1c?

Re: Bug reports for v0.7.1c

PostPosted: 26 Mar 2013, 13:11
by Xeddicus
I just found out about Incantus (and every other CCG engine) and just want to say thanks for the program and hope it's not dead. And even though it's apparently been 9 months since the bug was found I'd also be happy with an update that fixed bugs no matter how small it was.

Re: Bug reports for v0.7.1c

PostPosted: 26 Mar 2013, 14:52
by MageKing17
Xeddicus wrote:I just found out about Incantus (and every other CCG engine) and just want to say thanks for the program and hope it's not dead. And even though it's apparently been 9 months since the bug was found I'd also be happy with an update that fixed bugs no matter how small it was.
While development has ground to a halt, mostly due to how busy I am in real life, you can find my latest version of the code here, and the latest version of Incantus (the person)'s version of the code here. The reason this wasn't released is because there are some unresolved issues with the new UI code, but if you want to try it out, it does have more features than v0.7.1c.

Re: Bug reports for v0.7.1c

PostPosted: 26 Mar 2013, 15:32
by Xeddicus
Thanks. Is there a post somewhere showing what I need to compile the code? And what are the UI issues? Thanks again for all the work.

Re: Bug reports for v0.7.1c

PostPosted: 26 Mar 2013, 16:08
by MageKing17
Xeddicus wrote:Thanks. Is there a post somewhere showing what I need to compile the code?
Python isn't a compiled language; if you have Python 2.6 (might work with 2.7), Pyglet, greenlet, twisted, and cocos2d (and their dependencies), then you can just run main.py to try to run the game. If you have py2exe, you can run setup.py2exe.py to make an executable from the latest code.

Xeddicus wrote:And what are the UI issues? Thanks again for all the work.
For one thing, the new card rendering only works on "standard frame" cards (so Planeswalkers, levelers, and even future-shifted cards will look wonky). For another thing, after running for a while, some sort of bug was causing cards to stop rendering text, which was a little weird, and I couldn't track down the cause.

Also, the source code doesn't include everything you need to run the game; you also need an up-to-date card database, which you can obtain here.