Jump to content


PC Member
  • Content Count

  • Joined

  • Last visited

Community Reputation


About mactrent

  • Rank
    Gold Novice

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I can confirm at least the first of the described problems. As of yesterday, Pyroclastic Flow triggers the 'kick' animation when it should, but no fire appears as it should in front of Nezha as he kicks. I haven't been able to confirm whether that fire is simply invisible, or if it's not spawned in the correct place, if at all.
  2. And the fact remains, when the bot does it, it is not. As noted in the original post, the vast majority of moderation actions are done by the bot. Perhaps most of those are warranted, and perhaps most of the unwarranted ones are only a brief kick and not a suspension, but it's not perfect, and mistakes will be made. The question is whether and how to improve on it. Reasons have been stated for why making [part of] the bot's configuration public might be an improvement, and reasons have been stated for why making [all/a large part of] the bot's configuration public might be damaging. Seems to me there's quite a bit of room for more transparency there without risking the stated downsides, but that's my opinion. That's how it should be, but this whole update to the chat moderation system became necessary because that was not always [perceived to be] the case, perhaps especially in recent months. The perception is important, so making visible changes is important. --- The fact that the changes to moderator selection, oversight and retention have stopped short of letting [some particular] old moderators go does not mean there wasn't improvement. The fact that there was improvement doesn't mean there's no room for more. Airing the past's dirty laundry in public has been tried, but DE has yet to respond to that, so it seems like a non-starter; we can only try to make sure future infringements of the [newly/slightly clarified] moderator code will be reported and acted on. Toward that end, I'll echo that the requirement for an opinion to be 'constructive' is just a little too broad to allow a moderator to disrespect a player for holding it. Let's place that particular bar a little bit higher, shall we? --- It seems important to note that the chat moderator page prohibits the moderator from doing certain things, such as using 'Any racist, sexist, homophobic, or transphobic terms', which puts the onus on the moderator to make blah-self aware of those terms. That's perfectly reasonable for a community representative. This same onus is on the players themselves in regards to race (where slurs and stereotypes are explicitly actionable), but not to this: ...so: if you're attacking individual players, you're gonna be moderated (duh) if you're making more broad malicious statements, against 'people that do/think <x>', you're gonna be moderated if you're knowingly bypassing the filters to try and say things that you know are slurs, you're gonna be moderated BUT if you just straight up say something that is considered (by whom?) to be a sexual slur, that's NOT on the human-moderation list That's a pretty big oversight, especially with recent events, to just gloss over. Please don't just leave it at "we said it's non-exhaustive" in regards to this. I think that 'sexual slurs or pejoratives' should also be on that list if there's gonna be moderation based on them (outside the context of attacks or almost-spellings). If that moderation is handled by a bot, instead of humans, that only solidifies the point. "Modified at our sole discretion" shouldn't mean "configured to enforce additional rules we didn't bother to tell you about." "Nezha is gay" is a useless and annoying thing to say, but doesn't match your current guidelines as actionable. "Traps are gay" is a stupid and hurtful meme, and should absolutely trigger the bot, if not human moderation. "A Gay Guy Plays" is the name of one of your partners, not a slur. "You are gay" is often meant as an insult, but "I am gay" is a neutral statement about oneself. If you're gonna have the word trigger the bot across all contexts, then at least include [potential] sexual slurs in the list of actionable items. Humans being over-zealous in defining what a slur is, is a problem. The bot being similarly over-zealous, with no feedback and with the only faintest idea of context, is a much bigger one. If you solve the problem of slurs by not addressing it, and secretly changing the bot, you do so at the cost of severe damage to your credibility.
  3. The sarcasm is unwarranted and unhelpful. You're on XB1, which probably has different norms, but practically nobody uses voice chat here on PC. Clan-mates use Discord or similar. Randoms using voice chat are extremely rare, and even more rare is for someone else to respond to them in kind. Usually if there's one person talking, there are at least two who only answer via text... which nobody banned from chat can read.
  4. I know random is as random does, and thanks for reducing some of the potential pain, but this particular change hasn't helped me at all. I have probably all the gyromag and even repeller systems I need from doing these bounties repeatedly (mostly the orb fight, feedback on that below), and I still don't even have enough Atmo systems to rank up to Hand with the Vox Solaris. And which rank do I have to be in order to buy them using my toroids (standing) in the first place? Bingo. Maybe make them available at different ranks, so that buying the systems you need for the next rank with standing is always a viable option? It gives a solid, achievable grind forward, with any drops you get from the bounties feeling like a bonus or boost, rather than a hard requirement. --- I do quite like the orb fight as it is now; the bounce-shields are easily avoided with constant vigilance, the staggers feel fairly reasonable, and I can usually avoid the need to hunt down a Fluctus-wielder to replenish my arch-gun. I still go with Nezha to protect myself from procs and staggers, and so that I can pop my arch-gun in the middle of the battlefield with relative safety. Regarding arch-gun ammo, I'm sure it's impossible to ensure there's always an enemy of a certain type available, with players mowing down so many of them in a short time. Possible solution: if my arch-gun is on cool-down when the orb is vulnerable, then highlight any arch-weapon ammo in the area, in case my teammates have already killed the muckers. Also, if there's a direct way to tell whether the orb's damage vulnerability type has been reset by a fellow Tenno rather than the damage or time maxing out, that could be a boon for saving communication in pub squads. I haven't been able to detect a difference in the visual effects while playing solo, but perhaps I just missed it?
  5. I think what various responses in this thread are missing is that the Tenno on Windows 7 pre-Service Pack 1 are running a version that doesn't get security updates anymore, just like Windows XP. Windows 7 with Service Pack 1, which is a free update that fixes far more things than it breaks still has security and stability updates for at least another year. I can think of no valid reason why a networked computer should have Windows 7 without SP1. Relatedly, DE is looking to end Windows XP support SoonTM, which will open the door for broader use of newer Windows APIs.
  6. I don't have a time-mark for you, but something @[DE]Glen said during his last Twitch stream made it sound like this was intended. Something like "I'm sure someone out there got lucky and already has an awesome Prisma Twin Gremlins riven." To be fair, that's just one way to interpret what he said.
  7. If that's still the case, mate, then make sure you 1) Logged on to Warframe in the past 7 days before Tenno Live and 2) Had your Twitch account linked to your Warframe. Alternatively, if you went to TennoCon, you should also have it now. If you did 1 and 2, or just TennoCon, then open a ticket on the support site, but this isn't the place to get that kind of help.
  8. You'll want to open a support ticket using the "Warframe Support" button that shows up in the forums. Link: https://digitalextremes.zendesk.com/hc/en-us That's assuming it doesn't show up after a relog. Best of luck!
  9. I love Limbo, and I wouldn't object to further nerfing this ability, if it came with more of the same QoL. It'd still be better than now, right?. I don't argue that Nidus' abilities should have double the duration, because they're good now. Same for Stasis, I've just got to get used to this different flavor of good. Notably, IMO it should have been the case since release that Limbo's non-Rifted allies could attack Rifted enemies. He doesn't need niche protection, he needs to be playable with any team. Many frames have underused abilities, but barring specific setups, most of those at least aren't a detriment to the team, they're just irrelevant. Limbo's current 1 and 3 in multiplayer are either a major boon in minor circumstances, or a hassle of varying magnitude. Adding Stasis' bullet freeze and/or limiting target selection as a draw-back for allies should only have been the case if those allies 1) intentionally opted into it and 2) also gained the benefits of it. Being unable to be attacked by, but also unable to attack with weapons, anything that Limbo has or hasn't brought into the Rift is not always (or in practice, even usually) a benefit, so that's out. Rift Torrent's effects come to mind as a good benefit that might tempt a player to opt-in to frozen bullets and/or a limited number of Rifted targets to shoot at. Everyone in the material plane should be able to shoot at anything - it's not their fault they got matched with Limbo, so don't let him keep their targets alive but unreachable. From Limbo's point of view, many of his targets are going to die before he can get to them. Even without Stasis freezing his bullets and causing a waste, he's going to have trouble maintaining his number of targets in the Rift. Currently, Rifted+Surged enemies spread the Surge to enemies around them when they're killed. I'd previously suggested having that spread a Banish instead, just like when Limbo Banish-bounces them to scoop the others in. That might be a bit much, so what if the Surge simply made it so Limbo can Banish them to the Rift, from the Rift. It'd be a lot like old Limbo, but would at least require the Surge. He's still got to start and maintain a chain, and he's still got to do the bounce within the duration of the Surge that spread to them, so it's not completely over-the-top.
  10. That would be the issue. This was a bug, which has been fixed in the PC version, but apparently not yet on consoles.
  11. Based on chronological order, it should be Chroma. They've been known to swap around a bit now and then, but that's a fair bet. I dunno about the weapons, though.
  12. I'm hoping this is the intention, but I am able to apply them to any other Warframe without spending plat on them. Thanks much!
  13. What the lady above said. 😉 Apparently not an issue of size, but of attachment point. They're working on it.
  14. Once in a blue moon, it's happened to me... 3 times in all this time, IIRC. Not even sure it was trolling in all those cases, though, which is the problem: it doesn't matter if he's intentionally trolling or not, any use of Rift Surge or Banish effectively has the same outcome unless we've planned on going with Limbo. There's always an enemy staring everyone in the face, that nobody has the ability or the inclination to kill. There's always some moment of confusion as the Surge spreads Banish to an enemy you were able to shoot a second ago, or you're just not able to visually identify which amongst the horde of enemies you're able to shoot. I dig your suggestion, but let me add to it: I think it'd be nice if Tenno could go in and out of the Rift at any time, whenever there's Rifted enemies nearby. Or even Rifted Limbo nearby, instead of having to search for a portal. Doesn't solve education or "suddenly unshootable, must Rift now" issues, but it's a step up from now. Other suggestions vary in complexity and scope, but I think we've agreed that changes to how other players interact with the Rift would be nice. Not in pubs, for exactly that reason. Banish and Rift Surge are troll-mostly powers on public, and communication-only powers on premade squads. You simply don't use these tools around other players. Forgive a little hyperbole, but that's pretty close to the practical reality. If Rift Torrent's damage multiplier applied to allies, then pre-made squads would at least have a reason to use it other than strictly for Limbo's benefit. A pre-made squad is, by definition, not usually trolling, so Limbo will be extra careful to let his allies access the Rift when they want. But that's still the exception for this power.
  15. The problem I was referring to was of enemies being placed out of reach, with the trolling by directly banishing a player as a minor (but topical) aside. Rift Surge is arguably more troll-able with a Cataclysm that you then drop. Cataclysm's range then becomes a non-issue - there's not any entrance to the Rift at all. That this is one of the best ways to play Limbo solo doesn't matter if it breaks all your teammates weapons relative to, well, just about everything they can see. And even if it was only a few enemies, is having them stand stock-still in plain sight, invulnerable to their weapons, still not an issue? I'm not attacking Limbo, here, I'm asking for his kit to not be so easy to troll with, and to be able to use his whole kit in some way without de-facto trolling, regardless of my intentions. Edit: I can't disagree with Banshee, either, though the augment change was a pretty nice step in the right direction - one that's allowing multiple players to actually play.
  • Create New...