I used to think the same way, so now I will introduce you to the concept of DRY:
https://en.wikipedia.org/wiki/Don%27t_repeat_yourself
In a case such as this where you are not pleased with the available methods of searching it's now time to look at the problem in a different way.
You have the problem of needing to change too many actions of the same type. In the DRY mindset there shouldn't be a repetition of the same action to begin with. Thus, my recommendation is to create a function along the lines of "Set muzzleFlash", you can make it more specific but in general this function should be comprised of actions you find yourself constantly repeating in your code:
Function: Set muzzleFlash(ParentUID):
Action: muzzleFlash: Set ParentUID to ParentUID (In most cases I imagine the value you are passing in is Player.UID for the ParentUID parameter)
I would refrain from repeating the same form of code throughout your projects because over time the required refactoring of code when changes are made becomes unreasonable.
Now that you have a function set, let's say later on you need to add an action to set a variable in muzzleFlash, or you need to make an edit to how variables are set in this function, you now have two benefits:
1. You can find all references of this specific function in your search results.
2. You can edit the function to effect all instances where you are calling the function.
Just my 2 cents.