Make GamepadLobby a built-in type #3245
Labels
A-Input
Player input via keyboard, mouse, gamepad, and more
C-Usability
A targeted quality-of-life change that makes Bevy easier to use
D-Trivial
Nice and easy! A great choice to get started with Bevy
What problem does this solve or what need does it fill?
As shown in https://github.com/bevyengine/bevy/blob/main/examples/input/gamepad_input.rs, we need to track when gamepads connect.
The
GamepadLobby
shown there is a common and useful abstraction: external crates should be able to coordinate around its existence (and end users shouldn't have to copy boilerplate from examples).What solution would you like?
Make
GamepadLobby
a built-in Bevy type and export it.Add
connection_system
from that example toCoreStage::PreUpdate
as part of the appropriate plugin.Update the examples to use this new type.
The text was updated successfully, but these errors were encountered: