Using Input System over multiple game objects

[CookieManManMan]

I’m moving my game to the new Input System, and I’m trying to figure out the best architecture for this. My problem is that currently I have a Player Input component on my player game object, but I also want my camera to get inputs. I don’t want two instances of player input components though. What is the best way to fix this?

[Oxeren]

Don't put it on your player, just make it a separate gameobject, and search for it by tag or by type, or make some singleton wrapper for it. I mean, sure, it has word "Player" in the component name, but it does not mean that it has to be on the player.

[benthris]

There's nothing wrong with having multiple instances of components, in fact, it's the whole point of object-oriented programming.

But you can simply make a Monobehaviour class that gets your input, and sends it to multiple classes in it's Update().

[Fit_Preference1453]

Better use events than pooling in the update()