Thanks for the reply! That makes alot of sense to me coming from a UScript background, I was just curious because arrays are quite a complex topic and to a non-programmer I know terms like replication and array can seem so overwhelming. Ive witnessed many morale defeats before any work is even underway and I believe alot of them are down to nothing but the fact people wernt working with a GUI, that text based programming (regardless of its complexity) has a stigma attached.
I do think that is Blueprints greatest strength is that its independent from underlying syntax allowing a user to explore their potential more thoroughly without being railroaded into a line of thinking. I find it great that I dont have to write as much pseudo because I can draw a flow graph on paper and just take that to Blueprint when Im ready instead of having to convert back and forth. I do think that is an overlooked step, that even when Im writing text based code I still find flowgraphs important on a number of different levels, especially for gameflow and events so its possible that Blueprint can teach skills you cant learn from math and syntax.