Thanks for taking a look!
I figured it had to do with some sort of hierarchy/logic issue in the programming for sure. I am going to try and replicate this in SW 2014 one day as I believe it would update as I intended it to here, based on my experience with the software so far. I think that is one thing SW excels at as it seems to know what you had, and how to shift the things before and after the edits to the next best version that won't hopefully crash...but it of course isn't perfect.
You don't think it has anything to do with the wonkier way it way originally made by MikeKovacik4928, right?
I thought I would be beating out any problem because I have selected what is very simply, the last face of that pattern feature to create my mid-plane. It seems to me, that a smarter solution would be to best solve for how the part was before the change, especially based on my mid-plane inputs alone, right? Like how does that practically make sense? I get it from an objective point, but we users want better intuitive, parametric capabilities like this so our parts just work the way we think they should. Last face is last face, right? I know my ideas are very basic with respect to what actually has to be coded in, but I believe that how the software should think about things.
Originally, the plane was created like you've suggested, as you can see from MikeKovacik4928's design; I guess he knew what he was doing in that regard. Using the right parameters, I can likely get it automatic like I want, it's just not as practical as I had hoped is all.
There is no power but what the people allow you to take.