In most university settings the university pays the instructor and the student pays the university, but the idea that you pay the instructor's salary really is unimportant unless the school is ridiculously small. College professors tend to be insulated from caring about that. Truthfully, seeing the prof is good to try and get an idea of why the course sequence exists as it does.. but it probably won't help you in the course.
I'm a high school teacher and we start with C# using console applications pretty much exclusively just to get a lot of the various programming concepts down. With college level courses though there isn't always a continuity to how they are presented.. even if a course pathway exists. In your case I'm sure the idea is to stretch your ability to adapt to something different. This is about working your ass off to overcome obstacles. The most important thing you can pick up from this process is to never be intimidated when presented with a new technology, because that will happen for the rest of your life.
My advice would be this.. you have an idea of how to program so you can now pick up a scripting language and run with it. Experiment with what you are doing as much as possible and encourage your teammates to do so as well. Stop worrying about what you missed in between.. you didn't miss anything. You are going to fill that gap with hard work, and being able to do that is what you are going to get out of the course.