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!

@monkeee polished this up and added new maps, hp, reload and ui. I made it a new project because it got a bit long and complicated. I liked how simple the original one was.
Here's the download code:
S5L43MNDHB

Preview:

I gave this a look and I found an easy improvement as it is now is to increase the node capacity to around 9 or 10. It seems to perform much better than 3. After that it starts to bottleneck somewhere else.

Thank you both for your inputs. This means to me I am close to the borders, where the CPU/Interpreter forgives me quick solutions ;-). I think I could get along, if I review my checks, but if I want to get further with more sprites/objects, I will have to review my code and apply optimizations.

thanks soo much for this i use it to know objects dimensions for my projects well i use it to find the values i need, i don't use the code in my project

Ok i will check that out and test if i can do the bullet board (enemy turn) and the dialog/menu(player turn) with that but idk if i could just colide with a location lets say like corners x 50 and 100 and y 4 and 36 so i could collide with the location itself instead of the box()

@waldron i appreciate that guidance. I will do it like this.

I think you want something like:

setSpriteSpeed (plr,100*c.lx,-100*c.ly)

Though 100 seems fast, but is in line with what you had.

I tend to do my collisions the same and something like this:

for i = 0 to len(enemy) loop
col = detectenemycollision(enemy[i],player)
if col then
..collission happened, do something..
endif
repeat

Not sure if that'll help at all/