jacob404 / promod-future

GNU General Public License v3.0
7 stars 1 forks source link

Print tank to casters at round start #141

Closed jbzdarkid closed 9 years ago

HighCookie commented 9 years ago

If the config is trying to hide who tank is from the survivor team, showing the casters will just create a scenario where survivors will know who is tank either by watching the stream themselves or having someone tell them.

Personally I prefer full disclosure of the tank to both teams and spectators.

jacob404 commented 9 years ago

The only point of not printing who tank is to survivors is that i dont want a lame meta game of tracking what spawns die (oh bravo just died as boomer, but hes not their tank. push and spawn it now. etc etc)

MattNF commented 9 years ago

There's literally no reason the Survivor team needs to know who Tank will be

HighCookie commented 9 years ago

@Jacob404 I hadn't actually thought of that. That changes my stance on it completely.

@MattNF Reasons would include when you're playing against a team with one or two high ping players. A second reason is when you know the style of tank you are going against because you know the player.

MattNF commented 9 years ago

That's a good point, I never considered ping.

jbzdarkid commented 9 years ago

But people can stream snipe regardless, and I'd say that figuring out who's tank is much less devastating than figuring out hit location. Twitch has pretty low delay now, ~10sec or lower, depending on stream.

MattNF commented 9 years ago

I don't know if Kissme does it but I remember back in the day casters would delay their stream by like 5 minutes to prevent stream sniping.

jbzdarkid commented 9 years ago

Yes, just like every other competitive community. Or like SourceTV.

MattNF commented 9 years ago

Yeah. L4D2 comp is still behind everyone else! Though that's also Valve's fault for not fixing SourceTV for l4d.

rpdelaney commented 9 years ago

Reasons would include when you're playing against a team with one or two high ping players. A second reason is when you know the style of tank you are going against because you know the player.

Why not tell survivors who got the tank when the tank spawns, but not before?

MattNF commented 9 years ago

Why do you need to tell the Survivors who the Tank is so you can "know the style of Tank"? You should be ready and prepared for any "style" in any situation.

rpdelaney commented 9 years ago

@MattNF Maybe you don't. But like you, I also thought the point about knowing whether it's an HPB or LPB tank was plausible. Anyway, is there any harm in printing who is becoming the tank as they become the tank, but no sooner?

MattNF commented 9 years ago

Yeah, we don't need any more chat spam. Already feels like DLR with the kill stats that print in chat nearly every hit.

Anyway, I always assume that the Tank will have long arms regardless of who I'm playing. Not really worth the risk to assume otherwise imo. Plus I've seen long arms on low ping players too.

rpdelaney commented 9 years ago

I, for one, give no fucks about chat spam -- especially if it's useful info getting printed. I can't judge what popular opinion is on this aesthetic though. As to whether kill stats should printtoall, it's a different discussion imo.

MattNF commented 9 years ago

I care a lot about chat spam. Not only can it be annoying and distracting, but I think it makes the config look unprofessional, like DLR. Ideally, Promod should a framework that runs invisibly in the background and not be in your face unless there is no other option.

I mean, do you really need a chat print to tell you that you popped a Boomer? It's like, thanks I wouldn't have noticed otherwise!

Anyway, back on topic sorta, I suppose that since we already have a print that prints out when a Tank spawns, the print could be added to that same line in parenthesis who the Tank is.

jbzdarkid commented 9 years ago

Again, the point of this issue was casters, for whom it's not spam. If we had a more elegant system of telling the infected which one of them was going to be tank, we could use that same system for casters -- but we don't, so we use simple chat messages.

rpdelaney commented 9 years ago

Anyway, back on topic sorta, I suppose that since we already have a print that prints out when a Tank spawns, the print could be added to that same line in parenthesis who the Tank is.

That's p. much what my suggestion was yeah :^)

HighCookie commented 9 years ago

I just want to add that im with NF, i think the config should print as little as possible to chat to make it seem less like another modded server and more like l4ds definitive competitive mode.

jbzdarkid commented 9 years ago

Ok, so you're in favor of removing the "X will become the tank" print? If not, I'd like it show to casters, as well. As was OP.

MattNF commented 9 years ago

No, it should print to the infected team (and casters). But not survivors.

rpdelaney commented 9 years ago

But you're already printing something that says the tank is up. How is it more chat spam to add the person's name to the same message?

MattNF commented 9 years ago

Was that directed to me?

Because I already agreed that was nbd if added in the same line.

jbzdarkid commented 9 years ago

It's only a matter of when the information is sent; this is at beginning of round. I'm not sure it's necessary at all, but it does help the infected plan.

On Oct 15, 2015, at 3:24 PM, Ryan Delaney notifications@github.com wrote:

But you're already printing something that says the tank is up. How is it more chat spam to add the person's name to the same message?

— Reply to this email directly or view it on GitHub.