| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |

Grey Area
|
Posted - 2003.09.01 21:46:00 -
[1]
Edited by: Grey Area on 01/09/2003 21:48:23 Why oh why did they remove the ability to use afterburners and MWD's in warp? It was our ONLY workaround for the "stuck on a 'roid/stuck on a station" bug, which, when it is in a 'roid belt, can often be fatal with the NPC's zeroing in. And why? "Potential Exploit" is the only explanation we are ever given, accompanied with the e-mail equivalent of a dark look, as if, in some way, we have brought this upon ourselves.
This collision bug has been in the game since day one, but do they make it a priority to fix? No. They concentrate instead on fixing a minor exploit (I mean it would be just AWFUL if someone came out 15km from the gate instead of the normal 30km, wouldn't it? ) at the expense of every player in the game who wants to test themselves against harder pirates, but who JUST might need the option to run away in a hurry. Now of course, you can't, so you just sit there spinning on your rock as the NPC's whittle away your shields. Petition for loss of your ship, and you are told "sorry, no compensation". It just adds insult to injury.
I beg of the Devs - one of TWO actions. Either allow us the use of our burners and MWD's again, or FIX that stupid bug. Daft decisions like this are ruining your product far more than any lame brained exploit EVER could. ========================================= * I'm ALLOWED to cheat. I'm a STARSHIP. * ========================================= |

Dyvim Slorm
|
Posted - 2003.09.02 12:45:00 -
[2]
Another way to fix this would be to allow a manual shutdown of the warp drive.
This really does need sorting out.
|

Sgt Drill
|
Posted - 2003.09.02 13:13:00 -
[3]
Yeah tell them.
YUou both have my full support on this.
Do something
|

Slip Low
|
Posted - 2003.09.02 16:22:00 -
[4]
Got my vote. Fix that.
|

Pretoria
|
Posted - 2003.09.02 23:06:00 -
[5]
This should be one of the priority for GM....
You have my vote, fix this bug and add a feature to shut down warping process.
|

Maximillion Eilerson
|
Posted - 2003.09.03 00:32:00 -
[6]
Pfff this sounds like a 10 minute fix that we'll have to do without for 6 months
|

sol man
|
Posted - 2003.09.07 21:45:00 -
[7]
thay have slowed eve down a lot. ok then can we have a butten so that we can fire up all our abs at once. i have 5 abs in my mammoth starting all at once would help or put the ****ing abs back to the way thay was or/and next time speek to the ppl who play the ****ing game to see wot thay think.
sol man ceo of sol man,s wave. sol man |

Rainiela
|
Posted - 2003.09.07 23:07:00 -
[8]
You got my vote. Nothing like being stuck in a roid field with no way out.
And while we are at priorities , can we please get huge and giant secure containers fixed. That way while we are getting shot at and destroyed while stuck in a time vacuum at least our produce will be safe and not poached.
|

voogru
|
Posted - 2003.09.08 07:20:00 -
[9]
All these bugs appear to be server side, they should be able to fix these bugs without requiring the client to download anything (If the server/client structure works the way I think it does).
Really, Could it be so much trouble to fix these minor bugs that cause major problems for players?
This has my vote, We pay for eve, now dev team, please do your job.
------- Your 425mm Prototype I Gauss Gun perfectly strikes Guardian Enforcer, wrecking for 827.3 damage. |

Dri Kulsane
|
Posted - 2003.09.09 07:42:00 -
[10]
I'm in on this...bit risky flooting there waiting for warp to get a kick in the arse
|

HeineB
|
Posted - 2003.09.09 08:36:00 -
[11]
I also agree with all above. But a little advice... just pay attention when you are out in a roid and you won't get stuck. :)
HeineB |

AEnikata
|
Posted - 2003.09.17 13:32:00 -
[12]
CCP, either put in some path-finding algorithms so that ships can find their way round asteroids, or disable the collision detection when entering warp - it may not be realistic, but it stops you having to 10 minutes before giving up, relogging, spending another 5 minutes or so finding a way to get away from asteroids or a space station, and then finally being able to warp. (Path-finding should be there, and would allow you to actually get to some cargo containers near debris, while disabling the collision detection to make warping occur immediately would be a quick fix that would make life a lot easier for everyone.)
|

Kazertraum
|
Posted - 2003.09.17 15:20:00 -
[13]
Another alternative would be to allow the afterburners to be used upon going into warp but disable the autorepeat on the AB's once warp drive is activated. This would allow you to escape the roid issues and prevent the exploit of warping right on top of a jumpgate.
|

StarLite
|
Posted - 2003.09.17 15:25:00 -
[14]
I also give my vote to this, I wonder why AB's got disabled during warping anyways, they saved me a lot of times while stuck in a roid again [well 8KM from a roid, but still stuck on it ] ___________________________________________________
|

Cordelia Matheson
|
Posted - 2003.09.18 08:20:00 -
[15]
Edited by: Cordelia Matheson on 18/09/2003 08:20:07 Yep - VERY important issue - my vote as well.
I'd prefer the disable warp-drive solution though. While I'm pretty sure someone will find some way to exploit that as well - like for getting closer to a gate - it also leaves a lot of the thrill of being in a roid belt, as you'd still have to find your way out to a clear position. But it certainly avoids being stuck on stations in transit or shot to pieces in belts without being able to do anything about it. And since - imho - the latter together with the no-reimbursement policy ( wich I accept ) will cost customers in the long run it should be high on the priority list.
Kind regards. |

Thardoz
|
Posted - 2003.09.18 10:54:00 -
[16]
Yes, that is definitalty one of the more annoying bugs that should be easy to fix. During prepping ship for warp you can be a sitting duck. I've been there - too close to a station waiting for 10 minutes at 1m/s to get the damn warp to happen. Even worse in an asteroid field with NPC spawning...
|

Tim Maser
|
Posted - 2003.09.19 03:36:00 -
[17]
I joined this game just after the afterburner warp thing must have been fixed. But by what I read a long time ago was that it was bug to begin with and everyone knew it would be gone soon. What you are asking is to put back in a bug for you to further exploit. That doesn't sound right, does it?
|

T'narg
|
Posted - 2003.09.19 17:58:00 -
[18]
An easy way to fix this would be to just turn off the colision 20secs after entering warp.
Its how I would of fix it if I was in a hurry.
-- Tnarg (XBox Programer)
|

Inquisitus
|
Posted - 2003.09.20 17:54:00 -
[19]
yeah this is a real problem and it must be fixed, or ur probably gonna get lots of angry players saying they've lost their ships coz of sum dum desiscion made by ccp 
|

Ezuriah
|
Posted - 2003.09.20 19:44:00 -
[20]
One time I got stuck leaving a station, I was there for half an hour looking at "WArp drive active" and my speed read "Stopped". If the "Stop my ship" option in the ship menu would disable the warp drive, I could've either re-docked or use AB/MWD's to reposition my ship away from the station. Instead I had to file a petition that I was stuck. After a GM sent me to another system, I saw a GM broadcast that the whole system I was in was a potential stuck hazard. It wasn't, it was just their damn oversight on this issue. The GM's really need to tell the Devs to do something about this issue. Either permit the use of AB/MWD's during warp or allow the warp drive to be disengaged by the player. It'll cut down on the number of stuck reports considerably.
The Keepers Alliance |
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |