MessagingService Release

[unmiss (Jack)]

I can’t access any of the pages regarding MessagingService, unfortunately…

[H_mzah]

For anyone who still wants to access it, here’s a cached version of the page from 3 days ago. Be aware the Limitations portion may have changed.

Main Developer Hub Page for MessagingService

Main functions for MessagingService:

SubscribeAsync
PublishAsync

[Prof_4K]

Could be the way the service is set up or a memory limit or something like that.

[r_r]

There appears to be a problem with limits. In a 1 player server, the limit for how many PublishAsync messages can be sent per minute is (currently):

Which computes to an allotment of 210 messages that can be sent per minute. However, I am currently sending 58 per minute, as can be seen by my PublishAsync usage print, which should leave me with 152 remaining PublishAsync messages that I could’ve sent in that past minute.

So despite the fact that I’m well below the documented limit, I appear to be continually throttled and my messages are not sending.

[Semaphorism (standalone_ecu)]

I can back this issue up, me and my friend were playing with it, and were hitting the limit way to quickly.

We may need to file a bug report.

[Thegameboy (Delfino)]

Do you have subscriptions to the same topic in other servers? This might have something to do with it:

MessagingService SubscribeAsync calls impact publishing rate limits

As the title states, prior to MessagingService’s public release I’m pretty sure that this hadn’t been the case as it seemed to only rate limit publishing. [image] In this case I’m publishing to a single topic with 2 other users subscribed to the same topic that are also publishing every other second on a single player server. It can be done slower however the more users that are connected to the same topic more time between requests are needed. Effectively when publishing and subscribed to t…

[inHeadspace (vee)]

This is still a major issue that’s preventing me from doing something that I’ve been trying to do; I was confused as to how I was hitting the rate by sending only 30-50 requests per minute. If this isn’t a bug, documentation on this behaviour would be pretty important.

[B_Ketchup]

I’ve seen publishes fail over 20 times consecutively in my game with near 2 minute long delays. This really needs to be acknowledged and fixed.

[CleverSource]

Can you both possibly provide code examples of what you’re attempting or what warnings/errors you receive?

[r_r]

The error I’m receiving is in my post, which is “The rate of publish requests exceeds the allowed limit”.

I’m using PublishAsync and am publishing to a topic 58 times per minute, and I’m listening to the same topic in the same server using SubscribeAsync. It isn’t problematic until I launch a second server, publishing to the same topic 58 times per minute, and simultaneously listening to the same topic, then I run into issues.

My code worked perfectly fine up until about a month ago, but when I resumed the project a month later, I ran into this error.

The “infinite player server” that @ForeverHD made also doesn’t work anymore. His game is open source, so I took a copy of it and observed that the errors in his game are the same errors I’m experiencing.

MessagingService: Creating an 'infinite player server'

Update: this no longer works with the recently imposed restrictions, although I’ll consider recreating something similar in the future to work with these changes. With the release of MessagingService, a wave of creations originally impossible to achieve have began popping up. Developers can now create global chatrooms, easily broadcast global announcements and setup basic match-making systems. However, out of all these, one particular concept really caught my attention: @Hanfian’s ‘infinite pla…

If you’d like to review the code that isn’t working, you can open studio for this game: Infinite Player Server (Open Source) - Roblox

There problem is definitely not within our code, and unless the documentation on the devhub is incorrect.

[CleverSource]

Thank you for the verification.

[Luk_ee (Luke)]

Omg yes! i can do great things with this in my models

[ForeverHD (Ben)]

Can confirm, I’m well within the limitations yet constantly receive error messages claiming the limit has been exceeded. All my ‘live leaderboards’ which worked originally have now failed completely.

@Seranok Do we have any time-frame to when this might be resolved?

[CarlPIandog (Carl)]

How could you create server wide announcements with this? I’ve no idea where to start as there aren’t many tutorials on this.

[Cruizer_Snowman (Badussy)]

I posted an example on how to use MessagingService/how it works. The game in un-copylocked so you can view all the code to better help your understanding of this.

[CarlPIandog (Carl)]

announcements no chat but I’ll look into it

[JamesBlossoms (James)]

Is this currently safe to use in a production environment, or should I steer clear?

[Semaphorism (standalone_ecu)]

Aside from the limit issues, you should be fine using it in production. As long as you don’t intend to use it based on the limits on the wiki.

[7kayoh (kayoh)]

This is very useful to me. I could make a fully global chat system which messages are synced with the whole game so players can see messages from other server.

Good job

[Seranok]

Hi Developers,

This feature now works in Studio, in all testing modes! This means you no longer have to publish your game to verify that it will work.

Note that MessagingService is fully partitioned between development and production, so messages you send in Studio will not be received in your production game and vice versa.