💡📝H. G. Muller wrote on Sat, Jan 15, 2022 01:30 PM UTC:
This error is weird: the error message obviously comes from the GAME code used to automate the preset, from the move parser. But it seems thise is called in an unexpected context: Game Courier tries to feed the game history to the code in the Post-Move sections twice. And the second time the position has already been changed from the initial one to some weird one, which indeed has a Z on g4.
For debugging I added a statement
printr $space
at the end of the Pre-Game section. When I then use the preset in Play mode, and play the given game, the page that complains about the error contains two dumps of the $space array. The first is the initial position (as expected), but the second is
Array
(
[a12] => d
[b12] => l
[c12] => u
[d12] => z
[e12] => o
[f12] => q
[g12] => k
[h12] => o
[i12] => z
[j12] => u
[k12] => l
[l12] => d
[a11] => r
[b11] => m
[c11] => n
[d11] => b
[e11] => a
[f11] => y
[g11] => y
[h11] => a
[i11] => b
[j11] => n
[k11] => m
[l11] => r
[a10] => x
[b10] => i
[c10] => e
[d10] => g
[e10] => s
[f10] => c
[g10] => c
[h10] => s
[i10] => g
[j10] => e
[k10] => i
[l10] => x
[a9] => p
[b9] => p
[c9] => p
[d9] => p
[e9] => p
[f9] => p
[g9] => @
[h9] => p
[i9] => p
[j9] => p
[k9] => p
[l9] => p
[a8] => @
[b8] => @
[c8] => @
[d8] => @
[e8] => @
[f8] => @
[g8] => @
[h8] => @
[i8] => @
[j8] => @
[k8] => @
[l8] => @
[a7] => @
[b7] => @
[c7] => @
[d7] => @
[e7] => @
[f7] => @
[g7] => p
[h7] => @
[i7] => @
[j7] => @
[k7] => @
[l7] => @
[a6] => @
[b6] => @
[c6] => P
[d6] => @
[e6] => @
[f6] => @
[g6] => P
[h6] => @
[i6] => @
[j6] => @
[k6] => @
[l6] => @
[a5] => @
[b5] => @
[c5] => @
[d5] => @
[e5] => A
[f5] => P
[g5] => @
[h5] => @
[i5] => @
[j5] => @
[k5] => @
[l5] => @
[a4] => P
[b4] => P
[c4] => @
[d4] => P
[e4] => P
[f4] => @
[g4] => Z
[h4] => P
[i4] => P
[j4] => P
[k4] => P
[l4] => P
[a3] => X
[b3] => I
[c3] => E
[d3] => G
[e3] => S
[f3] => C
[g3] => C
[h3] => S
[i3] => G
[j3] => E
[k3] => I
[l3] => X
[a2] => R
[b2] => M
[c2] => N
[d2] => @
[e2] => A
[f2] => Y
[g2] => Y
[h2] => A
[i2] => B
[j2] => N
[k2] => M
[l2] => R
[a1] => D
[b1] => L
[c1] => U
[d1] => Z
[e1] => O
[f1] => Q
[g1] => K
[h1] => O
[i1] => @
[j1] => U
[k1] => L
[l1] => D
)
This is neither the initial nor the current position, although it does have some characteristics of the current position.
Perhaps Fergus can shed some light on how the Pre-Game section could be executed twice when entering a single move in Play mode.
This error is weird: the error message obviously comes from the GAME code used to automate the preset, from the move parser. But it seems thise is called in an unexpected context: Game Courier tries to feed the game history to the code in the Post-Move sections twice. And the second time the position has already been changed from the initial one to some weird one, which indeed has a Z on g4.
For debugging I added a statement
at the end of the Pre-Game section. When I then use the preset in Play mode, and play the given game, the page that complains about the error contains two dumps of the $space array. The first is the initial position (as expected), but the second is
Array
(
[a12] => d
[b12] => l
[c12] => u
[d12] => z
[e12] => o
[f12] => q
[g12] => k
[h12] => o
[i12] => z
[j12] => u
[k12] => l
[l12] => d
[a11] => r
[b11] => m
[c11] => n
[d11] => b
[e11] => a
[f11] => y
[g11] => y
[h11] => a
[i11] => b
[j11] => n
[k11] => m
[l11] => r
[a10] => x
[b10] => i
[c10] => e
[d10] => g
[e10] => s
[f10] => c
[g10] => c
[h10] => s
[i10] => g
[j10] => e
[k10] => i
[l10] => x
[a9] => p
[b9] => p
[c9] => p
[d9] => p
[e9] => p
[f9] => p
[g9] => @
[h9] => p
[i9] => p
[j9] => p
[k9] => p
[l9] => p
[a8] => @
[b8] => @
[c8] => @
[d8] => @
[e8] => @
[f8] => @
[g8] => @
[h8] => @
[i8] => @
[j8] => @
[k8] => @
[l8] => @
[a7] => @
[b7] => @
[c7] => @
[d7] => @
[e7] => @
[f7] => @
[g7] => p
[h7] => @
[i7] => @
[j7] => @
[k7] => @
[l7] => @
[a6] => @
[b6] => @
[c6] => P
[d6] => @
[e6] => @
[f6] => @
[g6] => P
[h6] => @
[i6] => @
[j6] => @
[k6] => @
[l6] => @
[a5] => @
[b5] => @
[c5] => @
[d5] => @
[e5] => A
[f5] => P
[g5] => @
[h5] => @
[i5] => @
[j5] => @
[k5] => @
[l5] => @
[a4] => P
[b4] => P
[c4] => @
[d4] => P
[e4] => P
[f4] => @
[g4] => Z
[h4] => P
[i4] => P
[j4] => P
[k4] => P
[l4] => P
[a3] => X
[b3] => I
[c3] => E
[d3] => G
[e3] => S
[f3] => C
[g3] => C
[h3] => S
[i3] => G
[j3] => E
[k3] => I
[l3] => X
[a2] => R
[b2] => M
[c2] => N
[d2] => @
[e2] => A
[f2] => Y
[g2] => Y
[h2] => A
[i2] => B
[j2] => N
[k2] => M
[l2] => R
[a1] => D
[b1] => L
[c1] => U
[d1] => Z
[e1] => O
[f1] => Q
[g1] => K
[h1] => O
[i1] => @
[j1] => U
[k1] => L
[l1] => D
)
This is neither the initial nor the current position, although it does have some characteristics of the current position.
Perhaps Fergus can shed some light on how the Pre-Game section could be executed twice when entering a single move in Play mode.