@chucky831 you can do boxes[len(boxes)] = obj, means you need to give the next item in the array as the index. Here if there are 3 items already in boxes as an example, boxes[0], boxes[1] and boxes[2], then len(boxes) is equal to 3. and boxes[3] = obj will add the 4th item. or you use the len() function directly as I did at the beginning of my comment.

@Dave thanks a bunch!

Thanks. I was getting confused because you can go left to right first or up and down first. But whatever direction you pick first, you only do the second one once...

It’s getting there.

@Martin yes it was, thanks for the edit. The game works perfectly fine now!!

@Martin Thanks, will do in future.

testing

Not at all! You're approaching this problem from the right angle.

I found out why it was giving me an error. I misspelled a word in the code and I forgot a ","

Prettier I thought …
clear(blue)
for p = 1 to stars loop
circle(xx[p], yy[p], 2, 32, white, false)
repeat

It could be that I am wrong here: I just found out that the string I wanted to write is already cut off earlier:
I converted an array to a string. And the string has always a size of 1024 for bigger arrays.
My target is to write an array just like this into the file - being lazy - and then interpreting it during reading. So, now worries I just write it struct by struct, which are never > 1000 chars long.

The documentation needs a couple of updates, but this is an intended feature. You've done a great job there @spikey discovering the ins and outs. Expect help documentation to come which reflects this!

Very nicely done, great effect

Just checked, it does operate right to left (for both or and and), but it will always evaluate both sides regardless.

@Merc1973 don't apologise mate we're all here to help each other

@vinicity ...and there was a post https://fuzearena.com/forum/topic/470/using-multiple-render-effects about combining the effects.

Thanks for your kind words.
Keep safe, John

Sweet I have been following your progress on this game so I'll deffo take a look thanks man

@pianofire
Yes that's what I meant sorry.
The code would execute meaning the game would run but the sprite would not be removed (it was the player sprite as it happens) I had another action like print "aaa" and another (which escapes me) either side of the removesprite which would happen so I know it was getting to that code.

But if I decided OK it doesn't remove it so let's after the removesprite say do something else with the sprite then when hitting run it would error saying can't do that with a removed sprite.

So I resorted to moving it off screen instead.

I can and will recreate it tomorrow

@pianofire Thanks a lot! Exactly what I needed!

New texture added. wolfy-ceiling3 ID: XDXS2MND15