Hi! I am hoping to create an online-only multiplayer FPS army game. I am planning to have a main server that everybody connects to to join the game. Basically, my idea for the game is: -to have it be like the army, you start out as a private and have to work your way up -you get weekly wages(+extra for completing certain goals) to buy new weapons, gear, and to take training -have 2 or more armies to battle against each other I want one massive online multiplayer FPS. By that, I mean at least a few hundred people playing at once. I would create a server that would hold everybodies info; their rank, gear, amount of money, etc. Would a single computer be able to handle hundreds of people connected to it? Everything in the game would go through the server. I think my speed would be fine, maybe not enough bandwidth though... 8Mbps down, 1Mbps Up Finally, what protocol should I use? For now, I am creating the game in Blitz3D, which supports DirectPlay(directX), TCP, and UDP. I would maybe port it to BlitzMax for multiplatform support, but I couldn't use DirectPlay then. You could see the commands you can use for each here: http://www.blitzbasic.com/b3ddocs/command_list_2d_cat.php You can see that the Network, TCP, UDP, and DirectPlay command references are in a row. I think I remember reading that TCP at least can only handle 64 connections at once, which won't work. Thanks! Oh, and as a side thought, what port should I use? Since a lot of people have routers, are there certain ports that are open by default? -CoolProgrammer

He could mean simple hundreds of players use the server, not that each plays in one large session. UDP is the best choice for player movement, bullet vectors, just about anything that could lose a packet or two and still work. Things like character stats (health, ammo, etc) would maybe want to TCP so that is guaranteed to arrive in order so that you health doesn't jump around.

I think for now, I will create a very basic network program/game to figure out how to use UDP. After that, I will create a very basic multiplayer FPS. I actully already have one made that has one level. I will just modify that...

Quote:Original post by Windryder
DirectPlay is deprecated and nobody has used it for ages. Forget about that. You'll want UDP for this type of game. However, you may want to aim for a bit less than "hundreds" of players. The game you are describing borders to MMOFPS, which you, frankly, won't be able to make right now. Start out on a smaller scale (32-64 players, perhaps) and work your way from there.

Why wouldn't I be able to make one right now? Because UDP can't handle that many people, or I dn't know enought right now to make one?

Thanks for the links!

Oh yes UDP is capable, that's not the problem.

The complicated part comes with designing, implementing and maintaining an infrastructure that scales up to more players than from what a single machine can handle. That's in part what distinguishes a MMOG from a MOG, and what makes the former a lot harder to make.

Quote:I think my speed would be fine, maybe not enough bandwidth though... 8Mbps down, 1Mbps Up

Haha you make people lag like hell with such low upload in a conventional 10 player FPS server. :)

K thanks for the replies. I did some research on TCP and UDP and am trying to get a few computers(clients) to connect to my best computer(server) and send stuff back and forth for now. Then I will try to make a little more progress.

Just wondering, what service would I need to host a server that had around 100 people connected to it at once? Would a T1(1.5Mbps up/down) be good enough? I know the speed isn't that great, it's the bandwidth, which is what would need a lot of, right?
-CoolProgrammer

Quote:Original post by CoolProgrammer

Just wondering, what service would I need to host a server that had around 100 people connected to it at once?

100 people doing what?

The problem with this many people in a setting like FPS is quadratic load. Player 1 fires a bullet, and that info needs to be replicated to 99 other players. Now if 100 players fire a bullet, then each of the other 99 needs to be told about it.

This is the real problem why such things are hard to scale. There is MAG, but it's doing some really funky stuff, and apparently it causes quite some issues, such as person getting killed without opponent ever loading on their screen.

WoW gets away with it since each player can send one action per second or less and response can lag by a second or two. In FPS the update rate needs to be 10-30Hz.

Quote:8Mbps down, 1Mbps Up

Quote:Would a T1(1.5Mbps up/down) be good enough? I know the speed isn't that great, it's the bandwidth, which is what would need a lot of, right?

100 people moving, and each seeing each other at 10 Hz = ~(50 bytes per update * 10 * 100)^2 = 2.3 GIGABYTES per second. T1 is 16000 times too narrow for this. And this doesn't even take into consideration anything but movement, such as hit and damage information, various actions, and anything else interesting.

This is where things get complicated, since area of interest algorithms come into play, delta compression, etc... FPS is still limited to 64 players for this reason. Most of the time, it won't matter. It's the worst-case scenario that really ruins the day. This is why maps tend to be fairly spread or consist of in-door rooms, so that the chance of all 64 players coming into view of each other is minimized. But each of these compromises causes other problems, mostly with consistency.