Collision checking?  Do you mean making sure enemies never intersect?

If we keep the amount of enemies fairly low (under a hundred, probably), then you could just take a brute force method - randomly generate two numbers for X and Y coordinates, check those numbers against every other enemy's coordinates, then if the absolute difference is 7 or less, then either attempt select another random slot, or add/subtract the appropriate amount of numbers to get the enemies not to intersect.

Edit: You probably meant bullets - in that case, just use the same checks you did with variables, only because all of your data is in what is effectively a list, do the checks in a for loop.

Collision checking?  Do you mean making sure enemies never intersect?

If we keep the amount of enemies fairly low (under a hundred, probably), then you could just take a brute force method - randomly generate two numbers for X and Y coordinates, check those numbers against every other enemy's coordinates, then if the absolute difference is 7 or less, then either attempt select another random slot, or add/subtract the appropriate amount of numbers to get the enemies not to intersect.

Edit: You probably meant bullets - in that case, just use the same checks you did with variables, only because all of your data is in what is effectively a list, do the checks in a for loop.

So since my current check is If ((A-4<=X)and(A+4>=X))and(B=Y) i can just replace the variables I use for the enemy, with the loop, correct?

Ahh ! I used the code for the Pt-On() and it displays one of those like messed up sprite things when you do something wrong lol. I had to modify the variables a tad, and made sure that i fixed all of them properly but still it happens! 

And I'm about to create a topic for this, so I'll link that in an edit so we don't spam up this topic too much.

You can use the Bitmap function, but I think it's even slower because the routine is written by Texas Instruments and is not as optimized.

Also welcome here , sadly ztrumpet isn't around anymore so if you need more details from an Axe expert you might have to wait for someone else's answer.

Woah, necro! (sort of)

Welcome to the forums, tincopper2.

I'm not ztrumpet, but I can tell you that if you want to use 16x16 sprites in pure Axe, you'll have to use 4 8x8 sprites...that's the only way to do it without an Axiom or assembly coding. (or, as dj mentioned, you can use the bitmap command but that sucks if you want to get any kind of reasonable speed)

There are probably quite a few 16x16 sprite routines floating around in assembly, you could probably find one relatively easily (although if you want clipping that's a different story...)

Holy mackeral! Fast reply! Btw, thanks.

Oh nice

Note that the bitmap Y offset might be kinda weird (at least in my experience it's about 3 px off )

Edit: Never mind, that *shouldn't* be a problem

You'll want to do a tilemap. The tiles themselves are sprites.
For the sprites you'll want a sprite editor. There's a ton of those around here, take your pick
Tilemaps are kind of complicated if you're new to programming, but you can have a look around the tutorials and feel free to ask for help