-
Notifications
You must be signed in to change notification settings - Fork 44
Adds Script System for adding paths to redscript compilation (REDmod compatible) #21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I have some remarks and questions 🏃
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few more remarks 🏃
Co-authored-by: Octavian Dima <3403191+WopsS@users.noreply.github.com>
Will this require an increment to the SDK version? Trying to figure out to specify that this functionality is needed on the plugin-side. |
We increase the API version, but still supports 0.3.0 since it is backwards compatible. |
Before merging this, we need a PR for the SDK. |
Co-authored-by: Octavian Dima <3403191+WopsS@users.noreply.github.com>
Paths can be added via the
Scripts::Add
function in the sdk, duringLoad
:Paths can either directories or files (handled by
scc
), relative to the plugin's folder, or absolute (mainly for testing/development).This will also force script compilation when REDmods are enabled, which will cause double-compilation if cybercmd is installed - cybercmd is no longer needed for this scenario.