Custom types were more relevant in the early Godot 3.x days,
but nowadays, script classes should be preferred whenever possible
(i.e. in any non-C# language).
This follows the documentation writing guidelines, specifically
the "When to refer to a specific Godot version" section.
This also removes warning blocks for a known issue that was resolved in Godot 4.5.
* 🐞 fix(plugins): fix syntax errors
Correct the syntax errors in the plugin development section, specifically by modifying 'EditorInterface' to 'EditorInterface.Singleton' in the C# portion. It is imperative to utilize the singleton pattern here to ensure the plugin successfully compiles.
* 🐞 fix(different): ADD exceptions
Provide explanations for Singleton exceptions of `EditorInterface`
- Add screenshots
- Document reading and writing settings
- Document manually editing project.godot
- Note that most settings are changed in different
classes at runtime
The space in "some times" is a mistake and should be removed as it should be one word, not two (as can be seen when it is used correctly further down the page at the start of the, "Running one-off scripts using EditorScript" section).
This allows users to leave comments on pages that don't have
`:allow_comments: False` somewhere in the page's source.
Both manual and class reference pages can receive comments.
Index pages cannot have comments, as discussion should occur on "leaf" pages.
GitHub Discussions is used as a backend on the same repository. This means
that Discussions *must* be enabled on godotengine/godot-docs before this
commit is merged to `master`. Users can choose to use the "Custom" watch
mode if they don't want to get notifications for discussion updates,
but still get notifications for issue and pull request updates.
User comments are intended to be used for the following purposes:
- Add a clarification or correct something in the documentation,
without having to open a pull request. Contributors are encouraged to
take a look at discussions from time to time, and see if there's information
worth incorporating in the pages themselves. Don't forget to reply to
the comment when doing so :)
- Mention a workaround for a common issue.
- Link to useful third-party resources that are relevant to the current page,
such as tutorials or add-ons.
User comments should *not* be used for technical support. Other community
platforms should be used for that.
Page-to-discussion matching is done using the `pagename` Sphinx variable,
which is independent of the Godot version and documentation language.
Being independent of the Godot version allows keeping old comments
when the Godot version changes, while also allowing users from `/stable`
and `/4.1` to "see" each other in discussions.
See https://giscus.app for more information.
EditorScript is useful for one-off operations such as:
- Use as a playground for GDScript or C# scripting without
having to run a project.
- Scale all light nodes in the currently edited scene.
- Replace nodes that were copy-pasted with scene instances.
