[SUPPORT] Advanced Turn Based Tile Toolkit

[Monokkel]

Thanks for sharing, I could really use some more of this stuff. I’m just missing half of Part 2 now which I’ll finish later today.

Both parts are great. I learned quite a few things myself despite having worked with blueprints for a long time.

So I think I got the counterattack fully working now. No BPIs needed, no casting done.

Like I mentioned, I’m simply using boolean inputs and outputs to decide whether there should be counterattack damage or not, based on a public boolean I created inside BP_Unit’s TakeDamage():

(While I’m at it, I might as well ask: in the example map, I notice that normal attacks always go to the False scenario of the lower branch, because AutoAnimate is false. In which cases would TakeDamage() want to go the True route, and call the Hurt QueueAction?)

…And then in ExecuteAbility(), if this HasCounterAttack returns as true, simply Take Damage again (after doing the necessary checks):

Does this look sufficently efficient in your eyes ?

Seems very reasonable. The whole idea of having both an interface and a boolean was a bit much, I agree. This is clean and should work fine. If sometime in the future you have many different kinds of units with different counter attack behavior, an interface would make sense, but if this is not the case yours is the cleaner solution.

Also, is it just me or did the timestamp comments in some videos of yours disappear? I was checking those vids again to refresh on some stuff when I noticed it. I mean, if you deleted those for whatever reason, I’m all ears.

I certainly did not remove them. Maybe YouTube incorrectly marked them as spam or something? I’ll take a look and see if I can identify what might have happened. Very annoying.

Edit: Nothing in my Held for Review or Likely Spam folders on YouTube. What specific videos are you not seeing your comments on? It will help me figure this out.

Lastly, I only now realized that whenever I modify parent blueprints, child blueprints will understandably be now treated as modified files that need saving. So I tried saving the parent and not the child blueprint to see what occurred, and upon reopening the engine, I noticed that all the changes I made in the parent blueprint are seemingly correctly inherited by the child BPs. Do you know if we’re screwing up anything in particular if we do not save child blueprints in these situations, or do you know if they can safely be ignored? Obviously for safety’s sake I might as well always save, but I’m wondering if there’s more to it than meets the eye.

When you compile a parent blueprint, UE4 should automatically compile all child blueprints inhereting from it, which will mark them as having to be saved. You should not have to worry about anything breaking if you only compile and save the parent.