Supressing "kill messages"?

[Vedexent]

I'm wondering if there's a way to set the server - or in a mission file - so that the multiplayer server announcements - such as "PilotX has killed a Hummer with a Kh-25M"?

 

In missions that are trying to be as realistic as possible, this represents information you wouldn't normally have: did I get him. did I get the right one, what was he?

 

I don't want to disable the scoring system - although I'm not adverse to that if that's the way to do it - so I guess you could still keep peeking at your score to see if you got him, but I'd like to take out the announcments.

[ENO]

In the saved games / DCS / network.cfg change "disable events" to true.

 

 

 

server = {

disable_events = false,

client_params = "motd=\"Welcome to A-10C server!\";",

pause_on_load = true,

max_players = 32,

name = "DCS Server",

client_outbound_limit = 0,

client_inbound_limit = 0,

allow_object_export = false,

integrity_check = {

"Config/Weapons",

"Scripts/compile.lua",

},

}

[Vedexent]

Thank you very much :)

[camsr]

Yeah but someone using teamspeak can easily spread the word also.

[Vedexent]

If they've gotten close enough to positively identify the unit, and have confirmed they've made the kill, that's realistic too.

 

What I'm trying to avoid is situations where you're doing long range barrages, at a unit, knowing that one of those is an Avenger, and a couple are just Hummers, and then being told if/when you got the right kill.

[ENO]

It does add a good element of realism in that you need to verify kills. We tried it but guys got frustrated not knowing what killed them. It was a bit too much for our crowd so I turned it back on.

[VapoR]

Eno I think ED could solve this if they had some debriefing functionality in MP. Something like the SP debrief could pop up after you get killed but it would only show events related to you and not everyone else (so you couldn't cheat and see what the other side has done).

[Exorcet]

Eno I think ED could solve this if they had some debriefing functionality in MP. Something like the SP debrief could pop up after you get killed but it would only show events related to you and not everyone else (so you couldn't cheat and see what the other side has done).

I prefer having no information. The kill messages really spoil a big aspect of combat.

 

Perhaps this should be an option for individual selection. I'd like the messages off even if everyone else has them. I think it should also be a force-off option for missions, like disabling external views.

 

Of course in reality, there can be kill confirmation, but I feel that the godlike form we have now goes too far. The ideal would be improving the modeling of AWACS, command, and recon so that we could get realistic assessment. In the meantime though, what we have now feels like it comes from the game mode rather than the sim aspect of DCS.

[PFunk1606688187]

^ Agreed.

 

Sometimes I wonder why people who go full bore into hardcore simulation have such a hard time dealing with an absence of information. To me thats one of the best parts of it.

[ENO]

Some people go to decadent ice cream shops and order vanilla- or travel to France and eat at macdonalds. It's safe and familiar-

 

I wouldn't concern myself with other people's style of play or what they prefer. All manner of folks partake in all manners of playing style and nobody in this forum or anywhere else is in a position to judge.

[Exorcet]

Agreed, which is why I think this should be an option. If the server has kill messages enabled, then it's completely fair to use it. However, even in that case I would like to shut them off. Conversely if I was hosting a server, I'd like an easy way of disabling them (not that editing a file is all that hard, but I think the kill messages are on par with the mission options that we can switch on/off like external views).

[ENO]

100% agree. The option should be available in that fashion. In some cases it's up to the client and not forced but being able to force it off to suit the servers layout would be perfect.

Edited February 16, 2014 by ENO

[VapoR]

^ Agreed.

 

Sometimes I wonder why people who go full bore into hardcore simulation have such a hard time dealing with an absence of information. To me thats one of the best parts of it.

 

I gotta say I don't understand. Why would having a debriefing be unrealistic? I feel pretty certain that every pilot would be debreifed after every sortie. This is VERY different than kill messages in real time.

 

Even in the holy grail sim Falcon 4.0 you had a debreifing.

[Exorcet]

I gotta say I don't understand. Why would having a debriefing be unrealistic? I feel pretty certain that every pilot would be debreifed after every sortie. This is VERY different than kill messages in real time.

 

Even in the holy grail sim Falcon 4.0 you had a debreifing.

It would depend on the mission set up.

 

Typically online you crash, then jump into a new plane 5 seconds later. I have no issues with that, you're taking the role of more than one pilot.

 

The question is, what information is available to the new pilot. A plane was lost, you know when and where, but not necessarily why or how. If I was downed by an Igla that I never saw on my last flight, there is probably no way for anyone else on my side to know about the Igla. Someone will realize that a plane went missing over a certain area, and maybe mark the area as a threat, but no one is going to get a print out stating exactly what happened at the moment of impact.

 

I think the debrief idea is a good one, but simply making a debrief out of the all seeing kill messages may or may not fit the mission. I hope I'm not misunderstanding your idea.

[VapoR]

Just look at the SP debriefing screen, that's what I'm talking about.

 

If they took it further they could make the debriefing fairly vague, could just show you killed 4 vehicles and then got shot down by a surface launched missile for example.

[ENO]

It's a bit easier to determine how someone got shot down if briefing's are read and adequate. One of the things I know I struggle with as a builder is that I can have these long, rambling briefing's that describe every aspect of the mission and then I get complaints that they're too long. I cut them down and then people don't know what's going on. Funny enough some people complain that they don't know what's going on but didn't read the briefing anyway. Locking it up and forcing TS3 made that communication a bit easier since it was easy to update the folks who aren't interested in the briefing and just want to fly.

 

The alternative is to generate 1 mission every couple months with voiceovers that is complete in excruciating detail with printouts and full briefing notes and associated maps with threat indexes etc.

 

I have come to the conclusion for my purposes that I need to include slightly more detailed maps of threat areas. I haven't wanted to make missions too easy and I do want folks to work together to clear areas out before letting less defensible aircraft waddle into the zone to wave guns around. I'm having to rebuild a bunch of my missions to try and bring more information to the player so they have access to it... whether as a briefing tool or a debriefing tool. Ie: If you were in this area and got shot down by a missile, the resident threat was SA9/13. etc.