LÖVE

I'm making a simple game and I'll have a few types of enemies with slightly different properties (amount of health, damage, etc). How are people handling this? I can think of two options: having a number of tables like enemyHealth, enemyDamage etc that store these values or to go with classes and inheritance.

I've been leaning towards using tables to keep it simple but am all ears for better approaches.

Thanks!

If you use tables, I'd use it in the other direction: instead of having a bunch of tables, I'd have a table enemies, containing tables of the form {health = ..., damage = ..., ...}. Otherwise it tends to get unwieldy if the enemies need to be reordered (e.g. because of enemies being deleted).

Thanks - that makes a lot of sense and keeps it much more organized. I'm leaning towards this sense my game is so simple and I think I can get away without using classes etc.

dandypants wrote:Thanks - that makes a lot of sense and keeps it much more organized. I'm leaning towards this sense my game is so simple and I think I can get away without using classes etc.

there are no classes or inheritance in Lua. What Robin outlined is close to those concepts already, and most likely the way to go.

You could make something similar to prototype based OO, where you have a table describing every enemy type, and then for each enemy you reference a single enemy type, which you can then use to look up info about the enemy.

Also, about inheritance, you can add inheritance with three lines of code if you want to, like this:
(not tested and typed from a phone)

T-Bone wrote:You could make something similar to prototype based OO, where you have a table describing every enemy type, and then for each enemy you reference a single enemy type, which you can then use to look up info about the enemy.

Also, about inheritance, you can add inheritance with three lines of code if you want to, like this:

Code: Select all

function inherit(parent, child)
    setmetatable(child, {__index = parent})
end

(not tested and typed from a phone)

That's pretty much my class approach in every project.