Subject: The Player performing the current Event being processed
Target (Object): The array of Players and In game objects that was targeted by the current Event being processed
New Events:
Ability 1 used (Target, Subject)
Ability 2 used (Target, Subject)
Melee used (Target, Subject)
Ultimate used (Target, Subject)
It’s very difficult to find the target of a Mercy damage boost and certain other abilities as it stands and this should make things a lot easier.
New Features:
For all Values that return a player or list of players such as, “All Players”, “Closest Player To”, “Player Closest to Reticile”, “Players Within Radius”, etc give us the option to filter them by whether or not they are within Line of Sight, and whether or not they are alive. This is a lot more useful and it would make a lot of other values such as “All Living Players”, etc redundant.
Give us the ability to customize guns. Introduce new values such as Weapon Rate of Fire, Weapon Ammo, Weapon Fall Off Enabled, Weapon Rounds Minimum Damage (Fall off), Weapon Rounds Maximum Damage (No Fall off), Weapon Falloff Range, Weapon Spread Angle, Weapon Spread Recovery Time, Weapon Number of Shots Required for Spread Activation, etc
Let us customize the damage of different abilities at the very least. The workshop should have access to all the sliders, turns and dials that you can manually access in hero settings in custom games.
Allow us to make a player perform a certain action without having to force them to press a button. For example let us force a player to use melee without using “Press Button(Melee)” which might fire events that you don’t intend.
Give us a String To Number and Object to String converter and a Name of Player(Event Player) value
Isn’t this “victim/attacker/healee/event damage …”?
I see why you are asking this, but new rule types for such a specific use case? A new “target” action would be way better with the input being “button(primary fire)” or “button(ability1)” etc.
filtered array(players within radius(...), is in line of sight(current array element, ...)) and similar.
You better post your ideas in the “workshop suggestions” wiki thread I linked above. But please make sure that similar things are not requested already, before doing so.
And also make sure that things you are asking for are not already possible/implemented.
(Please take some time to learn workshop better before asking the devs for new actions that give you everything on a silver tablet
Of course, nothing against requests that improve workshops general functionality.)
These could all be condensed into an Ability Used event with a Button argument, because then it could detect the uncommon crouch abilities (Piledriver), jump abilities (Lunge), primary/secondary fire, etc.
We should be able to filter them by any condition!
Devs have stated that some heroes aren’t as compatible with sudden RoF changes. They would have to mess with every hero’s weapon, and they say that’s not worth prioritizing compared to the other big features they plan to add.
