[SUPPORT] Advanced Turn Based Tile Toolkit

[Monokkel]

@Curiosichi;720987

Thanks for the ETA on the feature additions! Good luck with it and the code clean up. If it is possible, do try to document how one would upgrade from your current version to the new version to make the process as easy as possible for your current customers. Thanks!

I’ll repeat that I might be completely off the mark regarding the ETA, but it is the best guess I could make. I’ll have to think about the best way to log all changes. It will be tricky to list everything, but I’ll note all the big structural changes at the very least.

@Curiosichi;720998

Do you have an easy way to disable the default HUD? Or manage overriding it with a custom HUD.

In the base toolkit, you have a HUDBlueprintRef set on Begin Play(), a get at HUDTurn Toggle() and referenced again by Non_Nativized_Functions for displaying game over.

To override the functions that use it without changing the base toolkit, would I need to create a copy of Event Begin Play in a child blueprint just to change the HUD generations portions of the base toolkit? That seems a bit clunky… In the example maps, you create a reference to new UI elements in the child grid manager instead but they only overlay the base UI, which to me makes obvious sense that a custom UI goes with a custom game mode/grid manager/player controller, but I want control over the whole UI.

edit: blarg I wrote a huge wall of text explaining how I did this then unreal forums decided I wasn’t logged in while typing into the quick reply…, but I accomplished this by basically copying parent/base toolkit code into the children custom bps. As I stated above, its clunky, I am no longer calling to the base class for begin play, kill unit, copying the Non Nativized functions file and using my pawn with skills to refrence it instead of counting on the base pawn to set that.

While I got it to work, it feels wrong, this is basically just copying your base classes to my custom, so my question still stands. Is there a better way to do this while retaining your base blueprints.

I’m not sure there is a super clean way of overriding the HUD functionality without altering the base toolkit. Your solution is actually pretty much how I would do it if I was forced to do that myself. I’m not sure I see the point of not altering the base toolkit, though. In the next update the HUD-setup will be completely changed anyway, so keeping the old HUD-nodes intact won’t wake porting your game to the new version any simpler. So unless there is not some other reason for not touching the base toolkit that I’m not seeing I would just alter it directly.