Page 458 of 491

Re: Bug Reports (snapshot builds)

PostPosted: 22 Sep 2018, 16:23
by Finallogic
V1.6.15

Pelt Collector triggers when opponent's creatures enter the battlefield, not just yours.

Re: Bug Reports (snapshot builds)

PostPosted: 22 Sep 2018, 16:29
by Finallogic
V1.6.15

Kraul Harpooner failed to trigger, though there was a creature in my graveyard and an opposing flying creature.

Re: Bug Reports (snapshot builds)

PostPosted: 22 Sep 2018, 20:30
by friarsol
PrinzMurmel wrote:v1.6.15: I played Encrust and enchanted a yet untapped Lys Alana Bowmaster. Nevertheless, when my opponent played an Elf next turn, my 2/2 flyer received 2 damage and was destroyed :roll: Am I mistaken that that should have been prevented by the enchantment?

Regards, P.M. {G}
You are mistaken. That's a triggered ability not an activated one

Re: Bug Reports (snapshot builds)

PostPosted: 23 Sep 2018, 07:56
by Ergg
V1.6.16
Legion Warboss is freezing the game on "Waiting for opponent..." when creating a goblin token at the beginning of combat phase.
It was working in previous snapshot though.

Re: Bug Reports (snapshot builds)

PostPosted: 25 Sep 2018, 21:45
by PrinzMurmel
Question: I was attacking with Cathodion, it was blocked and killed. I received 3 colorless mana, but they were automatically gone after a split second so I could not use them to buy something after combat. Is that correct behaviour? :?:
Regards, P.M. {G}

Re: Bug Reports (snapshot builds)

PostPosted: 26 Sep 2018, 11:36
by Fizanko
using today's snapshot, 1.6.16 r261 looks like the nasty doubling of planeswalker effect is still there.

