[SUPPORT] Advanced Turn Based Tile Toolkit

[Monokkel]

@ridley075

This worked great. Only problem is I have to modify the grid manager in core (or i could always create a duplicate). I’d like to be able to just create a child, and then override that function, but for some reason it does crazy things when I try that.

EDIT: Actually, just figured this out. I had to clear the local edges variable I was using (Because it’s overriding a function that not does not end in a return node, it just creates an event in the event graph, so i can’t use local variables, so i had to create a new normal variable for it). Now it works perfect! Thanks for the info!

Overriding functions in blueprints is a bit weird like that. You’ll notice that quite a few of my functions have a boolean output variable called bSuccess that isn’t really used. This is mainly so that child blueprints overriding this function will have it overridden as a function and not an event.

@crossmr

How can we control that? I have an aimed and snap shot. If they don’t move, they can aim and have a better hit chance, if they do they can move and snap shot with a lower hit percent.

If you’re basing your abilities on BP_Ability_Laser the AI value calculation is largely based around hit percent chances. It loops through all tiles in move range and checks the hit chance to hit various enemies from each tile, as well as the chance of being hit from those units at each tile. You can add your hit chance modification into that code as well. The simplest way to do this is to modify the FindAbilitySpecificTileValueModifier function of Laser. Something like this should do the trick:

@MarsOdysseus

Ok like I said in my previous message, it work but I noticed something.

If I move a unite and don’t attack or end my turn I can move others unit too.

What I want is if I take the decision to move a unite I can’t move other unit until my next turn even if I don’t attack or end my turn. Because I want player to be able to move only one unit by turn.

Thank you for you support.

I’m assuming you’re basing the abilities of your units off BP_Ability_MoveAttack. The code for switching to another unit for this ability is held in the DefaultClick function of BP_Ability. You need to add a check here that prevents you from switching units if the current unit has already acted (which in the default toolkit means that it has less than its max AP). This should work:

The updated videos on the basic stuff would do me real good…Yeah, like you said, I had to tweak collisions. It’s all very basic stuff I’m dealing with I think: now I’m trying to correctly make this child unit BP die; everything is working fine except the static mesh I added stays on the grid even after the unit dies and the tile is freed.

I can’t understand some aspects of the BP_Unit events. There is a “Kill Unit” event, triggered from the Take Damage function, which I assumed is responsible for removing the unit from the game once it’s dead. However, after debugging with breakpoints it seems it only is activated on the last kill before win/lose condition is achieved?

It’s so bizarre, since the Branch condition is a simple “if the unit’s health is <= 0”…And yet the game only pauses at the breakpoint on the last kill of a faction unit, AFAIK.

Also, what’s a good debug way to find out what blueprint is calling another blueprint’s events/functions? Print pins and breakpoints don’t allow you to see what came before them, and the Reference Viewer doesnt include references made outside the current BP.

Yep, I know updated videos are sorely needed. I’m planning to start working on that next weekend. The code for destroying units is a bit weird in the toolkit, and it is because of the action system and multiplayer. You don’t want to destroy a unit actor as part of the server side code, because all that stuff happens instantly, before animations are run. The units cannot be destroyed before all their animations have finished running. However, the unit still needs to be dead as far as the game logic is concerned, so it is removed from the GridUnits and InitiativeOrder arrays/maps (The RemoveUnitFromGame function).

Also, if the game is multiplayer we cannot simply destroy the unit immediately after the death animation is done playing on the server, as the clients might lag behind due to poor connections. Because of this a special action is called using the action system (called QueueDestroy). This action is run by the action manager, setting a life span to destroy the actor. This is by default set to 30 seconds, which should prevent issues for anything but the most extreme network issues. I’m not that happy with this hardcoded timer, though, and am currently working on a more flexible and intelligent solution to this particular problem.

Anyways, for your particular unit this means that you need to add functionality that hides it after it is killed, from the reference point of the client, but is still not destroyed, from the game logic’s point of view. Check out BP_Unit_Anim and the AnimateDeath event where the health bar is hidden. You want to hide the unit mesh here as well.