Tweet
When superbroadcasts first came out, there used to be no cooldown - they were also relatively cheap, and they weren't a problem. Later on, as the community grew, you could see the SB price being increased in order to counter spam. Eventually, cooldowns were added, such as the 10 minute one which could be very easily skipped. All you had to do is switch the subserver you are on and you would be able to superbroadcast again - that's because it wasn't properly implemented as a playmod. That was until PAW 2019, when we finally see it being implemented as a playmod; meaning it's not possible to skip over the superbroadcast cooldown anymore. While this surely helps us combat spam, it appears to have caused an issue aswell. The superbroadcast block was now more annoying than ever - you could send a broadcast, but another player could just superbroadcast right after you to push your broadcast deep into the sea of nothingness. My suggestion is simple, and I believe would resolve this issue AND would help combat spam further.
Superbroadcast Queue System - how should it work?
Let's break it down to steps.
1. A player sends a superbroadcast using the /sb command.
2. A message is returned: "Your superbroadcast has been queued on spot [queue spot]. The player is still given a 10 minute cooldown, so he can't clutter the queue.
3. Every time interval, a superbroadcast from the queue is being released, and buries the previous superbroadcast in chat.
4. Everyone is happy. Jimmy doesn't get blocked, and everyone gets equal "air time" for their superbroadcast.
In other words, once you send a superbroadcast, it doesn't send instantly; instead you wait for your turn. Some things that need to be taken care of is that the time interval is not too high; you don't want to fill the queue. I believe a reasonable interval is 10 to 20 seconds. This way, I believe even in peak hours, players would have to wait about 10-15 minutes to get their superbroadcast actually sent. Mods obviously should be allowed to omit the queue. Make sure that the gem count is deducted when the superbroadcast is actually sent, not when it's queued, so that the correct amount of gems is taken from the player.
EDIT 1: About server restarts, I think once the server restart countdown begins, the sbs should no longer be sent. The sb queue should be reset as the server restarts, as no gems will be deducted until it actually sends the superbroadcast.
EDIT 2: Perhaps, the time interval would be somehow dependant on online player count or amount of superbroadcasts in the queue - the more superbroadcasts in the queue, the lesser interval to ensure all sbs are processed within a reasonable amount of time. If there's a hundred superbroadcasts in the queue, even a change from 15 seconds to 10 change of the time interval would be a major enough change to balance it out.
EDIT 3: A /cancelsb command to remove your sb from the queue, in case you have to urgently go and don't wanna have your gems wasted.
I think I listed everything. While this system may have some minor disadvantages, it may work up as a solution to the current issues. Feel free to discuss what you think of this and point out any horrible thing I may have not thought of at the time of writing this.
Superbroadcast Queue System - how should it work?
Let's break it down to steps.
1. A player sends a superbroadcast using the /sb command.
2. A message is returned: "Your superbroadcast has been queued on spot [queue spot]. The player is still given a 10 minute cooldown, so he can't clutter the queue.
3. Every time interval, a superbroadcast from the queue is being released, and buries the previous superbroadcast in chat.
4. Everyone is happy. Jimmy doesn't get blocked, and everyone gets equal "air time" for their superbroadcast.
In other words, once you send a superbroadcast, it doesn't send instantly; instead you wait for your turn. Some things that need to be taken care of is that the time interval is not too high; you don't want to fill the queue. I believe a reasonable interval is 10 to 20 seconds. This way, I believe even in peak hours, players would have to wait about 10-15 minutes to get their superbroadcast actually sent. Mods obviously should be allowed to omit the queue. Make sure that the gem count is deducted when the superbroadcast is actually sent, not when it's queued, so that the correct amount of gems is taken from the player.
EDIT 1: About server restarts, I think once the server restart countdown begins, the sbs should no longer be sent. The sb queue should be reset as the server restarts, as no gems will be deducted until it actually sends the superbroadcast.
EDIT 2: Perhaps, the time interval would be somehow dependant on online player count or amount of superbroadcasts in the queue - the more superbroadcasts in the queue, the lesser interval to ensure all sbs are processed within a reasonable amount of time. If there's a hundred superbroadcasts in the queue, even a change from 15 seconds to 10 change of the time interval would be a major enough change to balance it out.
EDIT 3: A /cancelsb command to remove your sb from the queue, in case you have to urgently go and don't wanna have your gems wasted.
I think I listed everything. While this system may have some minor disadvantages, it may work up as a solution to the current issues. Feel free to discuss what you think of this and point out any horrible thing I may have not thought of at the time of writing this.
Comment