The logic for the child blueprint is broken into different sections. The first part is the referencing of variables stored in the parent even though the child blueprint inherent these variables It is makes it easier access to that data and more time efficient just getting the data from variables panel compared to searching for the data in the drop down menu.
Another integer variable i used was 'spawned amount'; this is in the index of how many meshes was spawned. The concept is that, I use a 'For Loop' node that fires a custom event in the loop; then later in the logic adds one on to the spawned amount. Doing this turns the script into a checking loop logic where I test between the amount spawned and the spawned max. This means if the amount spawned is less the the spawn max the fire another loop until the spawned amount index equals the spawned max.