Skip to content

Update bevy_remote client example: print and exit#23410

Merged
alice-i-cecile merged 2 commits intobevyengine:mainfrom
mockersf:update-bevy_remote-client-example
Mar 20, 2026
Merged

Update bevy_remote client example: print and exit#23410
alice-i-cecile merged 2 commits intobevyengine:mainfrom
mockersf:update-bevy_remote-client-example

Conversation

@mockersf
Copy link
Copy Markdown
Member

Objective

  • Small improvements to the bevy_remote client example

Solution

  • Don't use info! as a logger is not set, use println!
  • Send an AppExit::Success message from the client to the server once done

Testing

  • Ran the server and client examples: there are now things printed, and the server example exit with the client

Copy link
Copy Markdown
Contributor

@kfc35 kfc35 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked it out, looks good and does what it says it should

(As an aside, maybe we want to address this in a separate issue
2026-03-18T20:29:55.931911Z WARN bevy_remote::builtin_methods: Failed to serialize component bevy_time::time::Time<bevy_time::real::Real> for entity 9v0)

@kfc35 kfc35 added C-Examples An addition or correction to our examples A-Dev-Tools Tools used to debug Bevy applications. D-Straightforward Simple bug fixes and API improvements, docs, test and examples S-Needs-Review Needs reviewer attention (from anyone!) to move forward labels Mar 18, 2026
@alice-i-cecile alice-i-cecile added this pull request to the merge queue Mar 20, 2026
@alice-i-cecile alice-i-cecile added S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it and removed S-Needs-Review Needs reviewer attention (from anyone!) to move forward labels Mar 20, 2026
Merged via the queue into bevyengine:main with commit b61edbe Mar 20, 2026
49 checks passed
@kfc35 kfc35 mentioned this pull request Mar 26, 2026
splo pushed a commit to splo/bevy that referenced this pull request Mar 31, 2026
# Objective

- Small improvements to the bevy_remote client example

## Solution

- Don't use `info!` as a logger is not set, use `println!`
- Send an AppExit::Success message from the client to the server once
done

## Testing

- Ran the server and client examples: there are now things printed, and
the server example exit with the client
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-Dev-Tools Tools used to debug Bevy applications. C-Examples An addition or correction to our examples D-Straightforward Simple bug fixes and API improvements, docs, test and examples S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants