Hey do you guys think that with some training me and my friend could make an ORPG (Online Role Playing Game) with up to 100 people on at once?

How hard are you willing to work/study? There is alot to know if you do things from scratch and there is still alot to know if you start with an engine. I still think since your eventual goal will be an MMORPG or an ORPG you should stick with Unreal4. Learn to do little things in unreal while at the same time programming some small games like pong/breakout from scratch. Once you're comfortable programming go all out in learning Unreal. Another thing you can do is study other peoples source code to accelerate you along the path. Tangletail gave you some links and I'm sure if you're eager you'll dig into them just fine.

So he'll have to switch to C++, even though third party software DOES support C#, it might not always be up to date.

What do you mean switch, I thought he didn't know any languages yet? In addition any high performance server for a MMORPG and maybe ORPG will most probably be in C++ so it will most probably be better for them to go down a C++ path, which is Unreal. Also like I said previously IIRC unreal provides source where as unity does not so if there vision will require resource streaming if its not built-in they can add it. To me it seems the better choice since they are goal oriented, and can still do small from scratch projects in C++ as well. To me it looks like learn C++ and modeling programs is step 1, step 2 is get to know unreal slowly while doing smaller from scratch C++/SFML projects. Step 3 is if you feel comfortable at that point and some people might start working towards your goal in pieces. Maybe pausing to do other projects that concentrate on things that seem to complex when piled in with everything else. Step 4 is go all in on unreal and your goal. Step 3 is when they will realize what they are really getting themselves into, and have to decide if they want to continue with there goal. To them I say good luck.

I really should be writing this in my developer journal. But...

Creating an MMORPG is much like reading Hebrew Text. You do it from right to left. MMORPG == Massively Multiplayer Online Role-Playing Game. Let's start at the far right, shall we?

G is for game. How many have you made? How many have you finished? What types have you made? If the answers to those questions are synonyms to: None, Zero, Zilch, or Nada. Then your first and only step should be here. I wrote an article on suggested games to make. Assuming that you've heeded those suggestions. then that naturally leads us to the next question?

What RPGs have you made? Do you know what goes into RPGs? Are you familiar with: Scripted Events, Statistics, Databases, Files, Levelling Mechanics? Once you've figured all of that out, let's look at the next step.

O is for online. What do you know about: TCP/IP, UDP, Packets, Client-Server programming, Latency, and Lag? What networking libraries have you worked with? Will it be LAN or truly online, In the cloud?

M? Multiplayer for $200, Alex? You do know that whether it's LAN or Cloud play, you'll have to worry about maximizing security, synchronization, and coordination. As well as minimizing latency and lag. But at this point, you should be able to attempt to make a MUD.

M? What is Massively? Correct for $200! Remember that everything that you've done will be on a much larger scale. There will be load balancing, sign-ups, server costs, even more concern about security, synchronization, coordination, latency, and lag. By then, you'll need more than 2 people. With real experience. And honestly, it won't be massive. It'll just be bigger than small.

So there you have it. No classes needed. No step-by-step tutorial from beginning to end. Just treat the development process like Hebrew and in 5 to 10 years we should be enjoying your prototype.

Thanks for reading. Cheers!