Get rid of .dt commands

[FLOOB]

They are gamey. That is all.

[Zoney]

Sacriledge, gamey things in a game, the horror>  -1

[Wiley]

I'm not fond of them either although I don't feel too strongly about it, I'd give this a +1.

Consider this scenario.  One side has a a major object down at a field.  A player can time to the second when to begin his attack run on the hangar/ord/whatever just by spamming a .dt command.  It makes it easier for the attackers to keep the defenders objects down with smaller/virtually no window for stuff to sneak out whereas if there were no .dt commands, the enemy would have to see it to know it needs to be dropped.

If there were no .dt commands, they could be using a stopwatch, and some do.  That would require a level of commitment and presence over the area from the start, as opposed to flying to a base and using your MFD to determine and prioritize which targets are going to be available when you get there.

Wiley.

[bustr]

I never got the purpose for this. We have such a reputation for the fog of battle as our randomizer agent. Then boingggg, we get a precision timer for buff and jabo pilots to eternally crap on base defenders. I've been part of the M3 slobs who resupplied endlessly to get ords up just to have a buff box pass over 30 seconds later. Or the energizer bunny conga line of radar and VH hanger porkers who show up 30 seconds after either pops up.

This is kind of schizophrenic to the stated goal of this game, to promote combat.

The {dt} command promotes combat avoidance.

[Zoney]

Ya know, if they are using it to time when to hit it as soon as possible, you could use it to know when they were going to time their attack and.......................... .....

[lunatic1]

if only they could make the dt commands for your on country.

[cobia38]

if only they could make the dt commands for your on country.

 ^^^ this ^^^^

[Wiley]

Ya know, if they are using it to time when to hit it as soon as possible, you could use it to know when they were going to time their attack and.......................... .....

If you're in position, yup.  Hadn't thought of that I usually am just in a 'kill everything red over the base' frame of mind.  Still, it lets the attackers be surgical and you know as well as I do a jabocide requires a fair bit to go right for the defender to stop him.

Wiley.

[CASHEW]

+1

[DarkHawk]

How about we modify the request and only display friendly fields and not enemy fields.
Before we had the ability of displaying down time, we had to set a timer to determine when
a hanger would pop.

DHawk

[Zoney]

If you're in position, yup.  Hadn't thought of that I usually am just in a 'kill everything red over the base' frame of mind.  Still, it lets the attackers be surgical and you know as well as I do a jabocide requires a fair bit to go right for the defender to stop him.

Wiley.

That's a fact Jack!  But killing one 2 seconds before he drops is giggley fun.

[Lusche]

Let's just say I was very much surprised at the introduction of .dt that it was working on enemy objects...

[Cthulhu]

Let's just say I was very much surprised at the introduction of .dt that it was working on enemy objects...

No kidding.  This almost seems like bad coding that was never fixed. Frankly I think HTC should have addressed this two ways:

1) make .dt results available ONLY for friendly fields
2) introduce some randomness into the refresh time for objects that are destroyed. (Say +/- 20%)

That way friendly forces would know exactly when assets were available, but the enemy would have only a rough idea. Seems far more realistic.

[Wiley]

No kidding.  This almost seems like bad coding that was never fixed. Frankly I think HTC should have addressed this two ways:

1) make .dt results available ONLY for friendly fields
2) introduce some randomness into the refresh time for objects that are destroyed. (Say +/- 20%)

That way friendly forces would know exactly when assets were available, but the enemy would have only a rough idea. Seems far more realistic.

That's a nice idea.  I'd vote for it.

Wiley.

[waystin2]

No kidding.  This almost seems like bad coding that was never fixed. Frankly I think HTC should have addressed this two ways:

1) make .dt results available ONLY for friendly fields
2) introduce some randomness into the refresh time for objects that are destroyed. (Say +/- 20%)

That way friendly forces would know exactly when assets were available, but the enemy would have only a rough idea. Seems far more realistic.

You know making since around here can get you shot right Cthulhu?   +1