[SUPPORT] Advanced Turn Based Tile Toolkit

[Bridgeburners]

I’m spawning the ISMs client side, so I can assure you it is possible. Displaying tiles in sight and move range is handled in replicated ability blueprints in my WIP build. I pass input from the player controller to these blueprints which handle finding and displaying targets etc., mostly by calling functions from the grid manager. I can understand that you’ve had some trouble with this, because it is a bit tricky replication wise. Unless you have set things up differently, grid sized arrays like the Vector Field Array are not replicated (it would be a lot of data to send through), which means that if you try to run any function for spawning tiles on a client you’ll run into trouble, since the locations of all tiles are stored on the server. Therefore you have to get the appropriate locations on the server first and pass them to the client for display.

To give an example where you want to display tiles in move range around a unit when the unit is clicked:

Click input event in the player controller -> run event on the server that runs the Pathfinding function -> convert the array elements of IndexedCanMoveToArray to an array of locations locations by using ConvertIndexToLocation -> pass location array to a custom event running on the client, spawning an ISM on each location.

That is how I’m doing it currently, and it works great. Hope that helps!

Thanks for the response.

To your suggestion, that’s basically what I’m doing. (Not exactly, but the main idea is the same.) I make a small array of only the locations (as FTransform objects) which are calculated server side, and that small array gets passed to the client successfully. So telling the client where to spawn the ISMs is no problem for me. However I haven’t been able to assign values to the ISMs on the client side (i.e. tell the client that these objects are big blue squares), so when it comes time to actually place them where I need them on the client side, TileInMoveRangeMC is just an empty object. Is it correct for me to say that (at least in your currently released build) this process is done in the collapsed graph at the end of the “Activate Grid Manager” function? If so, should I have that graph run client side? Because I tried that but it doesn’t seem to work for me.