A bit late, but ok!

CLAP CLAP CLAP. AWSOME.

Animate the Root position / Character locator to end up in the position you want, IF you want the character to end up forwards where the step ends.

you r not alone everybody not understand anything :D just do what this guy doing if you really want to make and achive something go buy book on it blueprint or c++ what do you want

@@isimbulamadmobenibulsun660 I understand most if not everything he's saying. A few times I had to google something but mostly because of version differences. It does help to have some understanding of programming but you by no means have to be a programmer to do this. Of course everyone learns differently, there's no way he can teach in a way that everyone will understand, it depends on your background and learning style. It is complex, no one (at least no intelligent person) ever said creating a 3d game was easy to learn. The reason it took so long before we could actually see anything working at all is because we had to do a lot of setup. As for Charl's question from a programming perspective a global variable may be possible but it's considered bad practice for a few reasons it also may not work at all in UE due to the way the modules (the programs that make up the game engine) are set up. Though it may seem more complicated to set up the variables this way it's actually more efficient and helps avoid issues when you start having a bunch of characters and other complex things in your game (wait was that isPunching variable for the player character or generic baddy 275). The global variables we set up before are essentially control related and assume a single controller (mouse/keyboard, gamepad, or touch screen) so they aren't such a big deal though best practice (at least to my understanding) would actually be to setup keyboard shortcuts.

yes i did.. Update the unreal engine version. That's how my problem was fixed

That's a good question, and this is a really late answer! :-) But for anyone who may have the same question, I believe in this case, it was mostly done for tidiness (so you don't have too many crisscrossing node wires). It seems you could totally plug the "IsPunching?" variable which you "Get" from your Character BP into all the other locations where that variable will be used in the Event Graph of your AnimBP. HOWEVER, if you ever needed to use that variable "IsPunching?" within a State Machine (as a Transition Rule, for example-- the way we used the "Speed" and "IsInAir?" variables), then you would for sure need a local copy of the variable which can then be accessed for such use.

Every Pawn will have Is Falling and Get Velocity. Not every Pawn will have Is Punching. The game can't infer what kind of Pawn the Get Pawn Owner block will return, so we have to check first.

"IsFalling" and "Velocity" are variables that were created inside the "Pawn" class, while "IsPunching" was created inside the "CharacterBP" class. The function "Try Get Pawn Owner" will access only the functions and variables of the class "Pawn", and not the stuff that was created inside the class "CharacterBP", which is a descendant of the class "Pawn" but is another class nonetheless. It seems confusing because "Try Get Pawn Owner" is returning us an object that we know is a "CharacterBP", but it's treating it simply as "Pawn" and, because of that, we are not seeing the variables that were declared inside "CharacterBP". That's why we have the "Cast" function, it takes our object and says: treat this object as a "CharacterBP" and not as a "Pawn". After casting, we'll have access to the functions and variables created inside "CharacterBP", including those created inside "Pawn", because "CharacterBP" inherits from "Pawn".

@@peacesells2847 Taking it a step further it should actually be possible to set the cast function up before everything else since it inherits everything from Character which inherits everything from pawn (I haven't actually tested that though). I presume he avoided that setup so we could have something playable a little faster. Which functions are available also seems to depend on if we drag from exec or As character BP.

ok what you can do is add a input touch event in the characterBP and from the pressed you want to drag off to a branch, then drag off from the finger index inside of the input touch event and create an equals == node and set it to Touch 2, because we already used Touch 1 for touch jump input. Then from the execution of the branch you want to set isPunching to true. From the released of the input touch event, you want to do the same thing except set the isPunching to false because when you are not touching the screen with Touch 2, you aren't punching anymore so isPunching should be set to back to false.

can you make a tutorial about it?

In the skeleton tree set "upperarm_twist_01_l" to "Skeleton".

Just go to project settings> input> then make your own punch

@@WingMaster562 thank you, I have already figured out what I did wrong. Thanks anyway.

solucionado

I ran into this issue as well. Solution is in Video #5 Setting up Inputs, at about 10 minutes.