@Ashley, I agree totally with that article, it has actually helped me not be so picky in my code and just finish the project, but in this case I am not having those kinds of issues. I basically have a function that is constantly called, and 99% of the time no condition is met so I am calling it for no reason, in effect Memory Leak. I would think that could eventually drag down performance, like not killing sprites that go off screen, they will build up and eventually cause problems.
@keepee that is in effect what I am doing, but in stead of isPlayer within X/Y I just see if overlap. Not sure I see how between X/Y would really be different then onoverlap, can you explain a bit more? thank you.