(Maybe Bug) Odd MooClick Problem

[DizzyDoo]

I have an extremely odd problem with Mooclick. My program is just a simple connect, and then the player can send messages to each other. I then run two of them connecting to helper3000.net and they connect fine. A message successfully comes up when someone joins the channel or leaves it. However, when I attempt to send text to user... nothing happens. Here's my code:

+Player is moving
+Every 00"-20 seconds
-User send: Str$(X( "ME" ))+","+Str$(Y( "ME" )) on subchannel 1 to User

And the receiving events:

+Player on Message
+P_OnMessage_GetSubchannel( "MooClick" ) on subchannel 1 
+Alterable A of Remote-Player = PCU_GetID( "MooClick" )
-String Parser: Set source string to P_OnMessage_GetText$( "MooClick" )
-Remote Object- Set X position to Val(listGetAt$( "String Parser", 1))
-Remote Object- Set Y position to Val(listGetAt$( "String Parser", 2))

Very simple stuff, but despite good connections, nothing is received. The odd thing is, I run the same code in MMF1.5, and it works perfectly.

Ideas?

[Blizna]

Maybe something so silly than sending XY on time interval doesnt work?

Heh, anyway, you should send in on the channel, you send it to user which isnt specified here.

[Andrew]

Yes, you will need to select the user to send to on a certain channel before using the Send to User action.

[raytrace]

Why don't you use MooGame?

If not, you should make a type of dead reckoning and only check the positions if it fails

[DizzyDoo]

Oh sorry, yes, I have been sending on channel. I changed it to test if I was doing something wrong there.

Changed it back, but still not working. Okay, I've tried a chat application that did work but now doesn't... in MMF2 as well. What can I do?

[Blizna]

If you send to user, you have to specify which user you want send data to. You only need to use: Channel: Send text.

User is good for Usern join or events where you select user and then send to user.

[DizzyDoo]

Thanks Blizna, I'll keep that in mind, I still don't understand all events in Mooclick yet.

I fixed it! Finally, it was a stupid mistake of mine, sending the X and Y of a completely wrong object, and reading to another wrong one... Thanks to all who attempted to help.

[Blizna]

No problem, but think about better method, sending XY "every" will make your game laggy and high traffic when there are more players.

Examples: Send X,Y only when delta X,Y is greater

Grid. Send only when object reaches any other cell. Very nice method, you can easily change the size of cell and so handle with the "interval" of sending position (in small cells it will send more often and so)

Anyway, every method needs to have good dead reckoning..