feat(lua): additional, mostly creature class family, bindings #3170
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
SUMMARY: Infrastructure "A lot of creature class family functions and members exposed to Lua"
Purpose of change
Building on top of #2216, a whole bunch of functions for creature, character, avatar and NPC are now exposed to Lua, with other bindings in order for the aforementioned bindings to work, and a few other miscellaneous bindings.
Describe the solution
In order to bind most of the creature class family's methods and members to Lua, the types used/returned had to be bound to Lua first, which required additions to them, most of them covered by doc/LUA_SUPPORT.md. By using (mostly) regex, header files of the classes in question were formatted step-by-step so that it wouldn't be as tedious as doing it manually, however looking over the result was necessary sometimes. Preprocessor macros were made to make typing bindings manually less of a hassle when the regex processing didn't work.
Testing
Additional context
get_character_name
was replaced by a member of a class, therefore there may be some broken Lua mod(s) with the current state of the PR.