~~NOTOC~~
<=[[4rpl:start| Index]] \\
<=[[4rpl:start#mverse| MVerse]]

:!: Available in version 1.9 and later.

====== SendMVerseMsg ======
SendMVerseMsg(<-channel <-data)

===== Description =====
Similar to [[SendMsg]], except the message is sent to other clients in an mverse session. Note that the message will NOT be sent to client doing the sending. It is only sent to other clients. The data can be any 4rpl data type, including a list or a table. Care should be taken to not call SendMVerseMsg more than necessary or with more data than necessary since the call sends a message across the network to all clients.

===== Examples =====
<code 4rpl>
CreateTable ->table
"Larry" ->table{"name"}
42 ->table{"value"}
SendMVerseMsg("NetMessage" <-table)
</code>

<code 4rpl>
# Many 4rpl custom unit actions are not automatically synced in mverse. 
# For stationary units a possible solution is to send an mverse message 
# so that the other player sessions can create a clone of the unit.

<-unitType <-unitPos <-unitSettings createunit 0 SetMVerseCreatesUnitGhost
"MVMSG_CreateUnit" <-unitType <-unitPos <-unitSettings 3 listN sendmversemsg

:once
RegisterForMsg("MVMSG_CreateUnit" "MVMSG_CreateUnit_Function")
	
:MVMSG_CreateUnit_Function
<-_DATA[0] <-_DATA[1] <-_DATA[2] createunit 0 SetMVerseCreatesUnitGhost
</code>

See [[RegisterForMsg]]


<=[[4rpl:start| Index]]