RGL Discord PUGs Feedback

#74
Topic created · 19 Posts · 225 Views
  • This thread is for all RGL Discord PUGs feedback, such as map related ideas, general improvements or ideas, or feedback about any aspect of pugs.

    This is meant to be a very broad topic, so please feel free to leave any feedback here.

    Frequently asked Questions

    Can we spectate pugs through STV?

    We do not give out STV information at this time. Having too many people in the STV server can increase the load on the server.

    Why can’t we talk in Pickup-Waiting?

    We used to allow users to voice chat in Pickup-Waiting. However there was an incident with how people were acting when no staff members were around. This inevitably lead to us having to mute Pickup-Waiting in order to prevent these issues.

    Can I see my pug ELO?

    We don’t publicly share user’s ELO because the ELO system is constantly Changing. The ELO system is for pug runners to use for balance and making a publicly visible ELO system that users can interact with isn’t a good use of resources when we rather focus on improving the the ELO system and the overall pug experiance.

  • I think it would be cool to have an accessible STV server link for pugs so we can watch them while in pickup waiting, it would help give players something to do that is community related.

  • @BLANK3T said in RGL Discord PUGs Feedback:

    I think it would be cool to have an accessible STV server link for pugs so we can watch them while in pickup waiting, it would help give players something to do that is community related.

    This is something we’ve discussed internally. My main concern is every STV viewer adds strain to the server, so I want to be sure that we don’t have too many slots. But at the same time, if slots are limited then I feel like people would just be fighting over who can join.

    It is however something I can see if there’s firm testing being done as I don’t know the exact number of STV slots you have before there’s a noticeable impact.

  • Add some kind of completely meaningless currency (like Sigabucks or something) and let people bet on the winners of PUGs.

  • @LegendaryRQA I like this idea

  • @LegendaryRQA said in RGL Discord PUGs Feedback:

    Add some kind of completely meaningless currency (like Sigabucks or something) and let people bet on the winners of PUGs.

    I like the idea of pugbucks gambling however with stuff like this it’s important to think about implantation

    A. we do it on the server, which involves new mods and potential conflicts and issues.
    A.1. I actually have seen a mod like this in the wild but I can’t find it right now so if anyone wants to dm it to me.

    B. We do it in discord which would involve another bot, bot access would have to be limited to people in the game, and we’d need a bot that has good admin controls so we can lock who can use it and prevent spam.

    Not that I don’t love the idea of silly mods, but it’s important to keep the balance and implementation in mind.

  • There’s a Discord bug where sometimes a player can’t hear some (but not necessarily all) other players on their channel, though they in turn can be heard. Because it’s asymmetrical, it can be difficult to realize that it’s affecting you - more than half a pug can fly by before you realize that maybe no one’s hearing your callouts, which kind of breaks the whole point of the game.

    The bug seems to be triggered when A) auto-muting on the part of bots and B) potentially also transferring users between channels using bots.

    Until Discord fixes this (if ever), the workaround seems to be to limit the use of auto-muting and channel transfers using bots. To that end, I would propose leaving the BLU and RED voice channels unlocked during pugs so that users can manually join from the “Building Game” channel on their own (or leave and come back if the bug still manifests itself).

    There are two small drawbacks: Transferring users to their team channels automatically is faster and easier for pug runners, and potentially non-teammates might abuse this to join the channel inappropriately.

    However, given A) TF2 relies on effective communication, B) pugs are supposed to be taken seriously from a gameplay perspective, and C) the Discord bug can really ruin that aspect for players unsuspectingly, I think the drawbacks would be worth it.

    The first drawback introduces a little inconvenience and maybe 30 seconds of overhead to a setup process that is already 5-10 minutes long anyhow. The second drawback can easily be prevented by making a rule against it (and anyone who would violate such a rule to hamper the experience of pug players probably doesn’t belong here in the first place).

    This would also reduce the need for pug runners to manually step in and re-insert someone into the voice channel after having been made aware of the issue, which currently requires two players to engage in an idle state in the middle of an active game.

  • @Haytil said in RGL Discord PUGs Feedback:

    There’s a Discord bug where sometimes a player can’t hear some (but not necessarily all) other players on their channel, though they in turn can be heard. Because it’s asymmetrical, it can be difficult to realize that it’s affecting you - more than half a pug can fly by before you realize that maybe no one’s hearing your callouts, which kind of breaks the whole point of the game.

    The bug seems to be triggered when A) auto-muting on the part of bots and B) potentially also transferring users between channels using bots.

    Until Discord fixes this (if ever), the workaround seems to be to limit the use of auto-muting and channel transfers using bots. To that end, I would propose leaving the BLU and RED voice channels unlocked during pugs so that users can manually join from the “Building Game” channel on their own (or leave and come back if the bug still manifests itself).

    There are two small drawbacks: Transferring users to their team channels automatically is faster and easier for pug runners, and potentially non-teammates might abuse this to join the channel inappropriately.

    However, given A) TF2 relies on effective communication, B) pugs are supposed to be taken seriously from a gameplay perspective, and C) the Discord bug can really ruin that aspect for players unsuspectingly, I think the drawbacks would be worth it.

    The first drawback introduces a little inconvenience and maybe 30 seconds of overhead to a setup process that is already 5-10 minutes long anyhow. The second drawback can easily be prevented by making a rule against it (and anyone who would violate such a rule to hamper the experience of pug players probably doesn’t belong here in the first place).

    This would also reduce the need for pug runners to manually step in and re-insert someone into the voice channel after having been made aware of the issue, which currently requires two players to engage in an idle state in the middle of an active game.

    First, our bots don’t mute anyone. That’s handled by discord perms.

    I know discord has some issues that they haven’t fixed (discord mobile crashing on move is a longstanding issue) and this is almost certainly another discord issue.

    We can try manual moving, however I’m not doing the following:
    Leaving team channels open or removing the mute in pickup waiting. Both of these are counteractive to having a fluid pug progress.

  • let people talk in pickup waiting again 😧

  • @lay said in RGL Discord PUGs Feedback:

    let people talk in pickup waiting again 😧

    The short answer to this is no for moderation reasons.

    The long answer is that some time ago there was an incident with how people were acting in voice channels in the discord when no staff members were around. RGL has minimum standards of behaviour for the discord and various other spaces. What was happening is this standard wasn’t being maintained. This lead to sitting out being muted.

    And at this point I will fully say that pickup waiting should have been muted at the same time as sitting out, and the fact that we didn’t do that created unrealistic expectations for the community, and I’m sorry about that.

    More recently after coming off of a hiatus, we reviewed moderation stuff internally, and decided that since pickup waiting is not always moderated (much like sitting out) the mute should be applied.

    I understand that people miss talking in pickup waiting. I miss talking in pickup waiting with puggers. But I’ve looked at it from a few different angles and I think this is the most consistent solution we have right now.

  • It’d be nice to have a sticky on guidelines for newbies. Like “disable your in-voice chat and only chat through discord,” something like that. Maybe there already is one and I’ve not seen it.

  • @darzie maybe i’m lacking some context here, so apologies if that is the case. But as long as the expectation among players is that they can report inappropriate conduct in the vc, is it not fine to just let people talk? there may be a gap in time between the offense and action but local mute exists.

  • @ire The problem lies in evidence. We need to make sure our own actions are supported by reasonable evidence. Moderators hearing things vs people saying that someone said something are very different. Its very legal like, but it helps prevent un-necessary scrutiny.

  • @Psycho said in RGL Discord PUGs Feedback:

    It’d be nice to have a sticky on guidelines for newbies. Like “disable your in-voice chat and only chat through discord,” something like that. Maybe there already is one and I’ve not seen it.

    This is something that has been discussed before, and there was an early version of this written at one point. If there’s more interest I can look into finishing it. My main concerns are not wanting to overwhelm people with too much information and where exactly to put it. Pinned messages don’t always get checked but that said their probably isn’t harm offering more information if people want it.

  • Start some 6s pugs as late night PUGS. Even if I am not a 6s player, i think it can be fun.

  • If we could not play bagel that would be great. The map is boring as all hell, and all the cool shit is just not anywhere stuff actually happens

  • @narwool said in RGL Discord PUGs Feedback:

    Start some 6s pugs as late night PUGS. Even if I am not a 6s player, i think it can be fun.

    At this time we’re not hosting trad6s outside of special events.

    We’re also not hosting NR6s due to it having no upcoming seasons scheduled.

  • @Xenagos said in RGL Discord PUGs Feedback:

    If we could not play bagel that would be great. The map is boring as all hell, and all the cool shit is just not anywhere stuff actually happens

    Tossed you a discord dm link to the map feedback form (it’s also in the #pug_information channel). Posting here is fine but form makes it much easier for us to look back on. We review exp pug maps periodically.

  • Why can’t we see our ELO?

    I know a lot of people want to see their pug ELO but to be blunt, it’s not for public consumption. The ELO system is there to guide our balancing, but I wouldn’t say it’s refined where people would enjoy seeing their ELOs-the scale we use can change over time, and we also continuously adjusting ELO as how often one plays pugs may not keep up with the pace at which their skill increases. This can also lead to ELO being controversial, and simply put: if the system is working internally then I’m less concerned with how it scans publicly. I also don’t think that right now, making a palatable public ELO system is a good use of our time, when refining how pugs work is more important. It’s also worth noting our ELO system receives updates in how it functions completely, so keeping the scale updated properly would also be something that we would have to work on, when again I think there’s better uses of time.

Log in to reply