[SUPPORT] Advanced Turn Based Tile Toolkit

[Monokkel]

@izckl

Hi,

I figured a lot of things out since my post from saturday. I think I understand the toolkit much better and already began trying to build my ideas into it. As said I want to do a board game. Different tiles will be assigned different states in the course of a game (for example controlled by player 1 or 2 and so on…). For that I initialize a map with grid indeces as keys and integer values corresponding to the state. From a custom ability I call a function in the grid manager that updates this map - when a state changes. In the Ability-BP where possible targets are determined I changed it to output a set of indeces according to my needs. And in the animate actions part of the Ability-BP I changed the meshes which are supposed to be shown at the possible target indeces. Just to give you a short overview of what I changed. But I don’t know what could be responsible for my problem: I tried to print something out after the branch which checks whether the unit is ai controlled and that one gets printed. After that the event Player Activate should be called but the string which is supposed to be printed directly after the Player Activate event doesn’t show up. What could be the reason the event doesn’t start? There is nothing between the two Print to Stings other than the event call and the event.

I tried connecting the execution path (if that’s what you call it) coming from the ai check branch to the first node in the Player Activate part and then the meshes are shown on the correct tiles. But I guess there is a reason this is not directly connected that I’m just not seeing?

Edit: I made my additions in the same project in which I started fiddling around with it. Maybe I changed something without knowing it. Is there any easy way I could export my own functions and everything I changed without building up everything part by part again?

I have the same problem now between the event ActivateUnitAbility in the Unit and Ability System Blueprint. I guess I broke something somewhere?

Thanks for helping!!

Hey, sorry for the late reply. Adding a print string should not break any execution chains, so I don’t really know what is happening here. Are you modifying BP_Ability directly? If you are using a child blueprint of BP_Ability which overrides PlayerActivate then the PlayerActivate nodes in BP_Ability will not trigger. Where exactly are these print string nodes placed?

@Phoidy

I guess with Crux you mean me

I’m happy to hear it was helpful for OperatorCrux.

I’m still stuck with getting my custom characters to move:
I made a blendspace (1D) with the same specs as the ones you use (speed 0-600, idle, walk and run at the same position, preview works fine).
What i see now when I move a character is they are in idle animation (so the first part of the blendspace works), but they slide to another location instead of walking.
Somehow the walking part of the blendspace isn’t triggered or there is a problem in my ABP somewhere.
I haven’t worked on it for a few days, but I will dive into it again tomorrow.
If you have any suggestions I’d love to hear them

Oops, sorry. Swapped the names out while typing. Hard to know what part you might be missing as you seem to be doing all the steps that I did and which work on my end. Perhaps try deleting and re-adding a couple of things so that you know that the correct references are being used? In your custom unit blueprint make sure the MulticastMoveAnimation calls the Animate movement interface function from the correct reference. Make sure it is the interface event that is called and not something else. Ensure that the abp was compiled with the interface added before adding the call to this event. Try printing the input and output of the speed variable and see if it has the correct value. In your animation blueprint, check your blend space and make sure that the animation changes appropriately when you alter the balue within the timeline. Check that you are using the correct blendspace within the state machine and try deleting and re-adding the reference to the speed variable in the blendspace. That is all I can think of now as, like I said, you seem to have done all the right stuff, and it works for me.