How convenient is the documentation (available at docs.neverlose.cc)?
For beginners, it is not convenient at all (from my POV). I migrated from Skeet’s docs to Neverlose’s docs and had some headache at first, but in the long run, I’m all good with it. I think it should have more examples and usages for the certain element you are trying to refer.
I would appreciate a lot if the Lua API from Skeet was followed as an example (not a copy).
Example:
Element
syntax
values in syntax
GetScreenSize
syntax: g_EngineClient.GetScreenSize()
returns: x, y
*usages:
size = g_EngineClient.GetScreenSize()
print size.x*
How convenient and complete is the scripting api itself? What functions and commands are we missing?
Every print() used on Neverlose’s API should automatically convert inputs to string to avoid error and for efficiency, mainly.
For functions, I think these should be considered:
- Allow Lua devs to hide certain menu elements.
- Allow Lua devs to add custom menu elements.
- Allow Lua devs to refer directly to CS:GO’s panorama API.
- Allow text input in menu.
How convenient is our built-in script editor? When writing scripts for neverlose, do you use our built-in editor or do you prefer to use an external code editor?
I don’t use Neverlose’s internal IDE as I’m used to using Visual Studio Code, however, I see it as a useful and unique feature that should be maintained. It is convenient, however, more features should be added (such as auto complete syntaxes)
How convenient and straight forward is it to work with scripts in the neverlose menu itself?
It is pretty straight forward when you get the hang of it, but as stated above, as a beginner, you will need to learn how to deal with documentation mistakes. At the release of Neverlose’s Lua API, I had a hard time as the documentation had invalid syntax examples (but I guess everything or the most part has been fixed).
teacher