Forum Settings
       
This Forum is Read Only

Failing Guildleves due to crashes?Follow

#1 Sep 07 2010 at 8:52 PM Rating: Good
**
254 posts
Am I the only one that finds this really stupid? lol.

I just failed 2 guildleves in a row. Havent crashed all night, but soon as i start a guildleves and got 3/4 kills it crashes and i lose it for 48 hours. Makes no sense to me.

But how can they fix it? People will exploit the exp bonus if you can just fail and try again. Id suggest making it repeatable upon failure, yet removing the exp bonus on retry's.

Edited, Sep 7th 2010 10:52pm by Soezu
#2 Sep 07 2010 at 8:53 PM Rating: Good
***
1,636 posts
I think being able to retry leves would be nice, or even allow us to trade that one back in immediately.
____________________________


#3 Sep 07 2010 at 8:58 PM Rating: Decent
**
254 posts
Something needs to be done. Because losing your guildleve for 48 hours due to a disconnect or client crash is unacceptable. I just lost 2 in a row, 1 had a "Dalmatica" reward and I was excited to get it! Dalmatica was sick in FFXI with mp regen on it. I wanted to see if it had MP regen.
#4 Sep 07 2010 at 9:28 PM Rating: Excellent
Yeah the very first guildleve I was given, I go out to camp blackbrush, start it, and --blankscreen. I didn't actually crashed, I somehow managed to step on my computer power cord and unplug my computer! Ugh! So I start back up quickly, and try to log in. Error! Error that I look up and after about 10 pages figure out it means my character is still logged in - by the way, why the **** show us error codes if you're not going to tell us what they're for anywhere? Anyways, I can't get back in for a long time, and when I do, well guildleve failed. Well *that* sucks!

Now, having read up, I knew I could go finish the quest anyways, but that would start new people off on the wrong foot with a bad taste in their mouth, I'm sure.
____________________________
Die! Die die die. die die die die, die die. - Scarlet Briar
#5 Sep 07 2010 at 9:36 PM Rating: Good
Sage
**
770 posts
Hope they have a fix for it, it is quite annoying. or hope they stop the crashes hehe either way :) But i am lovign the beta ill add that.
____________________________
I do not suffer from insanity.. I rather enjoy it.

{retired} Devalynn Mithra WHM extrodinare -Garuda (gives everyone a high paw! yeah!)

Church OF Mikhalia
#6 Sep 07 2010 at 10:11 PM Rating: Decent
Scholar
40 posts
A little happy other people are having crashes tho, as bad as that is. More people the more likely it will be addressed.

Failed atleast 4 from 0x000005 crashes. Guess that's what beta is for tho right?
#7 Sep 07 2010 at 10:18 PM Rating: Default
**
254 posts
I'm loving it too, but ****. Really sucks losing a quest to a client crash or disconnect. Especially when it's on a 48 hours cooldown lmao. That's just the worste **** ever. I can live with the UI lag, but the failed leves from client crashes is a game breaker.
#8 Sep 07 2010 at 10:30 PM Rating: Decent
I was all excited because I picked up a rank 10 leve for Skull Valley that had a set of bronze chainmail as a reward. But first, I decided to do my crafting leves. Got a couple done...oh glee...and then went to do a low rank regional botanist leve. Crash as soon as I left camp. Scratch that one. Ran all the way back to town to see if I could reactivate...nope. Okay, start next one. Crashed when I got to the first tree. Scratch that one. Joined some in-game friends for some leve action...they were in the middle of one so I went to the aetheryte at Skull Valley and joined them. When I did, the quest *I* had in my log that awarded chainmail (and totally different from the one they were working on) went grey and was flagged as failed.

Lots and lots of bugs in group stuff right now. Makes me wonder if the closed beta testers did a whole lot of group testing or whether they mostly ran around solo oooing and aahhing and ******** on the forums.
#9 Sep 07 2010 at 10:44 PM Rating: Decent
**
580 posts
Only real fix I could see for this is to keep the timer for the leve fully tracked on server side and make it persisten. So if you crash or log out the 30 minutes keeps ticking down.

