Collectible Card Game Headquarters

Max mtg wrote:Sol, I could not reproduce that thing with sideboard. Did you do anything specific to achieve that?

Not that I can tell. I'm in Quest Mode, I have a sideboard, and I just click inside on the first card. I don't think I ever press spacebar or anything else. I'll look again when I get home from work (in 11 hours) to see if there's anything that might be part of it.

The empty dialogue window problem comes back in forge20700.This problem has been appeared in the early forge1.3.10snapshot versions.My computer is using java7 by the way.

friarsol wrote:

Max mtg wrote:Sol, I could not reproduce that thing with sideboard. Did you do anything specific to achieve that?

Not that I can tell. I'm in Quest Mode, I have a sideboard, and I just click inside on the first card. I don't think I ever press spacebar or anything else. I'll look again when I get home from work (in 11 hours) to see if there's anything that might be part of it.

Does having sleight of hand make difference for repro of this issue?

when i use unexpected results after 1 match wont work properly,

when ai uses Liliane of the veil ultimate Liliane stays on 5 counters (but i like it makes it harder to beat)

during end phase when i use a artifact that alows me to exile a creature during end phase and return to field i wont alow me to do this on creatures that i got from ai with act of treason is that normal

For my reference - Unexpected Results, Liliana of the Veil

Max mtg wrote:Does having sleight of hand make difference for repro of this issue?

I'm fairly certain I don't have the sleight of hand quest item, but I'll double check in a few hours.

tengumai wrote:Castigate

On 1.3.11, Castigate forces me to discard a card from my hand, even when I select an opponent as a target.

I have commited in r20710 a script that would produce a correct effect, but stack description is still wrong. At least, this action has decreased the severeness of bug.

Max mtg wrote:

tengumai wrote:Castigate

On 1.3.11, Castigate forces me to discard a card from my hand, even when I select an opponent as a target.

I have commited in r20710 a script that would produce a correct effect, but stack description is still wrong. At least, this action has decreased the severeness of bug.

This looks to be the same thing that moomarc was going to fix as reported on the main threads. It shouldn't really need any script changes.

friarsol wrote:

Max mtg wrote:Does having sleight of hand make difference for repro of this issue?

I'm fairly certain I don't have the sleight of hand quest item, but I'll double check in a few hours.

Definitely no Sleight of Hand. I've attached my quest data file in case that will help.

forge-1.3.12-20130401.125222-4
Kodama's Reach had blank boxes for the lands that I was searching for. I could X the boxes but I would not receive any lands in play or in hand.

friarsol wrote:

Max mtg wrote:

tengumai wrote:Castigate

On 1.3.11, Castigate forces me to discard a card from my hand, even when I select an opponent as a target.

I have commited in r20710 a script that would produce a correct effect, but stack description is still wrong. At least, this action has decreased the severeness of bug.

This looks to be the same thing that moomarc was going to fix as reported on the main threads. It shouldn't really need any script changes.

Impressive response time!

Corwin72 wrote:forge-1.3.12-20130401.125222-4
Kodama's Reach had blank boxes for the lands that I was searching for. I could X the boxes but I would not receive any lands in play or in hand.

Oh! Same issue as 7543021 has!
Corwin, please write down your system specs.
I'm particularly interested in CPU model, Java version and OS.

That must be the threads. Swing dialogs invoked from non-EDT thread are not guaranteed to work, the what myk has warned against. In this case I'll have to wrap them into invokeInEdtAndWait (or some similiar method)

friarsol wrote:

Max mtg wrote:

tengumai wrote:Castigate

On 1.3.11, Castigate forces me to discard a card from my hand, even when I select an opponent as a target.

I have commited in r20710 a script that would produce a correct effect, but stack description is still wrong. At least, this action has decreased the severeness of bug.

This looks to be the same thing that moomarc was going to fix as reported on the main threads. It shouldn't really need any script changes.

For now I've added the Chooser and DefinedPlayer parameters to other similar cards because I need a little more time to work some things out (r20722). It makes the scripts a little more foolproof if nothing else. Also, looking at the stack description, it has never been able to handle targeted hidden origin changes and needs quite a large overhaul.

EDIT: The main issue is fixed. It is now handled the way I had intended initially when I made the changes for Oath of Lieges, I had just made a slight logic error.

Max mtg wrote:

Corwin72 wrote:forge-1.3.12-20130401.125222-4
Kodama's Reach had blank boxes for the lands that I was searching for. I could X the boxes but I would not receive any lands in play or in hand.

Oh! Same issue as 7543021 has!
Corwin, please write down your system specs.
I'm particularly interested in CPU model, Java version and OS.

That must be the threads. Swing dialogs invoked from non-EDT thread are not guaranteed to work, the what myk has warned against. In this case I'll have to wrap them into invokeInEdtAndWait (or some similiar method)

Here is mine，hope it is helpful
Java environment： Java 7 Update 1 Standard Edition(build 1.7.0_01-b08)
System：win7 32-bit
Cpu： Intel celeron E3400（dual core 2.60Ghz）

moomarc wrote:For now I've added the Chooser and DefinedPlayer parameters to other similar cards because I need a little more time to work some things out (r20722). It makes the scripts a little more foolproof if nothing else. Also, looking at the stack description, it has never been able to handle targeted hidden origin changes and needs quite a large overhaul.

EDIT: The main issue is fixed. It is now handled the way I had intended initially when I made the changes for Oath of Lieges, I had just made a slight logic error.

Maybe we should add the stack descriptions of these cards manually, I searched "\bChangeZone\b.*ValidTgts\$ Opponent", only got 22 results.