I was playing the m19 constructed deck "Sarkhan Dragonsoul" and i started to notice that something was very very wrong when i finally played the Sarkhan, Dragonsoul planeswalker card :
- his +2 power wrongly killed every 2/2 creatures the opponent had (so i guess the -1 was in fact getting the doubled bug somehow, but couldn't catch it on the log)

Confirmed the nasty bug was indeed in full effect when i decided to use his -3 power (that deals 4 damage to opponent) and noticed it applied 2 times, dealing 8 damage in 2 steps :

Image
(click on picture for full size)

Re: Bug Reports (snapshot builds)

PostPosted: 26 Sep 2018, 16:39
by friarsol
PrinzMurmel wrote:Question: I was attacking with Cathodion, it was blocked and killed. I received 3 colorless mana, but they were automatically gone after a split second so I could not use them to buy something after combat. Is that correct behaviour? :?:
Regards, P.M. {G}
Yep, mana empties when you change steps. So if your Cathodion dies in combat, you need to use that mana during that damage step.

Re: Bug Reports (snapshot builds)

PostPosted: 27 Sep 2018, 11:25
by Twainer
some Guilds of Ravnica card issues in r266:
Invert//Invent - Power/Toughness switch doesn't do anything
Piston-Fist Cyclops - should work with sorceries
Glaive of the Guildpact - Has no equip ability when in play
Chamber Sentry - X is always set to 0
Urban Utopia - Cost is listed as 1G but game only asks for G
Vigorspore Wurm - Trigger should give vigilance as well

Re: Bug Reports (snapshot builds)

PostPosted: 27 Sep 2018, 13:53
by Bog Wraith
For the last two Snapshot releases including the current "forge-1.6.16-SNAPSHOT-r271-9bbd1da0ba" the program crashes on startup and produces this very small bug report.


"java.lang.NullPointerException
at forge.quest.QuestController.resetDuelsManager(QuestController.java:434)
at forge.quest.QuestController.load(QuestController.java:242)
at forge.control.FControl.initialize(FControl.java:235)
at forge.view.Main.main(Main.java:60)"


I've had no problems what so ever running the program until now and I update with almost every Snapshot release on a daily basis and have so for years.

I am running Forge on a Mac and have done so with no issues for a long, long time.

The last version I had running successfully before this problem was Forge_1.6.16_r239. I am running Java 10.02 and have been for awhile now.


Incidentally, I noticed that these last two snapshots have a new arrangement with the file naming, having the "r" number followed by a series of letters & numbers as opposed to the way it was before when the "r" number was at the end of the file name. Just wanted to mention this as these two releases have had this crash, at least for me.
----------------------------------------------------
Edit

Through a process of elimination I found that 2 of my Quest save files were causing this crash, so I deleted them. Not sure why this happened as I have had the same Quest save game files for a long time as I don't play in Quest mode much at all anymore.

Everything, so far, seems to be back running well again.

Re: Bug Reports (snapshot builds)

PostPosted: 27 Sep 2018, 16:24
by stormcat
:1.6.16-SNAPSHOT-r271-9bbd1da0ba
When I tapped Emmara, Soul of the Accord for Convoke, she double triggered.

Re: Bug Reports (snapshot builds)

PostPosted: 28 Sep 2018, 10:20
by stormcat
:1.6.16-SNAPSHOT-r277-2ab59849a8
House Guildmage's second ability should be surveil 2, not surveil 1.(Strangely, the script is 2.)

Re: Bug Reports (snapshot builds)

PostPosted: 29 Sep 2018, 05:12
by KrazyTheFox
Bog Wraith wrote:Incidentally, I noticed that these last two snapshots have a new arrangement with the file naming, having the "r" number followed by a series of letters & numbers as opposed to the way it was before when the "r" number was at the end of the file name. Just wanted to mention this as these two releases have had this crash, at least for me.
This is to aid in bug fixing. The letters/numbers correspond to a specific version of the source code, so we can tell if a bug report is new or old and exactly the version in which the error occurred. Nothing to worry about!

Re: Bug Reports (snapshot builds)

PostPosted: 29 Sep 2018, 17:39
by Bog Wraith
KrazyTheFox wrote:
Bog Wraith wrote:Incidentally, I noticed that these last two snapshots have a new arrangement with the file naming, having the "r" number followed by a series of letters & numbers as opposed to the way it was before when the "r" number was at the end of the file name. Just wanted to mention this as these two releases have had this crash, at least for me.
This is to aid in bug fixing. The letters/numbers correspond to a specific version of the source code, so we can tell if a bug report is new or old and exactly the version in which the error occurred. Nothing to worry about!
Ok for future reference, when I submit a bug report I post which r number snapshot it is. Should I still use only the r number or add the letters/numbers version along with it?

Re: Bug Reports (snapshot builds)

PostPosted: 29 Sep 2018, 20:14
by KrazyTheFox
Bog Wraith wrote:Ok for future reference, when I submit a bug report I post which r number snapshot it is. Should I still use only the r number or add the letters/numbers version along with it?
The letters and numbers are more helpful for developers, while the regular r number is more helpful for general users. I'd post both, personally.

Re: Bug Reports (snapshot builds)

PostPosted: 29 Sep 2018, 22:23
by Fizanko
Fizanko wrote:using today's snapshot, 1.6.16 r261 looks like the nasty doubling of planeswalker effect is still there.

I was playing the m19 constructed deck "Sarkhan Dragonsoul" and i started to notice that something was very very wrong when i finally played the Sarkhan, Dragonsoul planeswalker card :
- his +2 power wrongly killed every 2/2 creatures the opponent had (so i guess the -1 was in fact getting the doubled bug somehow, but couldn't catch it on the log)

Confirmed the nasty bug was indeed in full effect when i decided to use his -3 power (that deals 4 damage to opponent) and noticed it applied 2 times, dealing 8 damage in 2 steps :

Image
(click on picture for full size)
Just tested the new stable release 1.6.6 and i seem to be unable to reproduce this bug with the same deck for 3 matches.

So far Sarkhan, Dragonsoul -3 ability hasn't yet been doubled and the only creatures with x/2 that the +2 ability killed are the one i select (thanks to the Sarkhan's Whelp bonus to Sarkhan ability)

I'll keep my eye opened but it seems this bug is no more hopefully, good job.