Preacher Causes Strange Bug

[bmlaw]

Describe the bug
When the opponent (AI) has a Preacher in play and attempts to use its ability, strange bugs result.

First encountered in Adventure. After the AI tapped their Preacher, the ability didn't resolve, and many cards were "blacked out" and rendered invalid:

No spells or cards could be played. User still won by alpha-striking with creatures repeatedly.

When tested in standard forge mode, a Java exception was encountered:

java.lang.InterruptedException
	at java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1100)
	at java.base/java.util.concurrent.CountDownLatch.await(CountDownLatch.java:230)
	at forge.gamemodes.match.input.InputSyncronizedBase.awaitLatchRelease(InputSyncronizedBase.java:22)
	at forge.gamemodes.match.input.InputSyncronizedBase.showAndWait(InputSyncronizedBase.java:35)
	at forge.player.TargetSelection.chooseTargets(TargetSelection.java:187)
	at forge.player.PlayerControllerHuman.chooseTargetsFor(PlayerControllerHuman.java:2144)
	at forge.ai.ability.ControlGainAi.canPlay(ControlGainAi.java:96)
	at forge.ai.SpellAbilityAi.canPlayWithSubs(SpellAbilityAi.java:43)
	at forge.ai.AiController.canPlaySa(AiController.java:953)
	at forge.ai.AiController.canPlayAndPayForFace(AiController.java:896)
	at forge.ai.AiController.canPlayAndPayFor(AiController.java:875)
	at forge.ai.AiController.lambda$chooseSpellAbilityToPlayFromList$6(AiController.java:1703)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at java.base/java.lang.Thread.run(Thread.java:1583)

Notably, the human player was able to use Preacher's ability successfully. It was only when the AI attempted to use theirs that the exception occurred.

To Reproduce
Steps to reproduce the behavior:

1. Create deck with Preacher(s).
2. Give deck to AI.
3. Play against AI.
4. Play a (targetable) creature.
5. Wait.

Expected behavior
Not this.

Screenshots
See above.

Desktop (please complete the following information):

• OS: Windows 11
• Version 2.0.0.8 snapshot 12.05

[Agetian]

Hmm, that's the kind of exception I've never seen before. I did see some wonky behavior with this card by the way, regardless of the AI, but don't remember what the issue was exactly. Any ideas what might be happening here with this exception? Looks like some kind of a threading-related issue?

[Hanmac]

The Problem is "target creature of an opponents choice" that confuses the AI

So it tries to activate the Ability, but then it doesn't want to (depending on the target)

similar problem with Echo Chamber

[tool4ever]

one of the AI timeout tradeoffs, I can't really improve that feature

[Hanmac]

@tool4ever the main problem isn't really the timeout, but this funky (should i activate such ability?)