search

teel / apostasis

Automatically exported from code.google.com/p/apostasis
0 stars 0 forks source link

Dreamwalker parse not working correctly? #24

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
10 man log, did two pulls on Dreamwalker (2nd was kill).  Parser seems to 
be having issues:

./stasis: Encounter start: valithria at 2/5 20:22:08.866 .. writing 
Valithria Dreamwalker try 1 (sws-valithria-20100205-202208-0-) .. done.
./stasis: Encounter start: valithria at 2/5 20:22:52.655 .. writing 
Valithria Dreamwalker try 2 (sws-valithria-20100205-202252-0-) .. done.
./stasis: Encounter start: valithria at 2/5 20:23:52.512 .. writing 
Valithria Dreamwalker try 3 (sws-valithria-20100205-202352-0-) .. done.
./stasis: Encounter start: valithria at 2/5 20:25:11.414 .. writing 
Valithria Dreamwalker try 4 (sws-valithria-20100205-202511-0-) .. done.
./stasis: Encounter start: valithria at 2/5 20:26:51.304 .. writing 
Valithria Dreamwalker try 5 (sws-valithria-20100205-202651-0-) .. done.
./stasis: Encounter start: valithria at 2/5 20:31:40.084 .. writing 
Valithria Dreamwalker try 6 (sws-valithria-20100205-203140-0-) .. done.
./stasis: Encounter start: valithria at 2/5 20:34:44.236 .. writing 
Valithria Dreamwalker try 7 (sws-valithria-20100205-203444-0-) .. done.
./stasis: Encounter start: valithria at 2/5 20:35:33.057 .. writing 
Valithria Dreamwalker try 8 (sws-valithria-20100205-203533-0-) .. done.
./stasis: Encounter start: valithria at 2/5 20:36:22.064 .. writing 
Valithria Dreamwalker (sws-valithria-20100205-203622-1-) ..

et cetera.

Zipped logfile here: http://dl.dropbox.com/u/88344/WoWCombatLog.zip

Please do not mind the embarrassing Sindragosa attempts.

Original issue reported on code.google.com by twini...@gmail.com on 6 Feb 2010 at 9:32

GoogleCodeExporter commented 8 years ago 
Oh RNG failure. Your fight was unlucky in that Risen Archmages didn't come out 
within 
the time out period (30seconds) which is how I set up the fight to continue on. 
I 
increased the timeout to 60 for the next revision. Before I put up the new 
revision I 
will see about finding other mob id's to use as a continue (suppressors), as 
Valithria 
herself appears to not hold the timeout alive.

Original comment by wwusir...@gmail.com on 6 Feb 2010 at 11:48

GoogleCodeExporter commented 8 years ago 
Updated in last revision. Adding all of the mobs helps and the timeout change 
isn't 
needed. It's odd that I never got the error in 3 of my own parses that I 
checked the 
code with. Gl :)

Original comment by wwusir...@gmail.com on 7 Feb 2010 at 12:11