Add project file changes in preparation for Rojo 7.4.0#85
Open
Dekkonot wants to merge 2 commits intorojo-rbx:masterfrom
Open
Add project file changes in preparation for Rojo 7.4.0#85Dekkonot wants to merge 2 commits intorojo-rbx:masterfrom
Dekkonot wants to merge 2 commits intorojo-rbx:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In Rojo 7.4.0, whenever that releases, we have a new field called
emitLegacyScriptsin project files. Also, we've allowed Terrain to be included in a project file without a$classNamefield since it's basically a service in the same vein asStarterPlayerScriptsandStarterCharacterScripts.This just adds those changes to the schema for project files.