Skip to content

[FEATURE] Define specifications of editor #589

@Miou-zora

Description

@Miou-zora

Problem Statement

For now, there is no way to easily visualize data that we put in a game like collision boxes, player position, rendered game with spectator view.

Proposed Solution

As an Editor is a very big part, specifications should be made to define step to do to have a game editor.

Use Cases

Describe how this feature would be used and who would benefit from it:

  • Use case 1: See some space in the game that is not viewable when playing game.
  • Use case 2: Debug positions of stuffs in the scene.
  • Use case 3: Fast setup of project
  • Use case 4: See alive entities
  • Use case 5: See systems scheduling
  • Use case 6: Have an integrated profiler
  • Use case 7: Have the whole development process inside
  • Use case 8: Check values of components
  • Use case 9: Manage rendering pipelines

Impact

Describe the potential impact of this feature:

Implementation Details (optional)

If you have ideas on how this could be implemented, please share them here.

You can look at:

Additional Context

Add any other context, screenshots, mockups, or examples about the feature request here.

Related Issues

List any related issues or PRs:

Metadata

Metadata

Assignees

Labels

criticalVery important PR that requires @CoreTeam approvalenhancementNew feature or requesthelp wantedExtra attention is needed

Type

No type

Projects

Status

Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions