ID:1447881
 
(See the best response by Kaiochao.)
Code:
N/A


Problem description:

I don't have a piece of programming that I'm having a problem with. The problem is there a correct way(more efficient) for a better lack of word to program a projectile system. For example: Does the bump need to be called each time for every single projectile attack? If not, how can a proc be programmed to alleviate having a bump proc after/before every technique?
Best response
What's wrong with Bump()? It does nothing by default, so it doesn't hurt performance much by itself.

For projectiles to interact with objects/enemies, they require an event to fire when the interaction happens, such as on collision. You can't have a collision event without a collision event, basically. What you're doing in the event is the important part.

Of course you don't require Bump(). You can have non-dense projectiles that check obounds() after every movement. It's still collision detection, though, and it's called every step instead of when the projectile hits something.
Okay, Thanks.