As is expected with code that learning game programmers are writing, the formatting and structure of this project is horrendous. With no Lua prior experience I can tell most of these functions belong in Lua classes or modules, there are loops upon loops, variable naming is inconsistent and sometimes too obscure to mean anything, and it's a miracle when you run into a comment for the purpose of any functions that were written.
A branch should be created to attempt to move a majority of the logic into files (WITH COMMENTS ) that can be imported in the core overwrites that Valve looks for to define bot behavior.
The reason being that someone else could pick up the torch on these scripts going forward if I drop this side project.
The only things that must be taken into account is that specific files MUST live in the root directory of the project and those should also be documented in the README in that new branch for clarity.
As is expected with code that learning game programmers are writing, the formatting and structure of this project is horrendous. With no Lua prior experience I can tell most of these functions belong in Lua classes or modules, there are loops upon loops, variable naming is inconsistent and sometimes too obscure to mean anything, and it's a miracle when you run into a comment for the purpose of any functions that were written.
A branch should be created to attempt to move a majority of the logic into files (WITH COMMENTS ) that can be imported in the core overwrites that Valve looks for to define bot behavior.
The reason being that someone else could pick up the torch on these scripts going forward if I drop this side project.
The only things that must be taken into account is that specific files MUST live in the root directory of the project and those should also be documented in the README in that new branch for clarity.