This is basic Lua. Did you search before posting?

BrotSagtMist wrote: ↑Tue Oct 10, 2023 12:11 am I does not depend.
Its two lines for less cpu usage. That is ALWAYS a profit.
Not adding it if you can is a harmful mindset.
You should be spanked.

I still beg to differ and call it a microoptimization. Sorry, not into spanking.

Whaaat? How can you be so wasteful when the fix to pull it to almost zero cpu is just adding two lines? It depends on what's going on in the background. If zero to nothing, it does not matter. If nothing to something and it's not CPU intensive, it does not matter. Etc. until you actually hit some p...

BrotSagtMist wrote: ↑Sat Oct 07, 2023 2:59 pm ^
Yea the check itself is fine.
But you can optimize how often it runs. Eg check if the mouse has actually moved before.

That sounds like microoptimization to me. This basic hover check is not CPU intensive at all.

https://www.lua.org/pil/16.html

See the explanation about colon functions here.

And your question is?

Yep, the generation is fine.

Your issue was that you were looping over `coin` using `for` and `#coin` length. But with gaps, your table could contain index 7, but the length would be e.g. just 5. So you would never come to coin index 7. I recommend using pairs to iterate. You former buggy code (main.lua, line 73): for i = 1, #c...

The subtraction was just an example for demonstration's sake, my actual game's callbacks are much more involved. Indeed, but the order of applying damages is really up to you and your model. By "universal" callback do you mean something like this approach? function collide(object, other) ...

Then post the complete code or the relevant parts of it.