| Pages: 1 2 [3] 4 :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
ArmaggedonPSA
Minmatar
Royal Hiigaran Navy
   |
Posted - 2009.08.01 19:50:00 -
[61]
The GM's show up to kill you...then wish you a speedy recovery 
Dude I hoped you flipped the **** out on them in local or on the petition...That even ****ed me off 
------------
Join RHNVY Today! |
Johnny Gurkha
Repo Distribution and Salvage
|
Posted - 2009.08.02 00:46:00 -
[62]
Op owes me a new USB keyboard, I dribble/choked my coffee out laughing at the part the GM showing up 
|
Gunnanmon
Gallente
UNITED STAR SYNDICATE
|
Posted - 2009.08.02 00:56:00 -
[63]
A bug...in Eve? Bah, please don't question them moderating you out of a ship. And a couple of isks.
Signature locked for discussing moderation. Navigator
|
Greg DaimYo
Caldari
Biotronics Inc.
Majesta Empire
|
Posted - 2009.08.02 00:58:00 -
[64]
T3-Ships are bugged to hell and back atm.
We managed to blob an Ev0ke-Proteus in P3 a few days ago. He went boom on the IPAY-Gate... except for the fact that he didn't. The ship remained there until after the next downtime.
Character was offline for an eternity. Yet nothing happened with the ship. Me and about 10 other greedy bastards were sitting at the ship for about an hour waiting for it to pop. Nothing.
Sucks a bunch if you ask me.
|
Ore Tycoon
|
Posted - 2009.08.02 01:29:00 -
[65]
So CCP release buggy ships which die as a result of thier own fault - and you don't get reinbursed? I'm sorry but what planet are they living on? How does that logically make any sense at all? Am I taking crazy pills? This absolutely laughable!
If they did this to me I'd cancel 2/3 of my accounts.
|
Nyphur
Pillowsoft
Total Comfort
|
Posted - 2009.08.02 09:46:00 -
[66]
Edited by: Nyphur on 02/08/2009 09:50:43
 Originally by: 5pinDizzy
