Currently, compound binds are very hard to handle, if a bind with just one of the button is handled first, the compound bind can no longer be handled because then two actions would happen at once.

This could be solved with some sort of handler system:

Instead of checking a bind's state from an input event, handlers could be added to a bind on init which then call a consumer when it's state changes, this handling order could then be sorted, from most complex compound bind to simple single key binds.

After further deliberation, I have decided to disable compound binds in the meantime in favour of the future #20 as compound binds are not a common thing to have in games and is a confusing mechanic for many users.

Will just leave compound binds alone, and they will be discouraged to use. May revisit in the future.