so this is the way you have it stored:
{taken,x,y,piece}
taken is the 0th element in this so-called array.
To access the nth variable of the pth piece, you need to do this:
{p*4+n+L1}
p needs to be multiplied by four because each piece uses up 4 bytes of data in the array.

Hope that explains it

And I agree with Hayleia that a 64-byte array for representing the board would be handier. But that's your choice

It is caused by programs messing with the VAT (variable allocation table iirc). Make sure all hooks are off then do a RAM clear.
EDIT: and did you uninstall zStart on 2.55? REALLY uninstall? (as in, undo run on RAM clear)

Me too.

I can make this too, when thepenguin can give me the asm codes to use with Axe.

You guys no read other's posts? I accounted everything I said in the code I posted. Lol.
[sorry this is not meant rude, I'm just kind of surprised you had not seen it]
EDIT: quoting myself:

Ok I made your graphics routine slightly shorter, but your data needs to be restructured.

Code: [Select]

data structure:
-sprites:
[hexWPAWN]->Pic1PCS
[hexWBISHOP][hexWKNIGHT][hexWROOK][hexWQUEEN][hexWKING][continue here for the 6 black pieces]

-------

how the pieces are stored in L1:
{taken?(0 if still on the board),xpos,ypos,pieceno(0=pawn,1=bishop, just like the sprite arrangement, and no need for B/W pieces)}

-----
Now the big thing: drawing the stuff.

For(A,0,31)
  if {A*4+L1}=!0
    A>15->B
    pt-on(A*4+L1+1,A*4+L1+2,8*{A*4+L1+3}+Pic1PCS+48*B)     ;; the x and y positions might be a bit off. you should change this later on.
  end
end
I think that will do it

I lol'ed at the spoiler.
Critor, any news on the prototype?

If you got screenshots, send them to me!

edit: so I can make a promotional vid

To summarize hayleia's point: str, gdb, pic are not the same as the Basic str, pic, gdb.