MessagingService¶
Allows servers of the same experience to communicate with each other.
Not implemented yet
This class exists in the current Roblox API but is not implemented in Nova yet. Scripts that reference it will fail at runtime.
Description¶
MessagingService allows servers of the same experience to communicate with each other in real time, typically within 1-2 seconds, using topics. Topics are developer‑defined strings (1–80 characters) that servers use to send and receive messages.
Delivery is best effort and not guaranteed. Make sure to architect your experience so delivery failures are not critical.
Cross-Server Messaging explores how to communicate between servers in greater detail.
If you want to publish ad-hoc messages to live game servers, or publish across experiences, you can use the Open Cloud APIs.
Limitations¶
Note that these limits are subject to change.
| Limit | Maximum |
|---|---|
| Size of message | 1kB |
| Messages sent per game server | 600 + 240 * (number of players in this game server) per minute |
| Messages received per topic | (40 + 80 * number of servers) per minute |
| Messages received for entire game | (400 + 200 * number of servers) per minute |
| Subscriptions allowed per game server | 20 + 8 * (number of players in this game server) |
| Subscribe requests per game server | 240 requests per minute |
Inheritance¶
Object → Instance → MessagingService
Methods¶
| Member | Signature | Summary |
|---|---|---|
PublishAsync |
MessagingService:PublishAsync(topic: string, message: Variant): null |
Invokes the supplied callback whenever a message is pushed to the topic. |
SubscribeAsync |
MessagingService:SubscribeAsync(topic: string, callback: Function): RBXScriptConnection |
Begins listening to the given topic. |
Roblox reference: MessagingService
Generated from Nova's API dump and Roblox creator-docs. Nova-only members come from the engine's reflection metadata.