Assign mouse buttons/keys different actions based on which item/"state" is equipped?

[anonymous_user_84e009961 (anonymous_user_84e00996)]

@Yggdrasil;656294

Don’t forget that while you can handle the functionality of the mouse clicks and selections in the player controller, the actual coding of what to do with the object is probably best left to the objects themselves. Like in real life, there are many ways to get to the end result of where you are trying to get to. For example, the Use command:

For example, in the player controller you can have that enum state set to Use and broadcast that to the object blueprint. The object would then interpret the use of itself depending on what it is. I’m not sure how your game would react, but in my case food is used differently than chairs which is used differently than Angela.

I would have the parent blueprint called food_master be in control, making the Use message translate to eating the food for some effect or something. Then the food would disappear because it was used, or eaten. I could also make it so the food would be thrown if used, or placed into a vehicle’s tailpipe (like bananas for instance, pretty popular gag in Beverly Hills).

My chairs would allow the player to sit on them or placed into a reclined position if used. Angela, the sweetheart that she is, would probably look at you differently once she felt used by you. I would likely not want to eat the chair or Angela nor would I want to sit on the food or hurt the chair’s feelings, unless those were indeed options that I could give the player. Could happen, it’s a game. It’s your world, do what you want. I’m not here to judge.

The point is, you can switch on Enum and provide differing functionalities to the different items / states that are available, but the decision of how to interpret the states is coding best left to the items, otherwise your controller becomes much more complicated. Using the Parent / Child relationship of blueprints is fundamental to this type of system.

I would combine this system with an Interface. That way you can have a ‘Use’ function implemented across Food, Chair, and Agela.