Edgar Simo-Serra

Initial implementation is done. Seems to work well. Only a single pers atm, going to keep this open until we add a decent amount.

Still room for more, but good enough for now at least.

Yes, point defenses are planned, but I want to finish and merge the `fleets` branch first before working on that. Although I may take a hiatus to work on missions...

I think I got everything except the primitive shapes + the aiming helper.

> Also how about some categories of "high scores" - depending on what route the player takes. Could be high scores for e.g. number of ships destroyed, number of jumps...

> EDIT: Also, I'd like to add that this whole idea of "player growth" doesn't need to be present in Naev to begin with. Naev isn't an RPG as much...

> > If they all are equal, this basically makes it so that no pilot can really excel with respect to others (unless you change the AI or something), and...

Apparently we would have to either generate or create a file like https://github.com/mpeterv/luacheck/blob/master/src/luacheck/builtin_standards/love.lua . Maybe it would be possible to generate it from the luadocs stuff? That way would be...

Ideally we would want to generate all the functions and stuff from our documentation (so we don't duplicate efforts). Most of the time we also use `@luatparam` and `@luatreturn`, so...

> Pro: although it's an error to access gfx functions from missions (for instance), we probably don't care about the linter catching that and would be happier with a simpler...