I'm experiencing a bug with HearthRanger in Hearthstone after the recent "The Great Dark Beyond" expansion, which introduced the new Starship mechanic. The issue arises specifically after launching a Starship assembled from various Starship components.
According to the expansion's rules, a Starship, once launched, cannot attack or act during the same turn it is summoned. However, HearthRanger currently tries to repeatedly use the freshly launched Starship to attack during that same turn, causing an infinite action loop. This behavior results in the bot being stuck in an endless cycle, failing to recognize that the Starship is not allowed to attack immediately upon summoning. Below is an excerpt from the log file for reference:
I'm experiencing a bug with HearthRanger in Hearthstone after the recent "The Great Dark Beyond" expansion, which introduced the new Starship mechanic. The issue arises specifically after launching a Starship assembled from various Starship components.
According to the expansion's rules, a Starship, once launched, cannot attack or act during the same turn it is summoned. However, HearthRanger currently tries to repeatedly use the freshly launched Starship to attack during that same turn, causing an infinite action loop. This behavior results in the bot being stuck in an endless cycle, failing to recognize that the Starship is not allowed to attack immediately upon summoning. Below is an excerpt from the log file for reference:
22:02:58:INFO::----NODE PATH---- 98
22:02:58:INFO::-- ROOT NODE -- (value= -2.919998*0 + -24.34*1 = -24.34)
22:02:58:INFO::(value= -8.369995*0 + -30.14*1 = -30.14) Ghoul Charge [0|0|2]
22:02:58:INFO::....(value= 3.850014*0 + -11.92*1 = -11.92) Soulbound Spire [2|2|3] ->Place to board right side.
22:02:58:INFO::........(value= 4.050003*0 + -2.299997*1 = -2.299997) Harbinger of Winter [3|-1|2] -> Gorgonzormu [3|-2|3]
22:02:58:INFO::
22:02:58:INFO::
22:02:58:INFO::----NODE PATH---- 99
22:02:58:INFO::-- ROOT NODE -- (value= -2.919998*0 + -24.34*1 = -24.34)
22:02:58:INFO::(value= -8.369995*0 + -30.14*1 = -30.14) Ghoul Charge [0|0|2]
22:02:58:INFO::....(value= 3.850014*0 + -11.92*1 = -11.92) Soulbound Spire [2|2|3] ->Place to board right side.
22:02:58:INFO::........(value= 10.66001*0 + -3.110003*1 = -3.110003) Frail Ghoul [1|1|1] -> The Lich King [0|29|0]
22:02:58:INFO::
22:02:58:INFO::
22:02:58:INFO::VICPU_CLUSTER_END
22:02:59:INFO::TransitStateMachineFromIdle
22:02:59:INFO::TransitStateMachineFromPlayInGame
22:03:02:DEBUG::in game to idle 7-4
22:03:02:INFO::TransitStateMachineFromIdle
22:03:03:INFO::TransitStateMachineFromPlayInGameSetAside
22:03:05:INFO::TransitStateMachineFromPlayInGameSetAside
22:03:06:INFO::TransitStateMachineFromIdle
22:03:07:INFO::TransitStateMachineFromPlayInGame
22:03:13:DEBUG::in game to idle 7-4
22:03:14:INFO::TransitStateMachineFromIdle
22:03:14:INFO::TransitStateMachineFromPlayInGame
22:03:21:DEBUG::in game to idle 7-4
22:03:21:INFO::TransitStateMachineFromIdle
22:03:22:INFO::TransitStateMachineFromPlayInGame
22:03:22:DEBUG::turn time out - turns - 11
22:03:28:DEBUG::in game to idle 7-4
22:03:29:INFO::TransitStateMachineFromIdle
22:03:30:INFO::TransitStateMachineFromPlayInGame
22:03:30:DEBUG::turn time out - turns - 11
22:03:30:DEBUG::Send hsplay timeout !
22:03:30:DEBUG::calc CPUs force stopping.
22:03:37:DEBUG::in game to idle 7-4
22:03:37:INFO::TransitStateMachineFromIdle
22:03:38:INFO::TransitStateMachineFromPlayInGame
22:03:38:DEBUG::turn time out - turns - 11
22:03:38:DEBUG::Send hsplay timeout !
22:03:38:DEBUG::calc CPUs force stopping.
22:03:45:DEBUG::in game to idle 7-4
22:03:45:INFO::TransitStateMachineFromIdle
22:03:46:INFO::TransitStateMachineFromPlayInGame
22:03:46:DEBUG::turn time out - turns - 11
22:03:46:DEBUG::Send hsplay timeout !
22:03:46:DEBUG::calc CPUs force stopping.
The repeated commands indicate that HearthRanger attempts to use the Starship to attack, ignoring the fact that the minion is restricted from acting on the turn it is summoned. This causes the turn timer to expire repeatedly, leading to forced CPU stops.
Steps to Reproduce:
Use HearthRanger in a game where Starship components are assembled and launched.
Once the Starship is launched, observe that HearthRanger tries to attack with it immediately, causing an infinite loop.
The bot fails to progress as it keeps attempting to use the Starship to attack during the same turn.
Expected Behavior: The bot should recognize that a newly launched Starship cannot attack on the turn it is summoned and should wait until the next turn before attempting any actions with it.
Environment:
Hearthstone expansion: "The Great Dark Beyond"
HearthRanger version: [Specify your current version if known]
System: Windows 11
Please address this issue in a future update. Thank you!
The repeated commands indicate that HearthRanger attempts to use the Starship to attack, ignoring the fact that the minion is restricted from acting on the turn it is summoned. This causes the turn timer to expire repeatedly, leading to forced CPU stops.
Steps to Reproduce:
Use HearthRanger in a game where Starship components are assembled and launched.
Once the Starship is launched, observe that HearthRanger tries to attack with it immediately, causing an infinite loop.
The bot fails to progress as it keeps attempting to use the Starship to attack during the same turn.
Expected Behavior: The bot should recognize that a newly launched Starship cannot attack on the turn it is summoned and should wait until the next turn before attempting any actions with it.
Environment:
Hearthstone expansion: "The Great Dark Beyond"
HearthRanger version: [Specify your current version if known]
System: Windows 11
Please address this issue in a future update. Thank you!
