Iâll go over the 2nd question first since thatâs the easiest to resolve. So I donât own that turret pack, but could you tell me if the pack uses static or skeletal meshes for the turrets?
If they have static mesh models, then you can just head over to the DT_TowerData data table in the Tower folder and change these two parameters as required:
The TowerMesh parameter can be used to change the mesh used by the Tower while the OffsetFromGridCell parameter controls the position of the mesh relative to the underlying grid cell. So like, say, for example, if the tower appears half underneath the ground, you can set the z value to half the height of the tower so that it is spawned above the ground.
Once youâve modified these two parameters for the required tower, just head over to BP_TowerManager blueprint and press compile (maybe Iâll make some changes in the next update so that this step is not required). When you return to play the game, the tower model should reflect the changes that youâve made in the data table. If it still doesnât work, weâll look into what else might be causing the issue.
Now if the turret pack comes with skeletal meshes for the turrets, there will have to be a few more changes. So let me know if thatâs the case.
Itâs a bit late at night here on a Saturday. So Iâll get back to you with the remaining queries tomorrow morning. Cheers.
Alright, so moving on to the third question, the guns in the pack seem to be skeletal meshes, similar to the ones provided in the toolkit. So you can just swap out the meshes as shown below for each of the provided guns:
Optionally, if the guns in that pack come with an animation blueprint, youâll have to set that as well through the blue highlight option.
Apart from that, I donât know how big the blueprints for those weapons are, but Iâd suggest copying over all the blueprint nodes and variables from there to the weapons from the toolkit. Parent weapon blueprint to BP_BaseWeapon blueprint, and similarly for each corresponding child weapon blueprints.
And I just saw the video of your game. Itâs good to see the toolkit being put to good use.
Iâll be uploading new tutorials over the coming weeks since some of the existing tutorials are based on older versions of the project. So hopefully, thatâll be of help to you as well as other customers going forward.
As for the co-op support, I donât have any experience working on the networking and multiplayer side of Unreal. But if you have any doubts regarding the current implementation, you can always reach out to me here or through the support email.
Moving on to the 1st question, each Tower has its own attack logic but you can find them straightaway in the even graph if you open the Tower blueprints.
For the Laser Tower, Iâve provided a placeholder laser particle system, but you can replace it through the âLaserBeamParticleSystemâ parameter.
The Machine Gun Tower & Sniper Tower both use a similar hitscan firing system and just apply instantaneous damage. But you can spawn a particle system just before that in the section marked below:
The Shockwave Tower just applies damage to all enemy units in range, but you can spawn your particle system right before the for loop in its AttackEnemyUnits function.
Iâll share the steps for weapon projectiles as well soon.
Also, on a side note, I havenât used ChatGPT for Unreal development yet. Does it help with blueprint programming or general usage of Unreal Engine?
Well then, Iâll give it a try as well. I was thinking of using it to help me create tutorials more quickly. Didnât really think of using it for development.
Iâm available to work on blueprint-based projects, but Iâd like to know the scope of the project and if itâs within my skill set. You can share more info about your requirements either through private messages or my marketplace support email.
The toolkit is now available on Fab with a brand new v3.16 update.
Change Log:
I. Revamped the AI Controller and Behavior Tree for Enemy AI with a much more streamlined system thatâs less complicated and easier to work on, while having all of the previous features including AI being able to choose between the Power Core vs the Player as its target based on proximity, visibility, as well as any damage inflicted in recent memory.
II. Made improvements to the Tower Constructor/Highlighter UI both in terms of UI design as well as using event dispatchers to make the HUD updates happen in a more automated fashion. Also included are UI design improvements to other aspects of the HUD.
III. Created a data-driven model for setting up Enemy AI stats & behaviors. You can just customize or create new entries for enemies through the DT_EnemyData data table as shown below:
Hey there, yea this should be an easy fix. So all of these issues seem to be coming from just two class: BP_WaveSpawnController & BP_BatchedWaveSpawnController. These can be found in the folder Blueprints >> WaveSpawning and its subfolders. So just try this out first:
If you try packaging it these again, these errors should be gone. If you see more of the same type of âFStructProperty UnknownStructureâ errors, just go to the blueprints mentioned and repeat the above step. If the issues still persist, just let me know and weâll take a look into what else might be causing it.
I. Switched to an enum-driven system for retrieving hitpoint stats, making it easier to access specific values like Health and Shield. This significantly improves HUD integration and reduces the need to modify logic whenever new stats are introduced. A similar system for Tower stats is planned for a future update.
II. Introduced a new Shield stat alongside Health, with support for both additive and multiplicative modifiers applied to either stat.
III. Added shield regeneration that kicks in after a short delay if the player avoids taking damage.
IV. Shield functionality is currently limited to players, as enemy health bars havenât yet been updated to support shield UI. Support for shielded enemies will be added in the next update.
HUD System Revamp
I. Completely reworked the HUD update logic using Event Dispatchers to respond to all gameplay state changes.
II. Other gameplay classes no longer need direct access to the HUD widget, improving modularity and reducing cross-dependencies.
Upcoming Features:
Performance improvements for enemy nav path display calculations
Shield bar support for enemy units
Minor performance and design improvements across the board for all blueprints
