Skip to content

Currently, stride has an issue: the Editor extension documentation is too limited. #3201

@bnwa9723

Description

@bnwa9723

main issues with stride:
The document limitations of the stride engine:
For example, if we want to develop a plugin, such as an extension compiler, the Stride documentation is too limited. For instance, the documentation for registering Add Component, custom components, registering menus, registering Inspector, registering Gizmo, and capturing SceneView mouse is too scarce. This limits our plugin to the game itself and prevents it from fully integrating into the game compiler. We suggest that the official team provide more extension documentation for the Editor.
Is stride really that bad? Is it really inferior to other engines?:
Compared to the Godot engine, there isn't much difference between stride and the Godot engine. The reason why Godot engine extension plugins are so simple is because they provide more extension documentation, which stride lacks. It's a major shortcoming that the engine has the capability but can't fully utilize it.
stride functionality and development
The official documentation should provide extensive extensions to facilitate plugin development, such as the terrain plugin. The official team only needs to improve stride, while we create plugins to provide better convenience and enhancements to stride.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-DocIssues related to documentation and XML comments

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions