You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#2497 introduced the ability to hide other players' spawned objects, which makes it so many previously unsolvable annoyances can be removed with a click;
players spawning vehicles and revving their engines or turning on sirens to cause noise pollution
players spawning vehicles with stereo sound (bug, engine sound is heard all over the map, no matter the distance to vehicle)
players spawning resource-intensive vehicles, not to enjoy them but to cause performance drops for everyone
players spawning large objects (e.g. a cruise ship) at spawn to obscure other players' views
players using live repair mode to destroy other players' cars with the sole purpose being to annoy them
generally disruptive behavior using spawnable objects/vehicles
This was a great addition and made it more difficult for a single person to ruin the multiplayer experience for everyone else, which usually resulted in genuine players ending the session and disconnecting.
Having participated in multiplayer sessions and having seen other players' reports, I've noticed some other behaviors that we could discourage/prevent by extending this functionality. Here are the current issues:
players sending disruptive/inappropriate messages in the chat or just spamming the chat
players de-spawning and spawning vehicles to get around others pausing their actors
players spawning vehicles very often, causing lag and performance drops
I am not sure what this would involve technically, and whether this issue should have been posted on ror-server repository instead of here, but here are some proposed solutions:
the ability to "pause" a player; this would prevent their objects from even spawning
the ability to "mute" a player; this would prevent their messages from being shown in the chat
This would give the player a temporary (for the duration of the session?) option of preventing a potential nuisance player from interacting with them, with no need for reports, moderation, or blacklists.
Potential flaws/ways to get around:
a muted/paused player could disconnect and re-connect
if this works by username, Player-3 who might be different people as they connect and disconnect (due to Player- username being recycled), might remain muted/paused even though they're not the person that was muted/paused
if this works by username, a muted/paused player could disconnect, change their username, and re-connect to continue being an annoyance.
Please let me know your thoughts on this - as with any "good, well-intentioned idea" there may be drawbacks, unintended negative consequences, or people finding a way to abuse it.
The text was updated successfully, but these errors were encountered:
MarkROR
changed the title
Ability to hide a player's messages and prevent their objects from spawning during a session
Ability to hide a player's messages and prevent their objects from spawning during a multiplayer session
Nov 5, 2024
I really like this idea, especially the "mute" function, it has happened to me several times that the chat was spammed with inappropriate/racist/disruptive messages, it's very annoying.
I know that ohlidalp was planning to add a mute feature.
As for a feature to prevent objects from spawning, I can see two uses:
Preventing players from spawing objects to annoy other players.
Allowing people to, for example, do serious roleplay or record videos in multiplayer with only certain players; without being interrupted by other players or having to make a private server.
However, there has to be a way (since usernames can be changed [as you mentioned] and UIDs are not permanent) to keep people from bypassing a mute.
One possibility is to mute/block by IP, which is harder to bypass, since you need a VPN to do so.
#2497 introduced the ability to hide other players' spawned objects, which makes it so many previously unsolvable annoyances can be removed with a click;
This was a great addition and made it more difficult for a single person to ruin the multiplayer experience for everyone else, which usually resulted in genuine players ending the session and disconnecting.
Having participated in multiplayer sessions and having seen other players' reports, I've noticed some other behaviors that we could discourage/prevent by extending this functionality. Here are the current issues:
I am not sure what this would involve technically, and whether this issue should have been posted on ror-server repository instead of here, but here are some proposed solutions:
This would give the player a temporary (for the duration of the session?) option of preventing a potential nuisance player from interacting with them, with no need for reports, moderation, or blacklists.
Potential flaws/ways to get around:
Please let me know your thoughts on this - as with any "good, well-intentioned idea" there may be drawbacks, unintended negative consequences, or people finding a way to abuse it.
The text was updated successfully, but these errors were encountered: