Page 4 of 9

Re: Bug reports for v0.591

PostPosted: 25 May 2009, 13:52
by purklefluff
found a bug that crashes the game completely and closes the window:

when polluted delta is tapped (i don't think it was specific to the ability, but it may have been) the program shuts down.

haven't got the code from the console window. i'll see if i can replicate the effects again and try to get it this time.

other than that it seems to be working well! thanks for this guys, it's a great program.

Re: Bug reports for v0.591

PostPosted: 25 May 2009, 16:17
by juzamjedi
Hello Purklefluff,

I tried it just now and Polluted Delta seems to work OK for me. Try looking for a .log file that is the same name as your executable. Open that up after your next crash and post that text to this thread. The last traceback should be the relevant data.

Re: Bug reports for v0.591

PostPosted: 25 May 2009, 21:05
by purklefluff
ok, i got this:

Execution error with Nightscape Familiar
Darkling Stalker not implemented
Traceback (most recent call last):
File "Incantus/main.py", line 7, in <module>
main()
File "K:\Incantus\Incantus\src\ui\Incantus.py", line 790, in main
File "K:\Incantus\Incantus\src\ui\Incantus.py", line 656, in run
File "K:\Incantus\Incantus\src\engine\GameKeeper.py", line 82, in start
File "K:\Incantus\Incantus\src\engine\GameKeeper.py", line 115, in run
File "K:\Incantus\Incantus\src\engine\GameKeeper.py", line 242, in upkeepStep
File "K:\Incantus\Incantus\src\engine\GameKeeper.py", line 418, in playInstantaneous
File "K:\Incantus\Incantus\src\engine\GameKeeper.py", line 420, in playStackInstant
File "K:\Incantus\Incantus\src\engine\GameKeeper.py", line 433, in continuePlay
File "K:\Incantus\Incantus\src\engine\Player.py", line 461, in getAction
File "K:\Incantus\Incantus\src\engine\Player.py", line 443, in get
File "K:\Incantus\Incantus\src\engine\Player.py", line 432, in input
File "K:\Incantus\Incantus\src\ui\Incantus.py", line 756, in userinput
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/pyglet/clock.py", line 317, in tick
item.next_ts = self._get_soft_next_ts(ts, item.interval)
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/pyglet/clock.py", line 585, in _get_soft_next_ts
if not taken(next_ts, interval / 4):
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/pyglet/clock.py", line 563, in taken
if abs(item.next_ts - ts) <= e:
TypeError: unsupported operand type(s) for -: 'NoneType' and 'float'
hope this helps. it's from the console just after it quit....... wasn't due to the polluted delta this time. i think it may be due to the turns?

Re: Bug reports for v0.591

PostPosted: 26 May 2009, 20:36
by MageKing17
That sounds like your version of Pyglet has a bug. Are you using version 1.1.3? Because I'm still using 1.1.2, and this bug could have been introduced in the new version.

Re: Bug reports for v0.591

PostPosted: 17 Jun 2009, 23:40
by juzamjedi
Here is a new one. Several nonbasic lands in play when Magus of the Moon is put into a graveyard from play I get this error:

Code: Select all
Traceback (most recent call last):
  File "main.py", line 7, in <module>
  File "ui\Incantus.pyo", line 790, in main
  File "ui\Incantus.pyo", line 656, in run
  File "engine\GameKeeper.pyo", line 82, in start
  File "engine\GameKeeper.pyo", line 116, in run
  File "engine\GameKeeper.pyo", line 249, in mainPhase1
  File "engine\GameKeeper.pyo", line 396, in playSpells
  File "engine\GameKeeper.pyo", line 399, in playStackSpells
  File "engine\GameKeeper.pyo", line 226, in checkSBE
  File "engine\GameObjects.pyo", line 15, in send
  File "engine\pydispatch\dispatcher.pyo", line 392, in send
  File "engine\pydispatch\robustapply.pyo", line 47, in robustApply
  File "engine\Zone.pyo", line 82, in commit
  File "engine\CardRoles.pyo", line 323, in leavingZone
  File "engine\CardRoles.pyo", line 69, in leavingZone
  File "engine\abilities.pyo", line 155, in leavingZone
  File "engine\abilities.pyo", line 20, in disable
  File "engine\Ability\StaticAbility.pyo", line 26, in disable
  File "engine\Ability\StaticAbility.pyo", line 33, in toggle
  File "engine\Ability\StaticAbility.pyo", line 82, in _disable
  File "engine\Ability\StaticAbility.pyo", line 104, in remove_effects
  File "engine\Ability\EffectsUtilities.pyo", line 36, in expire
  File "engine\characteristics.pyo", line 202, in expire
  File "engine\characteristics.pyo", line 140, in remove
  File "engine\characteristics.pyo", line 122, in __eq__
  File "engine\characteristics.pyo", line 85, in __contains__
  File "engine\characteristics.pyo", line 122, in __eq__
  File "engine\characteristics.pyo", line 85, in __contains__
  File "engine\characteristics.pyo", line 122, in __eq__
  File "engine\characteristics.pyo", line 85, in __contains__
... [repeated]
RuntimeError: maximum recursion depth exceeded

Re: Bug reports for v0.591

PostPosted: 19 Jun 2009, 22:08
by MageKing17
juzamjedi wrote:Here is a new one. Several nonbasic lands in play when Magus of the Moon is put into a graveyard from play I get this error:

Code: Select all
Traceback (most recent call last):
  File "main.py", line 7, in <module>
  File "ui\Incantus.pyo", line 790, in main
  File "ui\Incantus.pyo", line 656, in run
  File "engine\GameKeeper.pyo", line 82, in start
  File "engine\GameKeeper.pyo", line 116, in run
  File "engine\GameKeeper.pyo", line 249, in mainPhase1
  File "engine\GameKeeper.pyo", line 396, in playSpells
  File "engine\GameKeeper.pyo", line 399, in playStackSpells
  File "engine\GameKeeper.pyo", line 226, in checkSBE
  File "engine\GameObjects.pyo", line 15, in send
  File "engine\pydispatch\dispatcher.pyo", line 392, in send
  File "engine\pydispatch\robustapply.pyo", line 47, in robustApply
  File "engine\Zone.pyo", line 82, in commit
  File "engine\CardRoles.pyo", line 323, in leavingZone
  File "engine\CardRoles.pyo", line 69, in leavingZone
  File "engine\abilities.pyo", line 155, in leavingZone
  File "engine\abilities.pyo", line 20, in disable
  File "engine\Ability\StaticAbility.pyo", line 26, in disable
  File "engine\Ability\StaticAbility.pyo", line 33, in toggle
  File "engine\Ability\StaticAbility.pyo", line 82, in _disable
  File "engine\Ability\StaticAbility.pyo", line 104, in remove_effects
  File "engine\Ability\EffectsUtilities.pyo", line 36, in expire
  File "engine\characteristics.pyo", line 202, in expire
  File "engine\characteristics.pyo", line 140, in remove
  File "engine\characteristics.pyo", line 122, in __eq__
  File "engine\characteristics.pyo", line 85, in __contains__
  File "engine\characteristics.pyo", line 122, in __eq__
  File "engine\characteristics.pyo", line 85, in __contains__
  File "engine\characteristics.pyo", line 122, in __eq__
  File "engine\characteristics.pyo", line 85, in __contains__
... [repeated]
RuntimeError: maximum recursion depth exceeded
This one confused me until I took a look at the code on line 122 and 85 of characteristics.py. Looks like remove_characteristics is using circular logic... __eq__ checks "if other in self" while __contains__ checks "if self == other". You can easily imagine the infinite loop this leads to. Should be fixed for the next version.

Re: Bug reports for v0.591

PostPosted: 21 Jun 2009, 01:10
by FiberBundle
Hi all. I recently discovered this project and have to say I'm impressed and excited about it. I run Arch Linux so couldn't test v0.591 -- only v0.59. (I am eagerly awaiting your new release.) However, I ran across some issues that may not be addressed yet in the newer versions, so I thought I'd post it here anyway.

  • Installation Notes: Your .pyo files are compiled for Python2.5. I was running Python2.6 which won't run them. After installing Python2.5 it ran fine. The library pyglet 1.1.3 I had installed had timing bugs (I believe reported here elsewhere : comparing a Null against a timing number somewhere in pyglet.), so I had to downgrade to pyglet 1.1.2. Afterwards I've had no issues from pyglet itself. You should probably note somewhere the installation dependencies: Python2.5, Pyglet1.1.2.
  • Cards that said they were supported in this version, but didn't work properly:
    • Gilder Bairn : prompts for how to tap mana for ability, but doesn't actually let you tap mana or do anything
    • Incremental Growth : select creatures, pay mana, goes to graveyard, no effect!
    • Coat of Arms : Power/Toughness of creatures does not get updated as board changes. They are set once as coat of arms comes into play, and new creatures are set once as they come into play, and that's it.

The game exposing the last note was epic enough I snagged some screenshots for fun (attached). You can clearly see the discrepancies in powers of insects as Symbiotic Wurms were sacrificed to Nantuko Husk when Coat of Arms was in play. Also visible are the large numbers of tokens on opponent's Phytohydras. For the curious, neither side could win this game due to opponent having Spike Feeders: the insect deck lost due to eventually being decked.

I'll probably wait for the new version before posting any more bugs here. Keep up the good work!

Re: Bug reports for v0.591

PostPosted: 21 Jun 2009, 15:33
by MageKing17
Sadly, your report is practically worthless due to the many changes that have occurred since v0.59... I know Coat of Arms has gone through numerous changes, and the current version hasn't even been tested! The problem with Incremental Growth also sounds like a bug that was fixed long ago with MultipleTargets thinking everything was invalid (I spotted it while playing with Candelabra of Tawnos... in fact, I think that was the bug that made me release v0.591 so fast). As for your problem with Gilder Bairn, I have no idea. All mana costs are handled the same way... you choose which version of the hybrid cost you want to pay, then play mana abilities until you can pay it. There's no way you could pay for Incremental Growth and not Gilder Bairn's ability. And, again, with the many changes that have happened since v0.59, figuring out what the cause of the problem was/is would be nearly impossible.

Not that I don't appreciate your willingness to help, it's just that bug reports from two versions ago aren't very much use. ;)

I really want to get a v0.592 out ASAP, but I just don't have the time for it at the moment. Too many items on the to-do list, not enough time to do them. Hopefully I'll have the time for it some day soon.

Re: Bug reports for v0.591

PostPosted: 29 Aug 2009, 15:10
by benjotron
Goblin Cohort crashes the game as soon as the controller's declare attackers step occurs, if he is ineligible to attack (even if he has been summoned this turn). I'm assuming the code that determines if is eligible to be declared an attacker is broken. I haven't looked at the code, but this should be simple to reproduce.

EDIT: it also crashes if Goblin Cohort is eligible to attack. I tried attaching a replay file, but the forum wouldn't allow the the extension type.

Re: Bug reports for v0.591

PostPosted: 29 Aug 2009, 19:45
by MageKing17
benjotron wrote:Goblin Cohort crashes the game as soon as the controller's declare attackers step occurs, if he is ineligible to attack (even if he has been summoned this turn). I'm assuming the code that determines if is eligible to be declared an attacker is broken. I haven't looked at the code, but this should be simple to reproduce.

EDIT: it also crashes if Goblin Cohort is eligible to attack. I tried attaching a replay file, but the forum wouldn't allow the the extension type.
Any bug reports from v0.591 (or even from the v0.592 beta, which some of you have) are mostly pointless at this point. Not only is the v0.592 beta very different from v0.591 (and the card database drastically different from the v0.591 release), but we're in the middle of making some very major engine changes (for those of you paying attention, yes, the new spell framework is underway (I've been busy with Real Life, but Incantus has merged the Stack and the CardStack and a whole bunch of other stuff, and DorkMasterFlek has made a wide variety of UI improvements, and I haven't had time to test any of it), so the card database is about to be rendered unusable without an overhaul).

Re: Bug reports for v0.591

PostPosted: 06 Nov 2009, 15:09
by Strainer
Hi everyone.

While looking for new Magic software I stumbled across Incantus the other day. As far as I seen it, this is the best looking project for Rules Enforcement, and I would love to contribute to it in any way.(Mostly creating cards is what I'd like to help with)

It also seems hard for me to find the most recent version of Incantus, if someone could give me a hint where to find the last revision and the last .exe that would be very appreciated.

Thanks.

Re: Bug reports for v0.591

PostPosted: 06 Nov 2009, 17:13
by Huggybaby
You'll have to try the chat room for the latest.

Re: Bug reports for v0.591

PostPosted: 06 Nov 2009, 21:10
by Strainer
I've been in Efnet, #incantus the last 2 days, but noone ever replied to me. I guess communication via the forum is more convenient somehow.

Re: Bug reports for v0.591

PostPosted: 06 Nov 2009, 22:16
by Huggybaby
Hmm, maybe they pooped out. Send Incantus a PM and see if he's around.

Re: Bug reports for v0.591

PostPosted: 25 Nov 2009, 23:43
by juzamjedi
Recently I tried to play Birds of Paradise and the game would not allow me to play it. It did not ask me to pay mana costs and perhaps telling is that the life total icon resets. The life total icon reset is similar to what happens when I try to play a land after I have already played a land.