You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/manuals/libraries.md
+3-10
Original file line number
Diff line number
Diff line change
@@ -105,19 +105,12 @@ Now the folders that you shared appear in the *Assets pane* and you can use ever
105
105
106
106
## Editing Files in Library Dependencies
107
107
108
-
Files in libraries cannot be saved.
109
-
You can make changes, and the editor will be able to build with those changes, which is useful for testing.
110
-
However, the file itself remains unchanged, and all modifications will be discarded when the file is closed.
108
+
Files in libraries cannot be saved. You can make changes, and the editor will be able to build with those changes, which is useful for testing. However, the file itself remains unchanged, and all modifications will be discarded when the file is closed.
111
109
112
-
If you want to make changes to library files, make sure to create your own fork of the library and make changes there.
113
-
Another option is to copy/paste the entire library folder into your project directory and use the local copy.
114
-
In this case, your local folder will shadow the original dependency, and the dependency link should be removed from `game.project`
110
+
If you want to make changes to library files, make sure to create your own fork of the library and make changes there. Another option is to copy/paste the entire library folder into your project directory and use the local copy. In this case, your local folder will shadow the original dependency, and the dependency link should be removed from `game.project`
115
111
(don’t forget to choose <kbd>Project ▸ Fetch Libraries</kbd> afterward).
116
112
117
-
`builtins` is also a library provided by the engine.
118
-
If you want to edit files there, make sure to copy them into your project and use those instead of the original `builtins` files.
119
-
For example, to modify `default.render_script`, copy both `/builtins/render/default.render` and `/builtins/render/default.render_script` into your project folder as `my_custom.render` and `my_custom.render_script`.
120
-
Then, update your local `my_custom.render` to reference the `my_custom.render_script` instead of the built-in one, and set your custom `my_custom.render` in `game.project` under the Render setting.
113
+
`builtins` is also a library provided by the engine. If you want to edit files there, make sure to copy them into your project and use those instead of the original `builtins` files. For example, to modify `default.render_script`, copy both `/builtins/render/default.render` and `/builtins/render/default.render_script` into your project folder as `my_custom.render` and `my_custom.render_script`. Then, update your local `my_custom.render` to reference the `my_custom.render_script` instead of the built-in one, and set your custom `my_custom.render` in `game.project` under the Render setting.
121
114
122
115
If you copy-paste a material and want to use it across all components of a certain type, it might be useful to use [per-project templates](/manuals/editor/#creating-new-project-files).
0 commit comments