Known MooClick and MooSock issues in MMF2

So, as was my habbit in MMF1.5, I would like to inform you (if you dont know) about some troubles with MOO in MMF2. At first-it doesnt look like its MOO API fault, Yves already has the info.

Also the first thing (which could crach server side) -using action Delete socket on event On Recieved or similiar. The worst is that it wont crash everytime, but only occassional.

The second, similiar problem (MooClick) -dont use Player:Disconnect on On Server Message condition (On player message I havent tested). Caused crash everytime.

These both bugs are connected on the condition and werent present in MMF1.5 as well when you use other condition in MMF2. So if you have MooSock on the server side and encountered any strange crash, check this out..the same for MooClick

So, as was my habbit in MMF1.5, I would like to inform you (if you dont know) about some troubles with MOO in MMF2. At first-it doesnt look like its MOO API fault, Yves already has the info.

Also the first thing (which could crach server side) -using action Delete socket on event On Recieved or similiar. The worst is that it wont crash everytime, but only occassional.

The second, similiar problem (MooClick) -dont use Player:Disconnect on On Server Message condition (On player message I havent tested). Caused crash everytime.

These both bugs are connected on the condition and werent present in MMF1.5 as well when you use other condition in MMF2. So if you have MooSock on the server side and encountered any strange crash, check this out..the same for MooClick

Its annoying that the game will just crash with no helpful error message (eg, the extension which caused a problem and any other information, such as the event that it was last processing).

I still cant believe MooGame is so buggy, and since 3ee are MIA, it would be good if they just ended up releasing the source to the object so other developers could fix it.

I've just gone and implemented dead reckoning myself using events in MMF (no objects) which is working reasonably well.

Its annoying that the game will just crash with no helpful error message (eg, the extension which caused a problem and any other information, such as the event that it was last processing).

I still cant believe MooGame is so buggy, and since 3ee are MIA, it would be good if they just ended up releasing the source to the object so other developers could fix it.

I've just gone and implemented dead reckoning myself using events in MMF (no objects) which is working reasonably well.

Yep same. I get some really odd crashes with my game. Like when a second player joins the first (or second) instance will crash. Then i load up the game again and it works ok... One tester can't even play the game because it crashes everytime :P

I'll look into this though.

Yep same. I get some really odd crashes with my game. Like when a second player joins the first (or second) instance will crash. Then i load up the game again and it works ok... One tester can't even play the game because it crashes everytime :P

I'll look into this though.

Yeah..I dont have any other problems (no crash when I remove MooSock from the server side)-it runs for 4 days now with about 20 players at average.

Yeah..I dont have any other problems (no crash when I remove MooSock from the server side)-it runs for 4 days now with about 20 players at average.