It worked, but I'm again confused, those values were stored on the Y axis, okay,
I think I might know where my confusion is coming from,
so, it looks like I'm asking for the X axis instance, but that's only to reference it.
I'm not specifying where to look on the Y axis with CurX, I'm specifying the instance I'm looking into, then moving up the index, I get the X, Y, and Zindex of that instance.
In my opinion this is so counter intuitive that even though from here on out I can absolutely apply it confidently,
If I were to program an array function with search functionality for a game engine, Id have Cur# be a listing expression,
so if I were to do the same thing I did above,
Id go, Has Value = "armor" ( this is so that I've already specified which instance on the X axis I'm requesting, I shouldn't have to do it again??? This would do the same thing as CurX in this situation but I wouldn't have to type it out again ) Instance.At()
And then inside the "()" I'd use CurY to look into the Y axis to retrieve my values.
I know for a fact I'm not the only one who finds this confusing, I've seen programmers hop on here and say its convoluted, even if they eventually figure it out with the help of this community.
Alright, I think I can continue from here and exit the prototyping stage, I'm sure some of you noticed the script was pretty small, that's only because it's in its own testing area for safe keeping.
Time to scale it up and see if it truly works.
I'll let everyone know if I have issues, but assuming things go smoothly, Ill post the entire save and loading system step by step so that anyone from C2 or C3 can replicate and modify.