Oh ok that would explain it. I got it to work though so no worries thanks for the reply

Thank you :)

I think I saw you found your way into the Discord server. But for posterity here is an alternate invite link that should never expire: https://discord.gg/MfAEAkhG47

~Max

@mozipha

This is what I ended up going with it’s a little messy but I’ll put it here incase it’s helpful to anyone else. I’m working with sprites so I believe I can’t just sprite[0] = sprite[1]. If you can I haven’t been able to get it to work.
Thanks again.

function remove(ref o_array, index) array n_array[len(o_array) - 1] var offset = 0 var i for i = 0 to len(n_array) loop if i == index then offset = 1 endif n_array = createSprite() setSpriteImage( n_array[i], block_image ) setSpritelocation( n_array[i], getSpriteLocation( o_array[ i + offset ] ).x, getSpriteLocation( o_array[ i + offset ] ).y + ( offset *8 )) setSpritecolor( n_array[i], getSpriteColor( o_array[ i + offset ] ) ) removeSprite( o_array[i] ) repeat removeSprite(o_array[ len(o_array) - 1 ] ) return n_array

Can you give more specific information? The project download codes and assets in question?

I'm not aware of any built-in way to do that. For most array processing functions, if you want them, it's up to you to code them.

It's not directly related to your question, but one trick I've found that can be useful in some circumstances, particularly when dealing with structs, is to convert the array/struct into a string using str() and then process it with the string functions. It's particularly relevant to structs because it allows you to search for a field within the struct, which can't normally be done. The limitation on this, though, is that str() will throw an error if the struct contains anything such as a handle that can't be converted to a string.

@stevezx81 And I don't know how to code a Sonic physics engine, and that would actually be the best way to see them in action.

Normally what I do is a bunch of ‘if player x position < 0 then player xspeed = - player xspeed
If player x > screenwidth then player xspeed = - player xspeed
If player y position < 0 then player y speed = - player y speed
If player y position > screen height then player y speed = - player y speed.’

This has the effect of bouncing you off walls. To stop dead, you’d put speed = 0, and laso probably shift the players position a bit to put them back jnside the screen if they go over by a few pixels.

There’s a clever example in the tutorials using clamp() which looks neater. It’s at https://fuzearena.com/help/view/Sprite Game - scroll down to the part ‘creating boundaries’

You can also use maps, probably, and use the map collision. All sorts of ways to skin a cat. Hope this helps!

So you need to keep track of what state the game is in e.g. title screen, game screen, exit screen then you can respond to the controls in different ways depending what the state is. There is a simple example in this post https://fuzearena.com/forum/topic/852/exit-the-game-loop-back-to-title-screen/2?_=1683130244723

All that setTimer does is tell Fuze to call a user function after a set time. That user function may of course contain anything you want, like loadMap().

The same goes for the other example. You can put whatever inside the delayed functions...

@gothon Thank you so much! This will be very useful for coding the kart AI. I'll be using a 2D vector for the angle from now on.

@toxibunny Nah, it got rejected (I thought submitting it would work). I didn't recover it :(.

@skullo I'm glad you found it funny, I really like it when my dumb jokes make someone laugh. I was considering adding unlockable lore considering how fun the high scores were for me to play and code (although I don't know if my weird sense of humor crosses the line).

You appear you have a loop before the loop where the sprite gets drawn, if the above loop blocks that loop then the sprite will never be drawn

That looks neat!