Input Controller and horizontal/vertical movement

If you want to approach it this way, via an enum, then a common solution is the use of a "switch" statement:


switch (e)
{
case MovementDirs.Up:
// handle moving up
break;
case MovementDirs.Down:
// handle moving down
break;
default:
// error?
break;
}


You would need to add the other "case"s for left and right. The places where I have "comments" you can replace with whatever code you are intending to move your characters. The code won't continue past the break statement. It is kind of like a chain of if-elseif branches. Does that make sense?

Yep, you actually need "e.info"

The repeater did check for a key being held down. It allowed the events to be sent repeatedly but should fire at the "rate" field of the repeater.

The code I wrote was geared toward input you would need for a menu navigation or for moving a cursor around a board. If you are looking for more of a real-time movement system then I would get rid of the Repeater portion of the input controller. From looking at your code, I would guess that the reason your character keeps moving is that you aren't doing anything to slow down the moveVelocity of the character. Perhaps you need the moveEvent to trigger even when the move direction would be "none" and then you can set the velocity to zero.

Also, your moveInput vector is already normalized, so you can skip that step, and since this update is occurring each frame you should use a Time.deltaTime multiplier to make the game feel the same across different systems.

You're right, the whole event-based input system doesn't make a lot of sense if you need to check it every frame anyway. In fact, it can be much worse because it is constantly creating event objects which have to be garbage collected. You might as well check the Input from Unity yourself.

You won't be able to see a private class from anywhere except the other public class in the same file. You could have the other class modify the value as long as you exposed the field as a non const and public field. Otherwise you could have the private class listen to events, etc as another means of getting it configured. Note that the class doesn't HAVE to be private either. I only made it private to indicate that I didn't intend anyone to need to mess with it. By hiding things you can kind of help indicate to other people how you intend things to be used.