Hello! I don’t have a solution (yet), I just wanted to let you know that I totally understand what you are going through… When I first began blueprinting, I wanted to make a ledge grab and climbing mechanic. I thought it would be easy, because it’s such a common thing in games… But I was wrong, it’s way more complex than I thought.
So I ended up postponing the ledge grab, and instead worked on easier things. As I got more familiar with blueprinting, I was finally able to go back and start constructing the ledge grabbing. It’s coming along great! But there’s still much more I need to do with it.
In the future, I’m going to make a tutorial on ledge grabbing! But I want to make sure my blueprint is just about perfect first. So it will be awhile.
But anyway, I suspect you will go through a similar story here. Wall running is a pretty complex subject. Also keep in mind that “wall running” can work in many different ways, throughout different games. And each way, could have a very different way of programming. (Btw, In your description above, I can’t tell if you wanted it to go vertical or sideways. “Vertical” would suggest going upwards.)
When you’re first starting out with something, the beginning is always the hard part. Just don’t give up, and you will eventually get into the swing of things.
Here’s some general advice for when you’re first learning to blueprint:
Always do one thing at a time. If you make too much at once, it will be hard to tell what went wrong. A common debug method programmers use, is to call a “Print String” node, just to signal when something works, and tell them they’re ready to move on. It can also give you a better understanding on how things work, or what numbers go around.
Another thing to keep in mind is that blueprints give you plenty of freedom on your approaches. There will often be multiple ways to program the exact same thing.