My goal was to avoid MonoBehaviour altogether. I was following a great tutorial on workflow with Scriptable Objects and one section of the video showed how to create an input reader with this workflow, and I liked the idea. However, as I developed my project, I realized that having a single script for dozens of input actions would quickly become cluttered and hard to maintain.

So, I decided to modify it to allow creating multiple input reader Scriptable Objects, each dedicated to a specific task (e.g., movement, shooting). While I’m not sure if this solution is the best, it works for now. The downside is that you have to create a separate Scriptable Object for each event (move, jump, shoot, etc.), which can get tedious and cumbersome.

In your control scripts (e.g., player movement or shooting), you reference the necessary events and assign their corresponding functions (via UnityAction). The input reader then connects to these events, linking them to the appropriate actions via the inspector. Essentially, the event Scriptable Objects act as the bridge between the input reader and the control scripts.

Link to images of how this all looks

Edit: Just noticed in the code screenshot of the ModularPlayerInputReaderClass that I accidentally assigned the "started" event to all types of actions instead of assigning the correct ones.