Nit-picking at function parameters in blueprints.

I don’t understand why in a blueprint functions taking in parameters I have to drag wires off the entry node instead of calling a get node. Of course, the obvious solution would be just to define local variables and set your parameters to those, but that makes no programmatic sense setting a locally defined variable to a function parameter because parameters are already globally defined within the entire function scope. I can’t name a local variable the same as a parameter so the editor does acknowledge that something of that name is already defined. So why can’t I use a getter node?



I believe this was briefly discussed here. See if it clarifies anything.

Oh glad to know its being worked on.