You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been looking at this rulesheet while looking for bugs in a prover optimization (this is one of the few places it's been screwing up).
The rulesheet currently allows for moves where the queen's destination and the arrow's location are the same. Presumably this is due to the toroidal nature of the board. We should be able to prohibit these, at a coarse level, at least.
There may be separate issues generally related to the recursion happening on a board where it can continue to loop indefinitely.
The text was updated successfully, but these errors were encountered:
I suspect the "bug" for the prover optimization is actually just this recursion issue popping up: ggp-org/ggp-base#6 This is a bug in the ProverStateMachine and not the rulesheet.
I still need to fix the shoot-onto-your-own-square issue, though I may just wait until I rewrite Amazons (if moving and shooting are separated into different turns, the game should be much faster to simulate).
I've been looking at this rulesheet while looking for bugs in a prover optimization (this is one of the few places it's been screwing up).
The rulesheet currently allows for moves where the queen's destination and the arrow's location are the same. Presumably this is due to the toroidal nature of the board. We should be able to prohibit these, at a coarse level, at least.
There may be separate issues generally related to the recursion happening on a board where it can continue to loop indefinitely.
The text was updated successfully, but these errors were encountered: