Enable registering time runners of different steps and schedules by Rabbival · Pull Request #15 · Multirious/bevy_time_runner

Rabbival · 2026-01-09T07:26:23Z

Feature

Previously, bevy_time_runner systems only support running in the default time context ().
This PR adds support to register systems in arbitary time context to support some cases where running in non-default context is necessary, such as, playing animation in Fixed time which is required to be in sync with physic engines.

Notable Changes

TimeRunnerPlugin which now uses TimeRunnerSystemsPlugin<()> by default.
TimeRunner is always expected to have the TimeContext<TimeCtx> marker component.
TimeContext<TimeCtx> is automatically inserted to children of TimeRunner.
Add feature debug. This adds TimeRunnerDebugPlugin which logs warnings on missing TimeContext<TimeCtx> marker component when enabled.

Detailed Changes

Add TimeRunnerSystemsPlugin<TimeCtx = ()>
Add TimeContext<TimeCtx> marker component.
Add Tagging to TimeRunnerSet (Breaking)
Add tag_time_runner_children_with_context system.
When debug feature is enabled, an "on add" hook is registered to TimeRunner
Add TimeRunnerDebugPlugin
Add TimeRunnerDebugInfo resource
Add TimeRunnerPlugin::enable_debug field, true by default (Breaking)
TimeRunnerPlugin automatically adds TimeRunnerSystemsPlugin::<()> when is not added.
TimeRunnerPlugin automatically adds TimeRunnerDebugPlugin::default() when is not added and enable_debug is true.

These systems now expected TimeCtx generic and modified parameter (Breaking)

tag_time_runner_children_with_context
tick_time_runner_system
time_runner_system

Dependency

New debug feature which depends on bevy_log

Internal

Updated all tests
Add time_runner_with_no_time_steps_warning test

* Time runners will now determine the time according to which they should be ticked (for example, Fixed) * Therefore, the general schedule on which their ticking systems would run can be configured (would make no sense to tick fixed timers on PostUpdate) * This does mean that one has to register these as separate plugins * The previous configuration (default time on PostUpdate) is registered by default

…nnerPlugin

to make up for the fact time runners are now generic

Multirious · 2026-01-25T08:11:38Z

IIRC, this is done prior bevy 0.18 so I'll rerun CI just to make sure.

This reverts commit 19c3d97, reversing changes made to fcb9b21.

This reverts commit b5e62eb.

Multirious · 2026-01-25T10:31:29Z

Sign in to view

-pub struct TimeRunnerPlugin {
+pub struct TimeRunnerRegistrationPlugin<TimeStep = ()>
+where
+    TimeStep: Default + Send + Sync + 'static,


Originally, the generic type in Time only requires Default. https://docs.rs/bevy/latest/bevy/prelude/struct.Time.html

We might need to make the requirements the same. (This also applies to other part of the changes)

It does, but the original time is a Resource and not a component

Multirious · 2026-01-25T10:32:53Z


-/// Add [`time_runner_system`]
-/// Registers [`TimeRunner`]
+/// Add [`time_runner_system on schedule`]


This break doc links. Should probably be

Add [`time_runner_system`] on schedule

Or maybe

Add [`time_runner_system::<TimeStep>`] on schedule

?

Changed to Add [time_runner_system::] on schedule

Multirious · 2026-01-25T10:35:43Z

    fn default() -> Self {
        TimeRunnerPlugin {
-            schedule: PostUpdate.intern(),
+            default_time_schedule: PostUpdate.intern(),


I think renaming is not necessary here, since by Plugin documentation, TimeRunnerPlugin should already be known as default configuration. This only adds additional breaking changes.

Multirious · 2026-01-25T10:42:58Z

 #[derive(Debug, Clone, PartialEq, Component)]
 #[cfg_attr(feature = "bevy_reflect", derive(Reflect))]
 #[cfg_attr(feature = "bevy_reflect", reflect(Component))]
+#[require(TimeStepMarker<()>)]


I think this does basically nothing?

Multirious · 2026-01-25T10:43:22Z

    repeat: Option<(Repeat, RepeatStyle)>,
 }

+/// A marker component attached to all TimeRunners no matter their TimeStep, for ease of querying


This documents likely out-dated here

It is, good spot

…fault This commit adds `enable_debug` field `TimeRunnerPlugin` which is a breaking change.

Generic time steps extra

Rabbival added 7 commits January 9, 2026 09:26

fix failing tests

016e9ed

make reflect(ignore) only active when reflect feature is enabled

1b8573d

add default timestep for syntactic sugar

2f082c6

expose TimerRunner<()> schedule that'll be registered with the TimeRu…

acc7083

…nnerPlugin

fix cfg feature

811fa6b

add a marker component for ease of querying

fcb9b21

to make up for the fact time runners are now generic

Multirious and others added 6 commits January 25, 2026 15:39

Merge branch 'main' into generic_time_steps

19c3d97

Revert "Merge branch 'main' into generic_time_steps"

b5e62eb

This reverts commit 19c3d97, reversing changes made to fcb9b21.

separate time step marker from time runner

f7ff9fb

fix comments

0e73005

remove redundancies

c6a1f81

Reapply "Merge branch 'main' into generic_time_steps"

4246078

This reverts commit b5e62eb.

Multirious requested changes Jan 25, 2026

View reviewed changes

Rabbival and others added 15 commits January 25, 2026 14:06

apply tweaks requested in pr

2023d10

attach TimeStepMarker::<()>::default() on tests

387ff01

Clippy fix

19c2a43

Docs fix

cc0ce9e

Add default debug feature that has bevy_log dependency

de10484

Update Cargo.lock

0e8e276

TimeRunnerDebugPlugin and TimeRunnerDebugInfo

6ecc1fc

on_time_runner_added hook impl

94df64d

time_runner_with_no_time_steps_warning test

2916e2a

[BREAKING] Make TimeRunnerPlugin adds TimeRunnerDebugPlugin by de…

f347e5d

…fault This commit adds `enable_debug` field `TimeRunnerPlugin` which is a breaking change.

Check for TimeRunnerSystemsPlugin<()> before adding it

08cbb9a

Merge pull request #18 from Multirious/generic_time_steps_extra

2230e3a

Generic time steps extra

renames

9e381ca

automatically tag time runner children with TimeContext

c91e171

add change log

4e25449

Rabbival and others added 10 commits February 1, 2026 17:29

fix feature tags

2747614

fix feature tags warning

d77eca4

Update lib.rs

80e329e

remove clone requirement from TimeCtx

d8aa22a

register TimeRunnerSet::Tagging,

82f0789

fix tag_time_runner_children_with_context query

d7544fe

update change log

232c802

Update CHANGELOG.md

a8502b3

Update CHANGELOG.md

718c1e1

Update CHANGELOG.md

6d21a03

Multirious approved these changes Feb 2, 2026

View reviewed changes

Multirious merged commit e3f116b into main Feb 2, 2026
3 checks passed

Multirious mentioned this pull request Mar 3, 2026

Allow Use And Registration of Generic Time Contexts Multirious/bevy_tween#78

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Enable registering time runners of different steps and schedules#15

Enable registering time runners of different steps and schedules#15
Multirious merged 38 commits intomainfrom
generic_time_steps

Rabbival commented Jan 9, 2026 •

edited by Multirious

Loading

Uh oh!

Multirious commented Jan 25, 2026

Uh oh!

Multirious Jan 25, 2026

Uh oh!

Rabbival Jan 25, 2026

Uh oh!

This comment was marked as outdated.

Uh oh!

Multirious Jan 25, 2026

Uh oh!

Rabbival Jan 25, 2026

Uh oh!

Multirious Jan 25, 2026

Uh oh!

Rabbival Jan 25, 2026

Uh oh!

Multirious Jan 25, 2026

Uh oh!

Rabbival Jan 25, 2026

Uh oh!

Multirious Jan 25, 2026

Uh oh!

Rabbival Jan 25, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

Rabbival commented Jan 9, 2026 • edited by Multirious Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Feature

Notable Changes

Detailed Changes

Dependency

Internal

Uh oh!

Multirious commented Jan 25, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

This comment was marked as outdated.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Rabbival commented Jan 9, 2026 •

edited by Multirious

Loading