4rpl:commands:sendmversemsg
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 4rpl:commands:sendmversemsg [2024/10/06 13:33] – [Examples] kalli | 4rpl:commands:sendmversemsg [2025/02/14 14:57] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 21: | Line 21: | ||
| <code 4rpl> | <code 4rpl> | ||
| # Many 4rpl custom unit actions are not automatically synced in mverse. | # Many 4rpl custom unit actions are not automatically synced in mverse. | ||
| - | # For stationary units a possible solution is to have the unit send an | + | # For stationary units a possible solution is to send an mverse message |
| - | # mverse message | + | # so that the other player sessions can create a clone of the unit. |
| - | # of the unit. | + | |
| - | # In the custom unit script: | + | <-unitType |
| - | :awake | + | |
| - | self getunittype | + | |
| - | self getunitposition | + | |
| - | self getunitsettings | + | |
| " | " | ||
| - | # In a global script: | ||
| :once | :once | ||
| RegisterForMsg(" | RegisterForMsg(" | ||
4rpl/commands/sendmversemsg.1728221630.txt.gz · Last modified: 2025/02/14 14:56 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
