asumagic
commented
2 years ago This could be implemented as a LSP(+LSIF?) server implemented directly inside of the staging build.
The following features may be implemented:
- An official VS Code extension for modding and development.
- A Language Server for AngelScript, but still somewhat coupled to the engine (due to how includes, etc. are being handled). This would provide things like real time warnings and errors, autocompletion and basic refactors.
- Decent support for hooks? Jumping to definition could enumerate, say,
#blobs::spikes::onInit, so blobs could be shoved into a namespace. - Official infrastructure to allow documenting the engine interface. There would be various ways to do this, but preferably this should be something that can be contributed from kag-base.
- Possibly some support to define documentation for script functions.
- A Language Server for configuration files. This might not be too necessary, but would allow jumping to files, provide additional context as to how the file is being parsed, and allow some basic syntax coloration.
- Resolving paths using the
CFileMatcher(ctrl-clicking to any file e.g..pngfiles, etc.). - Providing utility to allow viewing game logs, rebuilding, etc. from a language client.
- An AngelScript and basic game console REPL.
- A Debug Adapter Protocol implementation to allow for mod debugging.
Technical challenges are:
- Implementing a SDK for the LSP in C++ because there is no great option to do so at the moment.
- Stability concerns because this is 100% going to repeatedly crash the game.
This would allow for quite a better modding experience, but would be time consuming.