Tiny MooSock MMORPG example

[Anders]

This tiny example includes a server and a client.

To test it:
Unpack all files to a folder and build both .mfa files to .exe files. Run the server once and the client a few times.

This MMORPG engine features:
-Logging in and out
-Walking around w. point and click
-Chat
-Position correction for player movement when you just log in.

The last feature basically means that if someone starts walking to another position, a message will be sent to all players about the move. But if you log in while the player is moving normally no message would be sent to you about that player moving. Then server then sends you information about the player so the client can correct the player's position and make that player move from the position the player would logically be in.

Note:
This example is kinda insecure as everything sent is plain-text, and the server doesn't check for position cheats. That is up to you to add

[Johnny]

wow very cool system with moosock

[Patrick]

nice altough, i wouldnt call it a Massive Multiplayer Online Role Player Game

[Oly]

The Client and Server .exe files crash after I run them

If I click on X to close one, it crashes and I have to force quit. I don't know whats wrong.

[Anders]

Have you updated to the latest MMF2 version?

[Cocodrilo]

Nice Andos!

[Corentin]

Thanks for sharing Andos
Just a question, why did you use a "recv" fastloop ? I usually do it with a group of events, is it supposed to be faster this way (just like you stop your loop, i close my group as soon as possible) ?

You should add a ping timeout to this system !

[Anders]

Hi Corentin:

No I'm just fond of event based programming (not to be confused with MMF2 events).

If MMF2 has a "on function" feature I would use that instead for clarity, but I just run a fastloop once to do that.

I guess having a group to do that stuff would be faster but using those for anything functional isn't really my cup of tea. I just use them for separating events into logical groups.

[Werepeach]

it'd be nice if this was better commented, explaining exactly what's going on in the events. Especially for people are new to MooSock.

[Corentin]

When you loop through sockets to send messages or such, you don't have to start the loop countsockets times, countsockets-1 is enough. Of course, if you do this, you take the risk to start loop -1 time...