Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command stepping #12240

Open
MiniaczQ opened this issue Mar 1, 2024 · 0 comments
Open

Command stepping #12240

MiniaczQ opened this issue Mar 1, 2024 · 0 comments
Labels
A-ECS Entities, components, systems, and events C-Feature A new feature, making something new possible

Comments

@MiniaczQ
Copy link
Contributor

MiniaczQ commented Mar 1, 2024

What problem does this solve or what need does it fill?

Currently only systems can be stepped through.
With the arrival of hooks the command ecosystem will be a lot more active and prone to infinite recursion through self-queuing commands.
While this cannot be easily prevented, tooling can be provided to debug the issue.

What solution would you like?

Ability to step through queued commands during flush_commands execution.
Human-readable command identifiers.
Similarly to systems, ability to always skip/run certain command types.

What alternative(s) have you considered?

None

Additional context

None

@MiniaczQ MiniaczQ added C-Feature A new feature, making something new possible S-Needs-Triage This issue needs to be labelled labels Mar 1, 2024
@TrialDragon TrialDragon added A-ECS Entities, components, systems, and events and removed S-Needs-Triage This issue needs to be labelled labels Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-ECS Entities, components, systems, and events C-Feature A new feature, making something new possible
Projects
None yet
Development

No branches or pull requests

2 participants