I know a few other people encountering similar problems to the OP.
Recommend avoiding tech 3 ships for now if you don't want to take any risks, buggy pieces of crap till a few creases are ironed out.
Avoiding T3 entirely is going way overboard, this is a very specific bug that only occurs when you die while logged off. The OP's account of the scenario was misleading in that they claimed it happened during normal use of the ship while warping out of a mission. In truth, they must have quit to try and emergency warp and died while logged off. Just don't quit to try and save your ship and you'll be fine.
Originally by: Ore Tycoon
So CCP release buggy ships which die as a result of thier own fault - and you don't get reinbursed? I'm sorry but what planet are they living on? How does that logically make any sense at all? Am I taking crazy pills? This absolutely laughable!
It's not that the bug causes the ship to be destroyed, it's that the bug occurs when the ship is destroyed naturally. For it to occur at all, the ship has to have been killed through normal gameplay. The fact that there's a ghost ship left behind makes it SEEM like your ship wasn't meant to be destroyed but it definitely was, you'll get a screwed up killmail for it and everything. More to the point, why would you expect a reimbursement for a loss that was your own fault and not the result of a bug?
|
Ore Tycoon
|
Posted - 2009.08.02 10:02:00 -
[67]
Edited by: Ore Tycoon on 02/08/2009 10:03:00
Originally by: Nyphur
Edited by: Nyphur on 02/08/2009 09:50:43
Originally by: 5pinDizzy
I know a few other people encountering similar problems to the OP.
Recommend avoiding tech 3 ships for now if you don't want to take any risks, buggy pieces of crap till a few creases are ironed out.
Avoiding T3 entirely is going way overboard, this is a very specific bug that only occurs when you die while logged off. The OP's account of the scenario was misleading in that they claimed it happened during normal use of the ship while warping out of a mission. In truth, they must have quit to try and emergency warp and died while logged off. Just don't quit to try and save your ship and you'll be fine.
Originally by: Ore Tycoon
So CCP release buggy ships which die as a result of thier own fault - and you don't get reinbursed? I'm sorry but what planet are they living on? How does that logically make any sense at all? Am I taking crazy pills? This absolutely laughable!
It's not that the bug causes the ship to be destroyed, it's that the bug occurs when the ship is destroyed naturally. For it to occur at all, the ship has to have been killed through normal gameplay. The fact that there's a ghost ship left behind makes it SEEM like your ship wasn't meant to be destroyed but it definitely was, you'll get a screwed up killmail for it and everything. More to the point, why would you expect a reimbursement for a loss that was your own fault and not the result of a bug?
That's not consistent with what the opening poster stated. He was in a mission and warped out, he was not tackled. He ever arrived at the station and had docking permission accepted. No rats or anything around him that could kill him. It's only when docking rights are accepted the bug kicks in and things go haywire. I'd be interested to know how you think this is his fault when he warped out of a combat area? Please tell me what killed him because as he said he was at the stations, how on earth is the loss his fault?
So no proper loss mail, warped out of a mission area to the safety of a station, asks for help, gets 'taken out', he loses all of his skillpoints and cannot play the game at all, then has to wait to see if everything is corrected at the next downtime. You're sitting there and telling me how a bug played no part in his loss and how all the above doesn't mean he should get reinsbursed? What planet are you from?
|
Venkul Mul
Gallente
|
Posted - 2009.08.02 10:26:00 -
[68]
Originally by: Ore Tycoon
That's not consistent with what the opening poster stated. He was in a mission and warped out, he was not tackled. He ever arrived at the station and had docking permission accepted. No rats or anything around him that could kill him. It's only when docking rights are accepted the bug kicks in and things go haywire. I'd be interested to know how you think this is his fault when he warped out of a combat area? Please tell me what killed him because as he said he was at the stations, how on earth is the loss his fault?
You are aware that those are the classical desinc symptoms?
The OP PC and the server weren't speaking. The OP ships was probably already dead but his PC hadn't got the information. And the same happened for the T3 bug. The server didn't get a reply with the PC computer about the loss of SP and the bug happened.
We are in summer, most IP work worse as resources are shifted to cover vacation spots and there is less personnel for the maintenance, so lag in transmissions and momentary disconnections are more common.
OP was unlucky and it is possible some fault in the communications caused her ship death (she speak of suddenly getting a lot of damage), but even that probably can be tagged to the server-player PC communications and not to a specific game bug.
Originally by: Ore Tycoon
So no proper loss mail, warped out of a mission area to the safety of a station, asks for help, gets 'taken out', he loses all of his skillpoints and cannot play the game at all, then has to wait to see if everything is corrected at the next downtime. You're sitting there and telling me how a bug played no part in his loss and how all the above doesn't mean he should get reinsbursed? What planet are you from?
Earth. Where we don't have perfect and instantaneous communications across thousand of light years.
|
Marlona Sky
D00M.
Triumvirate.
|
Posted - 2009.08.02 10:39:00 -
[69]
Edited by: Marlona Sky on 02/08/2009 10:40:49
Originally by: Nyphur
Avoiding T3 entirely is going way overboard, this is a very specific bug that only occurs when you die while logged off. The OP's account of the scenario was misleading in that they claimed it happened during normal use of the ship while warping out of a mission. In truth, they must have quit to try and emergency warp and died while logged off. Just don't quit to try and save your ship and you'll be fine.
I gave a 100% account of what happened on my end of the event. Granted I tried to make it slightly entertaining for the reader and did a poor job for some people is one thing. But the facts I stated are true.
If you want to have an opinion on this matter is one thing but saying I am lying about the event is un-called for.
I have lost many ships while playing this game, I have no need to attempt to lie on the forums to generate sympathy in getting ONE ship reimbursed to me by CCP.
I am simply sharing with the rest of eve community and trying to inform them of this bug.
Your accusation of me lying is childish. Go back to your playpin and play with your dolls.
|
Nyphur
Pillowsoft
Total Comfort
|
Posted - 2009.08.02 10:41:00 -
[70]
Edited by: Nyphur on 02/08/2009 10:45:02
Originally by: Ore Tycoon
That's not consistent with what the opening poster stated.
I know, I'm saying the opening poster is mistaken about the course of events he described. With all due respect to him, I've had first hand experience of the bug and I'm 99% certain that he logged off rather than just warping out. I've experienced the exact bug he's describing, reproduced it accurately on the test server and submitted a detailed bug report on it. The only occurances of the bug I've seen documented and the only way I could reproduce it was by being logged off when the killing blow came. In fact, I just re-tested it on sisi 5 minutes ago and it's still the case.
The actual process goes like this: You log off and while logged off, your T3 ship is blown up. But when the killing shot hits, the death process is interrupted (probably at the subsystem skill loss routine). You get a killmail for the ship containing no items destroyed or dropped, no wreck is produced and your ship remains as a kind of ghost ship. You can warp, access the cargo hold and a few other things but you can't target anything, be targetted, use stargates, use wormholes, activate modules or dock. When the bug occured for me the first time I didn't know anything was wrong until I tried to use a wormhole. In the case of the OP, he didn't realise anything was wrong until he tried to dock. That doesn't mean docking caused the bug, it means the bug caused the docking issue. What killed him was the mission he was in, he was dead before he warped out and got to the station.
|
Marlona Sky
D00M.
Triumvirate.
|
Posted - 2009.08.02 10:43:00 -
[71]
Originally by: Nyphur
Originally by: Ore Tycoon
That's not consistent with what the opening poster stated.
I know, I'm saying the opening poster is mistaken about the course of events he described. With all due respect to him, I've had first hand experience of the bug and I'm 99% certain that he logged off rather than just warping out. I've experienced the exact bug he's describing, reproduced it accurately on the test server and submitted a detailed bug report on it. The only occurances of the bug I've seen documented and the only way I could reproduce it was by being logged off when the killing blow came. In fact, I just re-tested it on sisi 5 minutes ago and it's still the case.
The actual process goes like this: You log off and while logged off, your T3 ship is blown up. But when the killing shot hits, the death process is interrupted (probably at the subsystem skill loss routine). You get a killmail for the ship containing no items destroyed or dropped, no wreck is produced and your ship remains as a kind of ghost ship. You can warp, access the cargo hold and a few other things but you can't target anything, be targetted, use stargates, use wormholes, activate modules or dock. When the bug occured for me the first time I didn't know anything was wrong until I tried to use a wormhole. In the case of the OP, he didn't realise anything was wrong until he tried to dock. That doesn't mean docking caused the bug, it means the bug caused the docking issue. What killed him was the mission he was in, he was dead before he warped out and got to the station.
I will state as a fact I did not log off. Now, you may continue with your argument...
|
Nyphur
Pillowsoft
Total Comfort
|
Posted - 2009.08.02 10:47:00 -
[72]
Edited by: Nyphur on 02/08/2009 10:48:12
Originally by: Marlona Sky
I will state as a fact I did not log off. Now, you may continue with your argument...
Originally by: Marlona Sky
Your accusation of me lying is childish. Go back to your playpin and play with your dolls.
I'm not trying to call you a liar, in fact if the bug occured while you were logged in it represents a much more grave problem with T3. But all the evidence points to you having been logged off at the time you were killed, which in all of my tests has been the sole cause of this exact bug. I'm on Sisi right now on Old Man Star in a "ghost" Tengu if you'd care to come and test it out. I've even gotten the "docking request accepted" issue you described, it's certainly the exact same bug and the key factor for replicating it is being logged off while the killing blow occurs. If you can replicate the condition in any other way than being killed while logged off, file a bug report on how you did it.
Do you remember any other details about the event like session change timers, joining gangs etc? Session changing while being killed might also cause the issue but you'd need to test it.
|
LaVista Vista
Conservative Shenanigans Party
|
Posted - 2009.08.02 10:57:00 -
[73]
Nyphur, didn't we argue recently about how Apocrypha was the most awesome expansion ever with no bugs? 
I found this thread in Vuk Lau's GM cluster-****. And I must admit that if this is true, that's not good. 
|
Nyphur
Pillowsoft
Total Comfort
|
Posted - 2009.08.02 11:08:00 -
[74]
Edited by: Nyphur on 02/08/2009 11:13:33
Originally by: LaVista Vista
Nyphur, didn't we argue recently about how Apocrypha was the most awesome expansion ever with no bugs?
Pretty sure I said Apocrypha had less bugs than previous expansions, not that it had none. This is a very rare but completely reproducable bug. If I had to guess, I'd say it's probably a result of the process that causes skill point loss after T3 ship losses not being able to access the character's skill data. The most prominent and reproducable method of doing so is to log the character off before death.
Originally by: LaVista Vista
I found this thread in Vuk Lau's GM cluster-****. And I must admit that if this is true, that's not good.
The GM in this case didn't do anything wrong. It's not like they showed up and tried to kill a ship that wasn't meant to be dead. The T3 ship was destroyed in that mission and something interrupted the death sequence. It's the GMs responsibility to resolve that issue and kill the ship. The big problem in this case was a lack of timely follow-up and resolution but given the complication of the total skill loss Marlona suffered, I'm not surprised that it had to be escalated and took a few days to resolve.
Now that it's been resolved, the only remaining negative effect of the final outcome I can see is that if the death sequence had not been interrupted, half of the modules fitted to the ship would have survived and been dropped in a wreck that could have been recovered. The ship, subsystems and the other half of the modules that would normally have been destroyed should not be reimbursed. On the other hand, the pilot SHOULD have lost a level of one of the subsystem skills and didn't.
|
Marlona Sky
D00M.
Triumvirate.
|
Posted - 2009.08.02 11:13:00 -
[75]
Originally by: Nyphur
Edited by: Nyphur on 02/08/2009 10:48:12
Originally by: Marlona Sky
I will state as a fact I did not log off. Now, you may continue with your argument...
Originally by: Marlona Sky
Your accusation of me lying is childish. Go back to your playpin and play with your dolls.
I'm not trying to call you a liar, in fact if the bug occured while you were logged in it represents a much more grave problem with T3. But all the evidence points to you having been logged off at the time you were killed, which in all of my tests has been the sole cause of this exact bug. I'm on Sisi right now on Old Man Star in a "ghost" Tengu if you'd care to come and test it out. I've even gotten the "docking request accepted" issue you described, it's certainly the exact same bug and the key factor for replicating it is being logged off while the killing blow occurs. If you can replicate the condition in any other way than being killed while logged off, file a bug report on how you did it.
Do you remember any other details about the event like session change timers, joining gangs etc? Session changing while being killed might also cause the issue but you'd need to test it.
While in mission I determine that I will not be able to perma tank it.
I decide to warp to planet 1 so my domi friend can then take over tanking the mission.
By the time I align and hit warp I had started to bleed structure, but my rep module was still working.
When I land at the planet, I decide because I had taken some structure damage to dock and repair it before going back to the mission.
Station being in the same system as the mission, I warp to it to dock.
The first sign of something wrong is when you get that one or two seconds after you hear 'docking request accepted' crap, where you cant do anything, then it goes to black screen and loads the station.
I stayed at that frozen screen.
Now I will also point out that it was outside the station pre-docking thing that I was able to jet cargo, talk in different chat windows, leave gang, get reinvited to the same gang, blah blah.
Logging off or disconnecting from the server never occured until after I filed a petition. When I finally did decide to quit the game and log back in is when I appeared in station and there was a GM responce where said that I died and he put me in station with uber ibis as a ship.
That is when local started up with the, "Is it me or is there an unpiloted Proteus chilling outside the station?"
There was no session change timers before that time, and again I will state that being disconnected from the server never occured until after I was stuck on pre-dock and filed a petition.
|
LaVista Vista
Conservative Shenanigans Party
|
Posted - 2009.08.02 11:19:00 -
[76]
Originally by: Nyphur
The GM in this case didn't do anything wrong. It's not like they showed up and tried to kill a ship that wasn't meant to be dead. The T3 ship was destroyed in that mission and something interrupted the death sequence. It's the GMs responsibility to resolve that issue and kill the ship. The big problem in this case was a lack of timely follow-up and resolution but given the complication of the total skill loss Marlona suffered, I'm not surprised that it had to be escalated and took a few days to resolve.
The problem was communication. If the OP's description of what happened is true, then the communication was lacking.
CCP can learn something from Blizzard. If there's an issue like this which takes place, then the GM ought to convo the victim of the bug and hold his hand till the issue is resolved.
The GM did indeed do what he needed to do, blow up the ship. But the execution was poor.
|
Marlona Sky
D00M.
Triumvirate.
|
Posted - 2009.08.02 11:20:00 -
[77]
Originally by: Nyphur
Edited by: Nyphur on 02/08/2009 11:13:33
Originally by: LaVista Vista
Nyphur, didn't we argue recently about how Apocrypha was the most awesome expansion ever with no bugs?
Pretty sure I said Apocrypha had less bugs than previous expansions, not that it had none. This is a very rare but completely reproducable bug. If I had to guess, I'd say it's probably a result of the process that causes skill point loss after T3 ship losses not being able to access the character's skill data. The most prominent and reproducable method of doing so is to log the character off before death.
Originally by: LaVista Vista
I found this thread in Vuk Lau's GM cluster-****. And I must admit that if this is true, that's not good.
The GM in this case didn't do anything wrong. It's not like they showed up and tried to kill a ship that wasn't meant to be dead. The T3 ship was destroyed in that mission and something interrupted the death sequence. It's the GMs responsibility to resolve that issue and kill the ship. The big problem in this case was a lack of timely follow-up and resolution but given the complication of the total skill loss Marlona suffered, I'm not surprised that it had to be escalated and took a few days to resolve.
Now that it's been resolved, the only remaining negative effect of the final outcome I can see is that if the death sequence had not been interrupted, half of the modules fitted to the ship would have survived and been dropped in a wreck that could have been recovered. The ship, subsystems and the other half of the modules that would normally have been destroyed should not be reimbursed. On the other hand, the pilot SHOULD have lost a level of one of the subsystem skills and didn't.
The only problem that I have with the GM responce is after I confirmed that I would like the petiton escelated, that I noticed the loss of skill points and again the inablity to dock, move, ect. This was after the race by everyone in local to reboard the ship. My question is: After a petition is escelated, does any further reply to the same petition seen by the GM or is he no longer able to see it because it is sitting on a Senior GM's desk or something?
Also the lack of being able to file a second petition without deleting the original kept me from bringing up my new problem which was a result of the bug.
It is like being on a trip and when the car runs out of gas, you send someone to go get gas only to discover that you have a dead battery as well AFTER they have already left. (go ahead and pretend you don't have cell phones in this example please and you two were the only ones that were on this trip.)
Anyways, probably a bad example but you get the point.
|
Nyphur
Pillowsoft
Total Comfort
|
Posted - 2009.08.02 11:24:00 -
[78]
Originally by: Marlona Sky
Station being in the same system as the mission, I warp to it to dock.
The first sign of something wrong is when you get that one or two seconds after you hear 'docking request accepted' crap, where you cant do anything, then it goes to black screen and loads the station.
I stayed at that frozen screen.
Now I will also point out that it was outside the station pre-docking thing that I was able to jet cargo, talk in different chat windows, leave gang, get reinvited to the same gang, blah blah.
I had the same experience when I had the bug, except I was in a wormhole so couldn't try docking. Warping worked, I could access cargo etc but I couldn't use wormholes, target anything, activate modules, be targetted etc. When I replicated the condition on the test server 15 minutes ago, I tried docking and got exactly the same thing as you described. I could access my cargo, talk in chat etc but I couldn't rotate the camera because it was frozen in the "docking request accepted" state. I tried self-destructing and it destroyed the modules and subsystems but the ship itself didn't die. I then tried ejecting, which I couldn't do as I was "docking". After relogging, I was able to eject from the ship, which is now outside the OMS quafe station on the test server. Based on our combined experiences, I am 99% certain that you died in that mission and not as a result of GM intervention. If you check your killmail for the ship, it should tell you NPCs laid the final blow.
Originally by: Marlona Sky
Logging off or disconnecting from the server never occured until after I filed a petition. When I finally did decide to quit the game and log back in is when I appeared in station and there was a GM responce where said that I died and he put me in station with uber ibis as a ship.
That's probably the best thing they could have done, moved you to the station and taken the ghost ship. They should have moved the ghost ship though because not doing so allowed you to re-board it, which may have caused your problems with skills disappearing.
I believe you when you say you didn't log off but that's the only way I've ever managed to replicate the bug. Were you ganging anyone at the moment of death? I could test that.
|
LaVista Vista
Conservative Shenanigans Party
|
Posted - 2009.08.02 11:38:00 -
[79]
Originally by: Nyphur
That I can sort of agree with. I've only had a few complicated issues with GMs and every time they have more or less been "holding my hand" through it until it was resolved so I guess I've been lucky in that regard. The one complaint I'd have there was that there's no real indication that they're still there working on your issue. A few times I've just logged off in the middle of an issue being resolved because I didn't know if they were still working on it and 30 minutes had passed. A convo would probably be more appropriate for that.
You know, I have had one complicated issue. Here is what happened:
1. I put up a new POS.
2. I eject from my Obelisk, see it sitting there nicely at the POS and log out while a module is anchoring
3. I log back in a few minutes later and see my Obelisk traveling out of my POS at 1km/s
4. Petition in stuck queue and immediately have a GM response.
5. GM keeps trying to spawn me right nex tto my Obelisk, at no luck. Shortly after he can't seem to locate my Obelisk anymore
6. He asks me if it's cool with blowing up the Obelisk and replace it.
And well, that was kinda how it went down. It took about 30 minutes. At times it was slightly frustrating, which I think wouldn't be the case if I was in a convo with him.
|
Marlona Sky
D00M.
Triumvirate.
|
Posted - 2009.08.02 11:53:00 -
[80]
Edited by: Marlona Sky on 02/08/2009 11:54:10
I will say that I do not believe the GM killed me. The loss of HP was a result of him interacting with the ship trying to fix the issue.
I was in a gang with a Domi pilot and stayed in gang till I logged off after filing the petition.
I belive though we are starting to draw closer to a close on the real issue at hand which is how GM's go about petitions.
Have any of you played Chess thru the mail? I have not but you get the idea, I mail you a letter saying i move this bishop to this space. Then we both wait for the a couple days for the letter to arrive and for you to write your letter on what your next move will be.
Why don't GM's just open a convo with the person and save on all kinds of time. I probably did something to screw up his fix or something because while I am sitting there waiting for my petition window to open I am doing other things to try and fix my problem.
More or less it is just like when you are in an accident and the person that is trying to help you is talking to you the whole time, saying crap like, 'ok, i am going to move your arm now.' or 'dont move your leg' crap like this.
The current petition system seems like it is 10-15 years behind the curve. So because of this, or other factors involved I spend the rest of the day till down time unable to enjoy the game. Again it is just one day but still, it is just unacceptable.
And where is CCP about this bug? Shouldn't they state something on the forums like:
"Currently there is a bug where if you die while in a t3 ship you will have problems. Just file a stuck petition and wait for a GM and they will guide you thru the process. We are currently in the process of working on a solution and will do a hotfix or something asafp!"
I don't know, maybe I just think as a paying customer, we deserve better customer support?
Maybe the GM's do care as much as we do but don't have tools they need to do quality work? Time to stop by a hardware store and get the tools needed for the job?
And yes, I am mad because the more I think about it, the more frustrating it is on why a company continues to use a the wrong (outdated) tool for a job and keeps screwing it up when they have the ability to get a better one and do the job right.
Who is with me!!!! Yarrr!!!!!  
|
Nyphur
Pillowsoft
Total Comfort
|
Posted - 2009.08.02 11:57:00 -
[81]
Originally by: LaVista Vista
You know, I have had one complicated issue. Here is what happened:
My most complicated one was when I had an entire reactor farm skipping cycles and missing 50 hours product from every output silo, a combined total of a bazillion isk. The number of hoops I had to jump through and data I had to dig up was massive and the whole process took a few weeks and had to be escalated. Turned out they don't actually log silos, but they managed to prove the output was missing, reimbursed the losses and reccomended changes to log silo activity at POS from then on. But even after all that, I thought it was handled as well as could be expected. I mean it's their job to handle all these unexpected weird problems that crop up, that complex issues take a while to get resolved is expected.
Admittedly, having them convo would make it more responsive than the current system but I've always had good dealings with petitions, even the complicated ones that take weeks to get resolved.
|
LaVista Vista
Conservative Shenanigans Party
|
Posted - 2009.08.02 12:04:00 -
[82]
Edited by: LaVista Vista on 02/08/2009 12:04:44
Originally by: Marlona Sky
Have any of you played Chess thru the mail?
That's exactly the problem.
The communication aspect of CCP is really lacking. I have been discussing that lately a lot over my blog. It's quite symptomatic for CCP it would seem. And to be frankly honest, I think it warrants some serious consideration on the part of CCP.
EDIT: YOu can find my thoughts on CCP's communication over here.
|
Zurrar
Gallente
Epiphyte Mining and Exploration
Majesta Empire
|
Posted - 2009.08.02 13:58:00 -
[83]
i lost an astarte killing a proteus, he had to be officer fit.
we finally kill him and no wreck, its just setting there unlockable...
so i lost a 300m isk ship, for no loot...
|
Marlona Sky
D00M.
Triumvirate.
|
Posted - 2009.08.09 03:37:00 -
[84]
Update:
Finally recieved a Senior GM reply that was sortive asking, "So, tell me what happened?"
*sigh*
I hate having to re-cap everything AGAIN when everything is simply right there with the petion replies between me and the first GM I talked to.
Right now I am waiting for his reply...
|
Sari Ajantes
|
Posted - 2009.08.09 09:46:00 -
[85]
We curently have the same problem , with a bugged legion..
We are waiting for DT clearing cache files on client, etc ... will keep you informed
I can confirm this problem to everyone who has doubts!
|
Matt Simon
|
Posted - 2009.08.09 11:16:00 -
[86]
After reading this thread ive decided to not undock my very well fitted legion til ccp announces that the bug is fixed. winther expansion ftw :)
|
Wasted Skillpoints
|
Posted - 2009.08.09 11:35:00 -
[87]
Wait, why was T3 introduced in a way that only carebears would actually be interested in making the ship?
|
Titan Pilot
Amarr
Imperial Academy
|
Posted - 2009.08.09 14:39:00 -
[88]
Originally by: Marlona Sky
So there I am, in my Proteus doing a mission
lol, you guys are hillarious. thx for making my day at work at little brighter. best tri post ever 
|
Marlona Sky
D00M.
Triumvirate.
|
Posted - 2009.08.09 14:44:00 -
[89]
Petition is now closed. Senior GM said that they hope to have this bug fixed in the next patch.
*shrugs*
Here is to the patch.
/me raises a glass
|
Kravick Drasani
|
Posted - 2009.08.09 19:51:00 -
[90]
This happened to me a year ago while in an Ares. Was camping a gate when 3 stealth bombers logged in and showed up at the POS my alliance was bashing. They maneuvered out of the bubble and cloaked up. They called me in to the POS to fly around with drones assigned to me to try and knock em out of stealth. Unfortunately I wasn't able too. All three bombers launched concussion bombs at the fleet and warped off to a gate. I attempted to follow but the bombs had already detonated with me in the detonation radius, but strangely I managed to enter warp anyway.
My ship had 0 HP across the board, but I was still in my ship and was now in warp with a flaming ship. I lost connection and when I logged back in I was in a pod, with 0 HP across the board. I was also at the stargate I had warped too and was completely unable to move or activate the stargate. I was also completely unable to use any chat windows and all my skill points where at 0 with no skill currently training. Even EVEmon registered I had no skill training. My petition fell on deaf ears as when I got an email response they said I had "failed to respond in game." None of my chat windows where working so if I had been contacted by a GM I wouldn't have known or been able to communicate back.
Problem ended up being fixed by the next downtime and I hadn't actually lost any skill points or training time.
|
| |
|
| Pages: 1 2 [3] 4 :: one page |
| First page | Previous page | Next page | Last page |