The New Chat Restriction in The Feast

[Indicative]

PART SIX
CHAT RESTRICTION FLAWS

• Eliminates the ability to explain how the Feast works to new players. Without that ability it makes the PvP experience for NEW PLAYERS much WORSE. This is a critical flaw.
• There aren't enough buttons that you could make for all the scenarios and situations. Healing, MP, Medals, LB coordination -- there's too many things to make a reasonable amount of quick chat options. Instead of tying some abilities to chat macros and forcing players to hit more buttons.
• In regards to buffs, there's different distribution options. As a tank and if I'm confident that I'll be getting Medals, I can't explain that I'd like the defensive cooldown to mitigate the damage. As a Melee DPS I can't say that I'd like the defensive cooldown so I don't die when they focus me because I'm on the frontlines. As a Healer I can't tell the tank to not fight me for a defensive cooldown (has happened way more than I can count). Etc.

[Indicative]

PART SEVEN
SOLUTION
Honestly? You need to lift the chat restriction and punish toxic players. A quick report button, blacklist -- anything that would assist in that. Having the chat restriction makes the Feast a lot less fun because you have extremely limited communication. There's no way for experience PvPers to enrich newer players. Newer players don't have fun in the Feast because they don't know what they're doing and can't ask questions during the match. We also can't tell players they have USEFUL PVP ABILITIES.

I know some of the people reading this might be rolling their eyes and saying they shouldn't even be PvPing if they don't know what they're doing. That's fair, but ultimately that's not going to happen and we need to accept that.

Quick Chat buttons can stay. They help with the bloat from making macros. We could have more of these that would actually be nice and helpful.

(Also Holy crap I didn't know about the edit-post hax. Sorry for posting seven times!)

[Ama_Hamada]

You can edit posts to get past that, you never questioned how some made their posts so long?

[Indicative]

You can edit posts to get past that, you never questioned how some made their posts so long?

I-It never occurred to me. *sweats* I just woke up T_t

[Ama_Hamada]

Well now you know, hope i helped

[Kai_Lee]

Very nice post sylvie but if all the other reply doesn't convince SE, regardless of what anyone say I don't think SE would all of a sudden reverse their decisions.

[Ama_Hamada]

PART THREE
RANGED DPS

• Both Machinists and Bards can promote their turret/play songs respectively. I rarely use Bards use Foe's Requiem even if there's more than one caster on a team. I rarely see Bards and Machinists give MP to healers in PvP even if their MP is completely dry. There's no way to tell them that.
• There are a lot of newPvPers that don't realize that they have a OGCD button called Manasong. There's no way to communicate that button even exists.
• There's a damage efficiency based on range. This is INCREDIBLY IMPORTANT and a LOT of RDPS have no idea it's even a thing. There is NO WAY you can explain, in a quickchat macro, how it works and that it even exists. This is a very important thing that isn't very obvious and the game doesn't explicitly state it. Once again. There's no way you can explain this in a quick chat macro.

For the MCH, a lot of that has to do with the ability name "report" It can be confusing esp if someone is new what is being asked when they are asking for a "report" I honestly thought someone wanted someone else to report on something. VERY BAD naming choice for an ability.

[Mirateski]

I know there's a lot of input from people who are pvp vets, but I only started pvping with the Garo event so I thought I'd chime in with my thoughts?

I CANNOT STAND THIS CHAT RESTRICTION.

I've been in 8v8 matches because I'm scared to do 4v4 in case I fuck up and nobody can tell me. I recognise players who are bad at their job in pvp and can't tell my party to focus them because I've seen them before and they're bad. I can't tell the dps to leave the medals for me instead of getting ten stacks themselves. I can't tell the bard to get a defensive kit, tell the healer I'm going to cover them, let the party know I'll use lb during culling time (because like heck do I have room for macros, I barely have room for the pvp skills!)

I can't tell healers that PVE RAISE IS BAD. I HAVE HAD THAT REZ SO MANY TIMES. I HATE IT.

And like, the mode itself is super fun, I get really hyped but it's so frustrating to lose a match that I feel like I could have won if I had just been able to communicate. We're allowed to in frontlines and it works really well? Can you imagine frontlines with only "attack ice" "focus healer" "fall back!", it would be awful?

Please let me talk. I want to try ranked and improve, but I have no idea how to access anything other than asking my fc friends, who are ALSO all fresh to pvp, and we're all a bit lost here.

(Edit to add: I've been called all sorts of horrible names in PvE, so honestly I could handle someone calling me a shit tank in a ranked pvp mode if after the insults they gave me tips. I'm not a goddamn five year old.)

[Ama_Hamada]

You want to know why there is toxicity in PvP? same reason it exists in PvE, new people are not accepting to advice! I was trying to tell this person not to run in a group of 10+ flames alone, I even raised him and tell him to come back and he would not listen and went to die again, we lost a close game because of this. The reply I got of telling him to run back was "first time dont be a cuck" I then said "yeah i was telling you back up is there a problem?" (after he quoted me) then his reply: want there to be?


So you are going to take chat away because people can't take advice? Why not remove chat from PvE? same thing happens there.

[Isala]

So you are going to take chat away because people can't take advice? Why not remove chat from PvE? same thing happens there.

I've said it before, but the only time I've ever seen someone tell another player to "Die in a dumpster fire." was in a PvE instance.