Dragonfly detected

[iZumo]

There is also a 0.75s fire interval between bender shots, thus it's 3.25 seconds => with same conditions plus adding likely user refire delay 0.25 per each shot, we get 3.5 seconds for a shot, so the final time is 17.5 seconds. Usually first shots are received before dragonfly gets in reach, from 1 - 2 shots depending on the location, which results in approx 11.5 - 15.0 seconds of active bomb time. Enough to give a killing hit even when the driver shields or have him waste two shields on your bombing.

Dragonfly isn't a Venom, you rarely miss it.

[darkelf]

Stopped reading here.

Really.. Azarael you need to calm down. Lets focus on something constructive.



@ Azarael: Yes I gave numbers that are not facts. Those numbers were based on average time it takes me to shoot down a dragon fly in sunshine while playing on the race server with a rather full server. I don't know the absolutes of the benders twin beams, and it doesn't really matter when you can't see the dragon fly or the time it takes to reacquire your target before shooting again. But lets move on. This argument isn't getting anywhere lets find a solution to a problem we all know that exist and needs to be fixed.


@ All: Azarael mentioned giving the hell bender projectile weapons and removing the instant hit type weapons from vehicles.(correct me if I'm wrong I can't quote what you said exactly.)

After I was thinking about it, it might not be such a bad idea if the twin beams were a Gatling gun of sorts. The only problem I see with that is that it would drastically change the game play of shooting other hell benders off with twin beams. But as I have seen with other vehicles in the nitro collection you could always give the twin beam different fire modes that can be selected via scrolling. I see this a decent compromise and may elevate the problem.

[bOnO]

Yes, something like twinbeams effective only against benders, and projectiles against dfly. Worths a try, if someone wishes to implement it.

[Azarael]

That's it. I'm sick of all this "No Dragonfly" bullshit that's going on in the voting system right now. Dragonflies deserve much better than that. Much, much better than that.

I should know what I'm talking about. I myself flew a genuine Dragonfly in StadiumRace V3 for 2,400,000 flight hours (that's about 100,000 days) and have been practicing with it for almost 2 years now. I can even bomb some of the best racers with my Dragonfly.

Izumo spends minutes working on a single Dragonfly and edits it up to a million times to produce the finest ragequit device known to mankind.

Dragonflies are thrice as powerful as Raptors and thrice as tough for that matter too. Anything a Raptor can destroy, a Dragonfly can destroy quicker. I'm pretty sure a Dragonfly could easily bisect a Solobender with full hp with a single well-placed bomb.

Ever wonder why noobs never bothered voting for Dragonfly versions? That's right, they were too scared to fight the disciplined pilots and their Dragonflies of destruction. Even in Sunshine, noobs targeted their fellow racers first because they simply didn't know what the hell to do.

So what am I saying? Dragonflies are simply the best vehicle that the server has ever seen, and thus, require better stats in the voting system. Here are the voting adjustments I propose for Dragonfly maps:

- NoDragonfly maps are underweighted to 0.4

Now that seems a lot more likely to prevent noobs from blocking Dragonfly maps because they can't be bothered to learn to play, don't you think?

tl;dr = Dragonfly maps need to be more easily votable, see my proposed changes.

[iRobot]

I wish I had stable internet to fly them properly. I'd be the best.

[bOnO]

The problem is not the DF; the problem is the vehicle to fight the DF. Maybe the Hellbender is bad, but the Atlas is not good. It feels like you're shooting darts against a tank... And since we have not even the choice, between HB and Atlas, no wonder nobody will vote a dfly map.

[iZumo]

That's it. I'm sick of all this "No Dragonfly" bullshit that's going on in the voting system right now. Dragonflies deserve much better than that. Much, much better than that.

I should know what I'm talking about. I myself flew a genuine Dragonfly in StadiumRace V3 for 2,400,000 flight hours (that's about 100,000 days) and have been practicing with it for almost 2 years now. I can even bomb some of the best racers with my Dragonfly.

Izumo spends minutes working on a single Dragonfly and edits it up to a million times to produce the finest ragequit device known to mankind.

Dragonflies are thrice as powerful as Raptors and thrice as tough for that matter too. Anything a Raptor can destroy, a Dragonfly can destroy quicker. I'm pretty sure a Dragonfly could easily bisect a Solobender with full hp with a single well-placed bomb.

Ever wonder why noobs never bothered voting for Dragonfly versions? That's right, they were too scared to fight the disciplined pilots and their Dragonflies of destruction. Even in Sunshine, noobs targeted their fellow racers first because they simply didn't know what the hell to do.

So what am I saying? Dragonflies are simply the best vehicle that the server has ever seen, and thus, require better stats in the voting system. Here are the voting adjustments I propose for Dragonfly maps:

- NoDragonfly maps are underweighted to 0.4

Now that seems a lot more likely to prevent noobs from blocking Dragonfly maps because they can't be bothered to learn to play, don't you think?

tl;dr = Dragonfly maps need to be more easily votable, see my proposed changes.

First, genuine Dragonfly (I understand "unedited" by that) doesn't bomb but has rockets. Second, last change on the Dragonfly is from 31.7.2012 (V7 - anti-lag). Third, isn't it entirely obvious by now how race & skill goes? No demand and if there is something that requires "slightly more skill" it gets a cold response. Even Dragonfly gets a spammy lolcar weapon although the main thing is to time your shield well (you have 10 repairs). Did racers learn how to dodge that properly over the long time that it exists? No. Period. End of story.

It has been elaborated a thousand times already, goddamnit. So no, don't really again come here with your moral qualities about how gameplay should be, you're damn too well aware what the people want and don't want and that how "pro" something is (map, vehicle) doesn't bother the racers. I'm completely dismissing your post.

The problem is not the DF; the problem is the vehicle to fight the DF. Maybe the Hellbender is bad, but the Atlas is not good. It feels like you're shooting darts against a tank... And since we have not even the choice, between HB and Atlas, no wonder nobody will vote a dfly map.

It actually has been elaborated in the thread back half a year ago, and moreless the conclusion was that with HB it was too easy. Thus as a whole it moved on toggleable shielding and you have 10 repairs to sustain bombing for the entire track.

[iRobot]

An above average flier can land 3 bombs in 10 seconds.

The objective roads take several minutes to complete.

Dragonfly respawn is rather quick.

No skill involved in dodging bombs, you simply can't.

Shield mechanic unforgiving when focusing on navigating or combating other vehicles.

I see why people don't play it.


sent from my iPhone

[iZumo]

Yes, dodging the bombs is impossible to design properly (hence StadiumRace V3 removal). You don't have to shield when fighting other lolcars (no push) and well focusing on both navigation and the bomber is the point.

Respawn is nearly instant, that sucks on last objective. (It takes a while to fly to the obj1 & obj2).

[iRobot]

You cannot shield solo and get bombed at objective should you reach it, when your gunner opens garage.

It's always the same.

I don't even play those maps anymore, lag too much to fly it and driving is just too weighted towards the DFs favour.


sent from my iPad