Start Leve at 1:00
90% complete at 1:10
crash at 1:11
manage to get back on at 1:15
leve still going and you have 15 min to finish up that last 10%

This would make the most sense to me. No need to worry about exploits(people failing to redo it etc)
____________________________
_______

___________________________________________
Call your Mom, She misses you.
#10 Sep 07 2010 at 10:54 PM Rating: Good
Sage
***
1,500 posts
celinaredfern wrote:
Only real fix I could see for this is to keep the timer for the leve fully tracked on server side and make it persisten. So if you crash or log out the 30 minutes keeps ticking down.

Start Leve at 1:00
90% complete at 1:10
crash at 1:11
manage to get back on at 1:15
leve still going and you have 15 min to finish up that last 10%

This would make the most sense to me. No need to worry about exploits(people failing to redo it etc)
They can also save a partial progress of your leve: how much time you have left and how many mobs you still need to kill, and strat from there the next time you attempt to touch the same Aetheryte.

Ken
____________________________
"Maybe it means: you're the evil man, and I'm the righteous man, and Mr. Nine-millimeter here, he's the shepherd protecting my righteous *** in the Valley of Darkness." - Jules.
FFXIV: Mabel Rand (Gugnir)
FFXI: Kenage, retired.
K&K forever!,
#11 Sep 07 2010 at 10:59 PM Rating: Decent
**
265 posts
I honestly have not crashed a single time.. with the exception of one time during the second day of open beta. luck?
#12 Sep 07 2010 at 11:01 PM Rating: Decent
Scholar
17 posts
*sigh* glad i am not the only one having this blasted issue.


#13 Sep 07 2010 at 11:10 PM Rating: Decent
kenage wrote:
They can also save a partial progress of your leve: how much time you have left and how many mobs you still need to kill, and strat from there the next time you attempt to touch the same Aetheryte.

Ken


I think they'd pretty much have to preserve your progress like you said. Your leve should never be flagged as failed unless you ran out of time. I was originally thinking that I wouldn't even mind if they reset your progress and you had to start over if you crashed, disconnected, or otherwise failed, but I know if they did that people would just abuse the **** out of it for the xp/skill bonus.
#14 Sep 07 2010 at 11:55 PM Rating: Good
Scholar
*
103 posts
I just started crashing after the latest patch, and sure enough, I was on a guildleve.

I do hope they implement something for release, but I don't think they'll get it done in time. It took ArenaNet about 3 years add that functionality to Guild Wars. (Disconnecting during the mission used to kick you from it, but they added a fail-safe so you stay where you were in the mission for 15 minutes after disconnecting.) Blizzard did something similar to this for World of Warcraft too.

In a perfect world they'd have the Guildleve activate server side which would keep the timer counting down if you disconnect. No more instant fails on disconnection. Mobs would despawn after the guildleve timer runs out, as only then you would fail the quest and be unable to re-do it. No exploits possible.

Edit: Just crashed again. Had a single mob left on my quest.

By the way, is anyone who's crashing using the hardware mouse patch? That's the only thing I had enabled and I've been crashing. I did not crash before the latest game patch even though I used the hardware mouse patch. Tempted to reinstall the game.

Edited, Sep 8th 2010 3:22am by DAOWAce
____________________________
I don't mean to sound rude, but I can't help the way people interpret my words.
#15 Sep 08 2010 at 12:53 AM Rating: Good
Scholar
*
118 posts
Soezu wrote:
Something needs to be done. Because losing your guildleve for 48 hours due to a disconnect or client crash is unacceptable. I just lost 2 in a row, 1 had a "Dalmatica" reward and I was excited to get it! Dalmatica was sick in FFXI with mp regen on it. I wanted to see if it had MP regen.


Lol, well you can forget about it being endgame ranked gear. It's just a shirt. Really nothing special about it.

As for the crashes, clearly it's a big issue, so SE probably knows about it and will hopefully fix it soon.

