Callbacks? In my BASIC?! I manage all sprite collision through a single object operating on plain arrays. When two things touch, their "onHit" method is called. Anything not actively being controlled by a player or AI doesn't require an update! THE SAVINGS!!!

Peeps might recognize this technique from all my physics demos. The difference this time is that behaviors are coupled to sprites - physics calls SPOFS directly. This is in contrast to each entity polling physics for a position in an update method.

A problem that I see with the code is that only the first collision will be detected(From my experience if 3 sprites overlap, then SPHITSP will return the sprite with the lowest management number.) For example, for sprites with management number 1,2,3, the collision detected would be (1,2), (2,1) and (3,1). To solve that problem you need to use a loop to call SPHITSP() without arguments.

Example: SP%=_.SP%[I%] IF SP%>-1 THEN HIT%=SPHITSP(SP%) WHILE 1 IF HIT%==-1 THEN BREAK ...'Code inside IF HIT%>-1 THEN HIT%=SPHITSP() WEND ENDIF

@Raimondz: I was aware that could happen, but I didn't realize I could just keep calling SPHIT(). By post-poning collision until all sprites are resolved, I at least guarantee some hit happens to each. What I'm curious about is how I would manage the memory around multiple hits. Each call to 'Hit.bind' allocates memory for one collision. How many collisions do I really need to preallocate?