[SUPPORT] Advanced Turn Based Tile Toolkit

[Monokkel]

@crossmr

I’m not really expecting other status effects in this kind of game. So i’ll look at that. How would the AI handle a unit that has no attack abilities? At some point I may have to start working on the AI as well to make it a little better and handle my specific scenarios (like encouraging robbers to escape and cops to arrest robbers)

The AI loops through all its abilities and generates an estimated value for each. It chooses to use the one with the highest value, but if none have a value higher than 0 they just skip their turn. If they have no abilities they should just skip their turn.

@crossmr

Edit: Another thing I’m trying to address here is hiding move tiles on floors above the floor I’m on. To make it easier to move around. So for example, in that convenience store building, if there is a ladder on the back and there is a unit near that, they can move around in the store but also up the ladder to the roof. The issue I have now is that moving to the roof is easy, but moving inside is a bit of a mess because the roof move tiles are on top of the inside move tiles. I already have some buttons on my UI for “changing the floor”. what this does is change my path trace for hiding meshes between the camera and capsule. So by moving up a level it makes the building roof visible so it’s easy to move around there without being distracted by the lower level stuff. Is there someway I can return the move square tiles and what properties are available for them? Can I get a Z height of all the tiles and then try to hide the ones that are “above” the current floor selection?

The tiles in the included abilities are either instanced static meshes or decals. The ISMs are especially tricky to modify one at a time, but it can be done. You can loop through all instances and use GetInstanceTransform, removing or moving the ones over a certain height. You cannot just hide ISMs, though. One option is to have separate ISM components for each height level, so you can destroy/respawn all tiles at a certain level, but again you could not hide them and would have to store their locations somewhere so you could respawn them. It might be easier to switch to regular static meshes, which can be hidden. While spawning them you could populate a map with grid indexes as keys and static mesh references as values. That way you could look up their grid indexes and hide/reveal them as appropriate. All of these methods are a bit awkward, but it is the best I can think of at the moment.

@Juxtapox

Hey, I got it to work, except it always displays from 0,0,0. It seems the AnchorOffset is always at that vector. Could it be that in BP_Ability_2D you get Revealed Grid Indexes from BP_Gridmanager_2D, but in BP_Ability_MoveAttack there’s no such thing? Because I notice you cast to it in the 2D example.

Anchor offset should not affect it. That is just if you want to offset all tiles, which is currently only used for multi-tile units that have a center between tiles. I’m guessing you’re not passing the vector locations to the action properly. Not sure what could be wrong here. Could you screenshot your setup and post it here?