It sounds like you have a lot of work to do concerning how to actually create a game, let alone a multiplayer one. I have had many false-starts since my teenage years insofar as creating a game engine is concerned, and it took me a solid 10 years (with a lot of Real-Life getting in the way over that time) before I finally started figuring it all out. You could say I was super naive from the get-go, I knew how to render some stuff and have an array of entities with positions and velocities, but I had no idea how to actually build something that was manageable without coding myself into a corner that rendered the entire project hopeless and requiring a complete re-write (or some serious surgery that I had no patience for once I realized the horror of my code-design mistakes).
I have started many game engine projects over the years, each time thinking I had it all figured out, until I coded them to the point where it was obvious I still had some learning to do. I am finally *just now* releasing something, after spending 20+ years learning the ins-and-outs of game development, which I've been working on for over 2.5 years (again with Real-Life interfering along the way) and it's something I'm super proud of and excited about, and I couldn't have done it without learning everything that it took me to learn over all this time.
I guess what I'm trying to say is, don't give up, you probably won't get it your first try, but trying is how I learned, so go for it, but it can't hurt to have a realistic perspective of what you're going to be capable of starting with barely enough knowledge to make a single player game. If you won't have to deal with all the problems I did in my life you'll get there a lot quicker than I did.
If you're curious to see what I've managed to do check out my blog: http://deftware.blogspot.com
My game is called Bitphoria, and it's the product of wanting to make a multiplayer FPS game since the 90s when multiplayer shooter games were just in their infancy.