Further tests on the current state of array indexing shows something odd.
Even though we now know that the current build has a bug that means "writing" to an array uses 1-indexing, and "reading" from an array uses 0-indexing, we can't use that knowledge in the meantime to fudge a workaround because the first index seems to be unreadable.
+ Array:Set Size to 8x8x4
+ Array:Set Index (5,5,1) to 91
+ Array:Set Index (5,5,2) to 92
+ Array:Set Index (5,5,3) to 93
+ Array:Set Index (5,5,4) to 94
creates the array and sets those 4 values in the separate Z indexes.
Now looking for them in (5,5,n) won't work in the current build, as we know, but we should find them in (4,4,n).
But if we look in the those 4,4,Z indexes, we find the values 0,92,93,94
The first index is never retrievable.
This may be fixed as a consequence of fixing the original bug, but I would like to ask the Devs to check the array functions carefully before the next release, as this may be a new bug.