[SUPPORT] Advanced Turn Based Tile Toolkit

Monokkel · September 23, 2021, 12:23pm

bigrockwall:

I decided to go a different route and just hand make quests widget, objective widget, quests, and objective blueprints. I followed a youtube guide that does this in 3rd person game mode. Following his guide, I had no problem getting the quest log to open and populate in the 3rd person project.

Then, I migrated the blueprints over to an ATTBT project. That’s where the issues start. I think I have narrowed down the cause. In the 3rd person tutorial I followed, he uses the standard ThirdPersonCharacter for some needed code, and to be referenced in all the quest and objective blueprints. I cannot find a separate ThirdPersonCharacter_puppet, it’s just a pawn class that functions differently than the actors that come with the toolkit.

What I’ve tried so far. First, I tried moving code from BP_Unit_anim_character over to ThirdPersonCharacter to try to get 3PC to register to the grid, in the same manner as your tutorial videos about puppets connects Golden to the grid, for example. That didn’t work. 3PC just sits there like a piece of scenery.

Then I moved all the quest coding (J to open journal, and get quests on event play start) from 3PC over to Unit_Anim_Character. The issue I run into here, is that U_A_C is not a pawn, and the coding in the objective and widget blueprints only works for pawns, they wont compile properly when casting to actors. I did notice that the code for J = open quest widget seemed to work in the U_A_C event graph, but the objective widget (inside quest widget) doesn’t populate like it did in the 3PC only game.

So I moved on to moving the same 2 lines of code over to BP_Character_puppet, and changed all references in the other blueprints to reference it. Seems to compile fine, but I still don’t get any data populating my quest widget when i press j. Side note, BP_C_P has its own event start. I assume hooking up the get quests blueprint to the existing event start would work. Assuming BP_C_P is even the right place to put said code. My understanding from watching your tutorials was that puppet only accounts for visual representation, and all game logic was held in the BP_Unit_Anim.

Also, when needing to cast to a player controller, do I need to be casting to PlayerController, or PlayerController_ATTBT?

This is driving me nuts, I’ve spent 20+ hours on it trying to work out every possibility I could before bugging you about it here.

Hi again. It is still a bit tricky for me to know exactly what is happening here, since I don’t know how the asset in question works. That they have hard coupled a quest system to the pawn class seems a bit weird to me, but I guess I’ve heard of worse coding. I can only make guesses here, but I’m guessing that you are supposed to move into some trigger which activates a quest UI or the like?

I think this might be easier to solve on Discord, where we can go a bit back and forth and we can try to figure out what is the relevant part of the code together. Check out the original post of this thread to find it.

As for casting the player controller, that all depends on what you need. If you only need to access functionality that is contained in the base PlayerController class, no need to cast it. If you need any of the custom stuff in PlayerController_ATBTT you’ll need to cast to it (or use an interface).

Hey, have you tried to run the MPSpawn example map? It lets multiple players join the same map and only starts the game once all have clicked to start. It seems like your question might be more about general networking than anything specific to ATBTT (might be wrong here), so make sure you know how to set up such a map in a simple project without ATBTT first. Then you can see if you run into any ATBTT specific problems that I can help with.