06-11-2021, 12:59 PM
(This post was last modified: 06-11-2021, 01:01 PM by slimy_asparagus.)
To be honest this is a rephrase of Do a non-decision before a decision. However I have now done my homework.
My current code has 941 lines of code. I have stripped it down as far as I can go and still reproduce my current issue. I have attached the cut-down code (307 lines) and a trial.
The issue is the value of the top piece at space 1. It should be 0 but the test ludeme dialogue and the behaviour show it to be 1. The trial shows it was trying to set it to 0.
The clincher is that when I change the code to use the state rather than the value it works. This does not offer a work around, because I really need state for something else in the full code.
The specific bit of code which is failing is
My current code has 941 lines of code. I have stripped it down as far as I can go and still reproduce my current issue. I have attached the cut-down code (307 lines) and a trial.
The issue is the value of the top piece at space 1. It should be 0 but the test ludeme dialogue and the behaviour show it to be 1. The trial shows it was trying to set it to 0.
Code:
.....[SetValue:type=Cell,to=1,level=1,value=0]........
The clincher is that when I change the code to use the state rather than the value it works. This does not offer a work around, because I really need state for something else in the full code.
The specific bit of code which is failing is
Code:
(do
("UnsetDiagonalGrappleFlag" "F")
next:("CoreMoves")
)