Edited, Sep 8th 2010 2:54am by Solimurr
#16 Sep 08 2010 at 1:47 AM Rating: Good
Scholar
**
435 posts
a fix for abusing exp/rank bonus: don't give the exp/rank points until the leve is complete. They already delay the award of rank points until you kill the mob your are hitting.
#17 Sep 08 2010 at 1:52 AM Rating: Default
**
254 posts
Oh no doubt, still losing a nice upgrade to a crash.
#18 Sep 08 2010 at 2:00 AM Rating: Good
***
2,120 posts
There's another benefit to partying for guildleves, if you DC the rest of the party stays on the leve & can invite you back...you then go to the aetheryte and get asked "Join party leader's guildleve?" or somethin' similar. Let's you back in...if everyone DCs I guess you're still screwed...

This also sucks if the target mobs are far away from the aetheryte...

Edited, Sep 8th 2010 4:01am by TwistedOwl
____________________________

#19 Sep 08 2010 at 2:49 AM Rating: Excellent
In an update note, SE has said that it's now possible to "immediately exchange a failed leve". I haven't gotten this to work myself, but others on the forum here and IRC say they have.

Could someone write up a detailed explanation of how this is supposed to work?



Also, FWIW, you can re-share a Guildleve if you're in a party and crash/disconnect. Here's an example of how that would work:

Pikko, Wint and I are partied and we are doing her Guildleve. During the leve I crash and log back in. I can then rejoin the party, go back to the Aetheryite and use it to reacquire the Levequest. In order to do this Pikko must be party leader, not Wint.
#20 Sep 08 2010 at 9:20 AM Rating: Good
Sage
*
80 posts
Quote:
In an update note, SE has said that it's now possible to "immediately exchange a failed leve". I haven't gotten this to work myself, but others on the forum here and IRC say they have.

Could someone write up a detailed explanation of how this is supposed to work?


Would also like an explanation as to how it works now. Tried reactivating at the aetheryte right after, but it was greyed out. Tried reacquiring it from the adventurer's guild npc, but received the standard "There are no levequests available" message. The only way I've gotten it to work was in a party, wherein so long as one person stays online with it active, it can be shared/assumed at the respective aetheryte. I can live with the 48 hour cooldown if they fix that aspect, since you can join others on their levequests as it is, and still benefit from the great xp/rewards/fun (plus it promotes grouping/teamwork).

Quote:
I honestly have not crashed a single time.. with the exception of one time during the second day of open beta. luck?


Could be a mix of luck and successful patches, maybe? I haven't crashed since Friday, or Saturday morning I think? The game client runs solid now, for me. My only technical complaints are the random disconnects, UI lag, and the software mouse nonsense (The toggle's in the client already...shouldn't need to resort to 3rd party methods). Though those could all be attributed to background stat parsers running during beta, as well as devs wanting to record cursor clicks, perhaps? Only launch will tell~

Interestingly enough, I'm running AMD cards. A good friend of mine, who is rocking an Nvidia card, is unfortunately still plagued with crashes, on top of the disconnects. Thankfully, he has enjoyed the game so much, and is mature enough to realize launches (and especially betas) are rarely ever perfect, that he's going to be playing come launch. So, I'm still staying optimistic as the patches are steadily coming in almost, if not daily (which is what we want in betas...funny, people complain about that too), and I'm already seeing a solid community forming. At least on my server (Besaid), and within these forums. ^_^
____________________________
Normal mobs: The new "NM."

| i7-930@4.01GHz | 12GB DDR3 1600MHz @9,9,9,28 | 2x ATI Sapphire HD 2GB 5870 Vapor-X Crossfire@875MHz core/1250MHz mem | running W7 64-bit | all stable and cool |
#21Kkes, Posted: Oct 05 2010 at 9:34 AM, Rating: Sub-Default, (Expand Post) uhgg,, it is getting annoying . the last 2 days failed 6 quest because of server errors.
This forum is read only
This Forum is Read Only!
Recent Visitors: 18 All times are in CST
Anonymous Guests (18)