Excessive feedback?

[Deepsmeg 0]

Frostman and myself are having a slight argument about a new feature to the scud collection.

Frost wishes to include an error in launching, which will generate 17 sidechat messages over 35 seconds.

I think that that is too excessive for this purpose.

Would you lot like to play with an addon that gives such an invasive way of conveying information to you, even if it happens rarely?

[NL_Nemesis 0]

well me thinks it would also depend on what kind of info would be relaid would it be something like "this piece of russian crap wont start grab acup of coffee"

or something in the trend of "launchsystem mallfunction,diagnostics started" and then an update on the d.scan like firecontrol checked and the next igniter check .. missile clamp check andd so on and so on...

if thats the case then i think it could be less than 17...

[Deepsmeg 0]

It's pretty much "Clamps are locked. Something's armed the warhead."

It's something that could easily be shortened to 5 or 6 lines and put onto a better channel.

[uscg pilot 12 37]

idk both sound cool but the 35 woulkd be more realistic becuase if theres sumthing wrong then ppl will be chatting alot

[Deepsmeg 0]

but 35 seconds of a scud going

"I am broken"

"1001001001"

"001010100101"

[raedor 8]

it'd be pretty bad if i got new objectives incoming via radio... so some less are better.

[Silent N Deadly 0]

but 35 seconds of a scud going

"I am broken"

"1001001001"

"001010100101"

In that case...less messages is better.

[Dingmatt 0]

Well if were going to descuss this then lets look at the error as it stands.

_scud sidechat "Warning Error Detected... "

_scud sidechat "Error Code #23: Clamps Control Locked"

_scud sidechat "Error Code #52: Fuel Ignition Failure"

_scud sidechat "W$ÅNI~G.,? %RR&R"

_scud sidechat "Debug: UNKNOWN COMMAND"

_scud sidechat "1110000110110001011"

_scud sidechat "0110101100001101001"

_scud sidechat "0010011111101011101"

_scud sidechat "0010011101001001110"

_scud sidechat "0011"

_scud sidechat "ATTEMPTING TO RUN"

_scud sidechat "RUNNING....."

_scud sidechat "Systems Nominal"

_scud sidechat "Debug Complete"

_scud sidechat "Checking Launch Status: MISSILE LAUNCHED"

_scud sidechat "Warhead Status: SAFE"

_scud sidechat "CORRECTING"

_scud sidechat "Warhead Status: ARMED"

_scud sidechat "AirBurst Timed Detonation In:"

_scud sidechat "5"

_scud sidechat "4"

_scud sidechat "3"

_scud sidechat "2"

_scud sidechat "1"

I believe that some explanation is needed before nuke malfunctions.

Dingmatt

[DKM Jaguar 0]

Why does it have to say 101010010101 at all? Why not just have it pause for that amount of time?

[AKK 0]

Yeah I think need to know should only go so far. But It really depends on the "situation". I mean if s**t was hitting the fan around me the "error" display sequence would make me wanna toss my computer out the window. However if it was "dead" time I dont think all that error display would be that bad. I mean audio visual is the reason we ply the game.

[Deepsmeg 0]

In an MP situation, whilst this is going on you'd have a lot of team talk about getting as far away from the thing as possible.

[Tomislav 0]

i think the 17 sidechat mesages would be cool,

maybe introduce a script for a launch problem an let it explode on the scud, or give us the option to disarm the warhead during it is on it'S way to the target.

mfg

Tom

[Dingmatt 0]

The error feedback is warning to get as far away as possible... more txt then more time.