How to assign inputs to a player controller?

UpsetChicken

I am making a multiplayer couch game where multiple players can join (pretty much like Smash Bros). On the character select screen there are 6 player slots, and I need that when a player press the A/Cross button, he joins in. However, I don't know how to make the game automatically recognize the input from a specific api(Xinput or Dinput) and assign the inputs to that player controller. Not sure how to go about this.

I can elaborate if someone someone finds this confusing.

kuligs2

Does this help? https://docs.godotengine.org/en/latest/tutorials/inputs/input_examples.html

You bind your inputs to actions -> Joycon button A -> join_action() -> then you hook up the input events to do what you want.

func _physics_process(delta):
	if Input.is_action_pressed("join_action"):
		# join thegame

UpsetChicken

kuligs2 Yea. But how do I assign a specific player to a specific connected controller?

e.g.: let's say I have four players(four controllers), and one of them press the join button. How can I make my game detect which controller joined(0, 1, 2 or 3)?

kuligs2

UpsetChicken you need to wrap your mind around rpc
https://docs.godotengine.org/en/stable/tutorials/networking/high_level_multiplayer.html

Basically you wrap @rpc before your function where you set player or on_player_choose and check if its player or server, if server then server sets the player slot etc.. you gotta set your whole game structure around that notion that server serves players, and players request server to do things for them, such as create new player, or spawn object, then the spawn function needs to be run on every player instance..

took me few attempts to understand... i suggest you build a test multiplayer bare bones game/scene, and test and see how it all works.. godot has the simple tutorial, you can start with that.. https://docs.godotengine.org/en/stable/tutorials/networking/high_level_multiplayer.html

Furystream

I usually map inputs by defining actions in the Input Map, then checking them in _process or _physics_process with Input.is_action_pressed. If you need per‑player controls, create separate action names for each player and pass them into your controller script as variables. During testing breaks I sometimes unwind with a quick click on KOITOTO, which oddly helps me reset before debugging tricky input issues.