Obviously you can do stuff with UInputMan in order to find out if keys are being pressed. Now, is there some way to figure out which player is pressing the key? I'm having an issue where pressing the melee button I've set up makes it activate for multiple players.

Now that I think about it, I could probably just set up different keys for different players, which would probably make more sense anyway. Still, just for curiosity's sake, I'm asking my question anyway.

Well, the problem here is, how would the game know which player is pressing it? The game assumes that there is only one keyboard.

It could check who moves when a certain button is pressed, then figure out if that's red or green.

Haaaaaaaaaa... good point.

Okay, time to change the subject a bit before I feel too dumb. What does everyone think is the most efficient way to set up new controls that can be customized by the user?

My current solution is to make a settings.ini that defines some simple null particles, each one representing a different control. You set the mass of each particle equal to the ID for the key you want. Then in the game, actors that rely on those custom controls have in their script some stuff that creates these particles somewhere out of the way and then reads their mass to find out whether or not a key does something. This is useful since it also lets players change keys in-game with the command line, by finding the particle and changing its mass.

I swear a while back somebody somewhere suggested something simpler, but I fail to recall what it was.

Could you do a "Press the button you want to use for..." MOSParticle popup, linked in script to the mass thing?

It needs to be persistent between instances of the game. And the interface for changing the keys in-game isn't really what I'm asking about. What I'm wondering is if anybody has any other ideas for storing the keys for the long-term. My idea works, but it feels a tad convoluted. Then again, considering what I have to work with, maybe convoluted is the best I can do.

Can you just check the line from settings.ini?

Not in any way that'd be any less complicated than actually packing in a file I/O library.

You'd have to have a file reader specifically check settings.ini, either through a batch file or lua i/o, and have it spit out another file for CC to check against. At that point, you might as well have a specifically created and modified file.

But uh, yeah, not having any I/O is pretty limiting to longterm stuff. I'd ask Data, but I can fully appreciate why he didn't include it. That said, limiting it to the same .rte shouldn't be too hard.

Well, I guess I'll stick with my method then.

What would be CC modding without awkward shenanigans?

You could say something like "if my actor is player number 2 and this button is pressed, I'm going to make this happen." TLB has a player checking code in his Mind Control Orb, but I can't make sense of it.

In theory that works, but in practice, it really doesn't. You have one keyboard. How does it know who pushed which button?
Let's say you're using the button "I". It is not associated with either player. How does the game know whether it was player 1 who reached over and pushed it or player 2? Simple answer: it doesn't.
Anyway, to get an actor's controlling player, actor:GetController().Player works just fine.