issue 158
(Project still active?) commented on by odelle2004
- wow great work (@_@b
wow great work (@_@b
Sep 29, 2009
issue 161
(Tick crits: Healing style) reported by wwusir...@hotmail.com
- new druid t9 4pc bonus gives Rejuvenation the ability to crit.
The framework support existed but wasn't completed.
lib\stasis\PAGE.PM
line 215: Change line to
"R-% Crit" => $self->{pm}->tip( _cricruglaText($sdata) ),
lib\stasis\extension\healing.pm
line 49: Add tickCritCount at the end
sub value {
qw/hitCount hitTotal hitEffective hitMin hitMax critCount critTotal
critEffective critMin critMax tickCount tickTotal tickEffective tickMin
tickMax tickCritCount/;
}
line 84: add 3 lines after $type = "tick";
if( $event->{action} == SPELL_PERIODIC_HEAL ) {
$type = "tick";
add: if( $event->{critical} ) {
add: $hdata->{"tickCritCount"} ++;
add: }
} elsif( $event->{critical} ) {
$type = "crit";
} else {
$type = "hit";
}
~Espoir
new druid t9 4pc bonus gives Rejuvenation the ability to crit.
The framework support existed but wasn't completed.
lib\stasis\PAGE.PM
line 215: Change line to
"R-% Crit" => $self->{pm}->tip( _cricruglaText($sdata) ),
lib\stasis\extension\healing.pm
line 49: Add tickCritCount at the end
sub value {
qw/hitCount hitTotal hitEffective hitMin hitMax critCount critTotal
critEffective critMin critMax tickCount tickTotal tickEffective tickMin
tickMax tickCritCount/;
}
line 84: add 3 lines after $type = "tick";
if( $event->{action} == SPELL_PERIODIC_HEAL ) {
$type = "tick";
add: if( $event->{critical} ) {
add: $hdata->{"tickCritCount"} ++;
add: }
} elsif( $event->{critical} ) {
$type = "crit";
} else {
$type = "hit";
}
~Espoir
Sep 28, 2009
issue 156
(Critical heal is not recorded in patch 3.2) commented on by wwusir...@hotmail.com
- Thank you for this fix. Would you know how to get it to display in the charts?
All I've been able to do is get the program to output new variables in the xml but
nothing like taking it from a parse...Something like hps values and such. But this is
a different variable all together.
Thank you for this fix. Would you know how to get it to display in the charts?
All I've been able to do is get the program to output new variables in the xml but
nothing like taking it from a parse...Something like hps values and such. But this is
a different variable all together.
Sep 26, 2009
issue 158
(Project still active?) commented on by edward.e...@port.ac.uk
- I've begun a fork at http://code.google.com/p/apostasis/
I'm gradually working on bringing in new patches. I also intend to add reliable patch submitters so they can
commit changes without having to have me actually around.
My perl isn't awesome, and I don't clear raid instances the week they come out, but I hope we can get a useful
repository with more recent changes in quickly. If gianmerlino wishes to take things up again in the future then
naturally anything committed to this new tree can be remerged back into StasisCL proper.
I've begun a fork at http://code.google.com/p/apostasis/
I'm gradually working on bringing in new patches. I also intend to add reliable patch submitters so they can
commit changes without having to have me actually around.
My perl isn't awesome, and I don't clear raid instances the week they come out, but I hope we can get a useful
repository with more recent changes in quickly. If gianmerlino wishes to take things up again in the future then
naturally anything committed to this new tree can be remerged back into StasisCL proper.
Sep 25, 2009
issue 156
(Critical heal is not recorded in patch 3.2) commented on by edward.e...@port.ac.uk
- This doesn't seem to be working correctly - the crit field isn't making it into the @col array - possibly as a result
of something in the 'stasis' perl file that calls the parser. Did you make any other changes to get this working for
you?
This doesn't seem to be working correctly - the crit field isn't making it into the @col array - possibly as a result
of something in the 'stasis' perl file that calls the parser. Did you make any other changes to get this working for
you?
issue 158
(Project still active?) commented on by traveltoaiur
- Would be nice to have some answer from Gianmerlino about this
Would be nice to have some answer from Gianmerlino about this
Sep 22, 2009
issue 160
(Patch 3.2.2 - Onyxia) reported by wowstenas
- In the zones section (around line 55):
"onyxia" => "Onyxia's Lair",
After all the other bosses but before the ");":
{
short => "onyxia",
zone => "onyxia",
long => "Onyxia",
mobStart => [ 10184 ],
mobContinue => [ 10184, 11262, 36561 ],
mobEnd => [ 10184 ],
timeout => 30,
},
In the zones section (around line 55):
"onyxia" => "Onyxia's Lair",
After all the other bosses but before the ");":
{
short => "onyxia",
zone => "onyxia",
long => "Onyxia",
mobStart => [ 10184 ],
mobContinue => [ 10184, 11262, 36561 ],
mobEnd => [ 10184 ],
timeout => 30,
},
Sep 18, 2009
issue 159
(Disc priest :Heal absorbed) reported by thekyj
- Hello,
do you know if it will be possible to show amount absorbed by the shields
of a discipline priest ?
Thanks in advance
Hello,
do you know if it will be possible to show amount absorbed by the shields
of a discipline priest ?
Thanks in advance
Sep 16, 2009
issue 153
(Crusaders' Coliseum support) commented on by odelle2004
- As we already know, we can parse both 10man and 25man, or both normal and heroic
with single setup. it means boss unit IDs are not depend on any difficulty.
But it seems boss spell IDs are depend on difficulty. Please see your stasiscl
results, spell names are same but spell IDs are different. Then it is possible to
separate difficulties if we can update program code how it can fetch not only unit
ID but also spell ID.
As we already know, we can parse both 10man and 25man, or both normal and heroic
with single setup. it means boss unit IDs are not depend on any difficulty.
But it seems boss spell IDs are depend on difficulty. Please see your stasiscl
results, spell names are same but spell IDs are different. Then it is possible to
separate difficulties if we can update program code how it can fetch not only unit
ID but also spell ID.
Sep 15, 2009
issue 158
(Project still active?) commented on by vonlani
- i was also wondering if someone is still taking care of this project.
the diffs for the new raids are ok for me, but there seem to be other issues (critical healing) and a new version
would be great.
i was also wondering if someone is still taking care of this project.
the diffs for the new raids are ok for me, but there seem to be other issues (critical healing) and a new version
would be great.
Sep 14, 2009
issue 158
(Project still active?) reported by mr.mosch
- Im not sure if the project is still active. i use this thing every day - so
is there any developer reading the issues?
Im not sure if the project is still active. i use this thing every day - so
is there any developer reading the issues?
Sep 12, 2009
issue 157
(Koralon, new VoA boss) commented on by wowstenas
- Note that I rolled this into the patch on 153 for the Coliseum changes. In a sense
it's more of a complete 3.2 patch. Thank you for the Koralon section! :)
Note that I rolled this into the patch on 153 for the Coliseum changes. In a sense
it's more of a complete 3.2 patch. Thank you for the Koralon section! :)
Sep 12, 2009
issue 157
(Koralon, new VoA boss) commented on by wowstenas
- Note that I rolled this into the patch on 153 for the Coliseum changes. In a sense
it's more of a complete 3.2 patch. Thank you for the Koralon section! :)
Note that I rolled this into the patch on 153 for the Coliseum changes. In a sense
it's more of a complete 3.2 patch. Thank you for the Koralon section! :)
Sep 09, 2009
issue 153
(Crusaders' Coliseum support) commented on by wowstenas
- Here's a patch and the modified file for the people who don't like patches.
I'm not sure if there is a way to differentiate the Grand Crusader fights. If
stasiscl isn't registering the fights on Heroic, then the boss IDs are different and
it might work, but that's highly unlikely.
Here's a patch and the modified file for the people who don't like patches.
I'm not sure if there is a way to differentiate the Grand Crusader fights. If
stasiscl isn't registering the fights on Heroic, then the boss IDs are different and
it might work, but that's highly unlikely.
Sep 09, 2009
issue 153
(Crusaders' Coliseum support) commented on by dark666105
- Any update on that patch for the entire section?
Also if say a raid clears trial of the crusader and then immediately starts going
through trial of the grand crusader, is there any way for stasiscl to differentiate
the fights from each?
Any update on that patch for the entire section?
Also if say a raid clears trial of the crusader and then immediately starts going
through trial of the grand crusader, is there any way for stasiscl to differentiate
the fights from each?
Sep 02, 2009
issue 157
(Koralon, new VoA boss) reported by odelle2004
- {
short => "koralon",
zone => "archavon",
long => "Koralon",
mobStart => [ 35013 ],
mobContinue => [ 35013 ],
mobEnd => [ 35013 ],
timeout => 30,
},
{
short => "koralon",
zone => "archavon",
long => "Koralon",
mobStart => [ 35013 ],
mobContinue => [ 35013 ],
mobEnd => [ 35013 ],
timeout => 30,
},
Sep 01, 2009
issue 153
(Crusaders' Coliseum support) commented on by wowstenas
-
{
short => "anubarak",
zone => "coliseum",
long => "Anub'arak",
mobStart => [ 34564 ],
mobContinue => [ 34564, 34605, 34606, 34607 ],
mobEnd => [ 34564 ],
timeout => 30,
endAll => 1,
},
issue 154
(Casts and auras doesn't record direct heals) commented on by odelle2004
- In case instant spell, SPELL_CAST_SUCCESS is recorded when its casted. Then it is
easy to count.
In case casting spell, SPELL_CAST_START is recorded when its started to cast, but
SPELL_CAST_SUCCESS is not recorded when it lands, but each event is recorded for
each spell. For examples, ENCHANT_APPLIED is recorded for Grand Spellstone by
Warlock, SPELL_SUMMON is recorded for totems by Shaman, SPELL_HEAL is recorded for
any healing spells. Then. it is necessary to make sure what spell records which
event to count.
In case instant spell, SPELL_CAST_SUCCESS is recorded when its casted. Then it is
easy to count.
In case casting spell, SPELL_CAST_START is recorded when its started to cast, but
SPELL_CAST_SUCCESS is not recorded when it lands, but each event is recorded for
each spell. For examples, ENCHANT_APPLIED is recorded for Grand Spellstone by
Warlock, SPELL_SUMMON is recorded for totems by Shaman, SPELL_HEAL is recorded for
any healing spells. Then. it is necessary to make sure what spell records which
event to count.
Sep 01, 2009
issue 156
(Critical heal is not recorded in patch 3.2) reported by odelle2004
- Critical heal is not recorded in patch 3.2
- Symptom
Critical heal is not recorded in patch 3.2
- Description
Combatlog format was updated for direct healing spells with patch 3.2,
absorption field was added.
- Format
(patch 3.0)
Spell_ID,"Spell Name",Spell_School,AmountHeal,AmountOverHeal,Crit_nil_or_1
(patch 3.2)
Spell_ID,"Spell
Name",Spell_School,AmountHeal,AmountOverHeal,Absorption,Crit_nil_or_1
- Example of combatlog record
8/30 22:07:46.230
SPELL_HEAL,0x0300000000AB8072,"Odelle",0x511,0x0300000000AB8072,"Odelle",0x
511,48089,"Circle of Healing",0x2,2759,314,0,nil
- Patch
/lib/Stasis/Parser/V2.pm
## around line 40 (@_@b
my @fheal = qw/amount critical/;
my @fheal_wlk = qw/amount extraamount critical/;
my @fheal_wlk32 = qw/amount extraamount absorption critical/; # ++ Insert
this line
## around line 155 (@_@b
if( @col <= 5 ) {
@{$result}{ (@fspell, @fheal ) } = @col;
# } else { # -- Remove this line
} elsif( @col == 6 ) { # ++ Insert this line
@{$result}{ (@fspell, @fheal_wlk) } = @col;
} else { # ++ Insert this line
@{$result}{ (@fspell, @fheal_wlk32 ) } = @col; # ++ Insert this line
}
Critical heal is not recorded in patch 3.2
- Symptom
Critical heal is not recorded in patch 3.2
- Description
Combatlog format was updated for direct healing spells with patch 3.2,
absorption field was added.
- Format
(patch 3.0)
Spell_ID,"Spell Name",Spell_School,AmountHeal,AmountOverHeal,Crit_nil_or_1
(patch 3.2)
Spell_ID,"Spell
Name",Spell_School,AmountHeal,AmountOverHeal,Absorption,Crit_nil_or_1
- Example of combatlog record
8/30 22:07:46.230
SPELL_HEAL,0x0300000000AB8072,"Odelle",0x511,0x0300000000AB8072,"Odelle",0x
511,48089,"Circle of Healing",0x2,2759,314,0,nil
- Patch
/lib/Stasis/Parser/V2.pm
## around line 40 (@_@b
my @fheal = qw/amount critical/;
my @fheal_wlk = qw/amount extraamount critical/;
my @fheal_wlk32 = qw/amount extraamount absorption critical/; # ++ Insert
this line
## around line 155 (@_@b
if( @col <= 5 ) {
@{$result}{ (@fspell, @fheal ) } = @col;
# } else { # -- Remove this line
} elsif( @col == 6 ) { # ++ Insert this line
@{$result}{ (@fspell, @fheal_wlk) } = @col;
} else { # ++ Insert this line
@{$result}{ (@fspell, @fheal_wlk32 ) } = @col; # ++ Insert this line
}
issue 153
(Crusaders' Coliseum support) commented on by tindelli
- Just confirming that my earlier Twin Val'kyr listing works properly. Can't edit
comments (really google?) so here it is again for anyone interested:
{
short => "twinvalkyr",
zone => "coliseum",
long => "Twin Val'kyr",
mobStart => [ 34496, 34497 ],
mobContinue => [ 34496, 34497 ],
mobEnd => [ 34496, 34497],
timeout => 30,
endAll => 1,
},
After Anub'arak next week, I'll make a patch for the entire section that can easily
be applied, but for now, manual updates all the way >.>
Just confirming that my earlier Twin Val'kyr listing works properly. Can't edit
comments (really google?) so here it is again for anyone interested:
{
short => "twinvalkyr",
zone => "coliseum",
long => "Twin Val'kyr",
mobStart => [ 34496, 34497 ],
mobContinue => [ 34496, 34497 ],
mobEnd => [ 34496, 34497],
timeout => 30,
endAll => 1,
},
After Anub'arak next week, I'll make a patch for the entire section that can easily
be applied, but for now, manual updates all the way >.>
Aug 25, 2009
issue 153
(Crusaders' Coliseum support) commented on by dark666105
- I'm not really familiar at all with perl but is there a startCount command you could
use to seperate the two listings?
I'm not really familiar at all with perl but is there a startCount command you could
use to seperate the two listings?
Aug 25, 2009
issue 153
(Crusaders' Coliseum support) commented on by dark666105
- @tindelli
lol i deleted my old comment so i could add to it, thanks for that twins info.
on the faction champions thing, you could do what you mentioned in conjunction with
what pneumatus said. basically rather than creating 480 combinations you just add 2
with the endCount that pneumatus mentioned, one for the 10 man version for 6 and one
for the 25 man version with 10.
@tindelli
lol i deleted my old comment so i could add to it, thanks for that twins info.
on the faction champions thing, you could do what you mentioned in conjunction with
what pneumatus said. basically rather than creating 480 combinations you just add 2
with the endCount that pneumatus mentioned, one for the 10 man version for 6 and one
for the 25 man version with 10.
Aug 25, 2009
issue 153
(Crusaders' Coliseum support) commented on by dark666105
- Also does anyone have the IDs for the twins yet?
here are the IDs I found in mmo-champs DB, though I'm not sure what is for what.
Maybe one for each version and one "outside" of the coliseum like the rest of the
bosses? That hypothesis would coincide with only finding 4 IDs for jaraxxus in their
database. Then again I could be completely wrong.
Eydis Darkbane
34496, 36066, 35347, 35348, 35349
Fjola Lightbane
34497, 36065, 35350, 35351, 35352
Also does anyone have the IDs for the twins yet?
here are the IDs I found in mmo-champs DB, though I'm not sure what is for what.
Maybe one for each version and one "outside" of the coliseum like the rest of the
bosses? That hypothesis would coincide with only finding 4 IDs for jaraxxus in their
database. Then again I could be completely wrong.
Eydis Darkbane
34496, 36066, 35347, 35348, 35349
Fjola Lightbane
34497, 36065, 35350, 35351, 35352
Aug 25, 2009
issue 153
(Crusaders' Coliseum support) commented on by tindelli
- @dark666105: If you make a mobEnd array, and specify all of them, it will end when any of them dies. If you
make a mobEnd array and set endAll to 1, it will end when all of them die. Since not ALL of the mobs will be
there in any given fight, it will report all attempts as fails. The only other way would be to have a separate
fight for every combination of faction champions (480 combinations for each faction, assuming 3 healers and
7 other... not sure if there's any more restrictions, but it's still an absurd number). I was trying to implement a
patch that will allow for an "endCount" parameter as suggested by pneumatus, but then realized the 10-man
modes had only 6 mobs instead of 10, and I don't think the LogSplit actually can determine 10- or 25-man
versions. Probably going to have to just leave it as an attempt instead of a victory.
I'll be back tonight after I test my twin val'kyr patch. If anyone wants the preliminary (pre-tested) version, it's
{
short => "twinvalkyrs",
zone => "coliseum",
long => "Twin Valkyrs",
mobStart => [ 34496, 34497 ],
mobContinue => [ 34496, 34497 ],
mobEnd => [ 34496, 34497],
timeout => 30,
endAll => 1,
},
Haven't seen the encounter, so more might need to be added... ill update tonight after raid.
@dark666105: If you make a mobEnd array, and specify all of them, it will end when any of them dies. If you
make a mobEnd array and set endAll to 1, it will end when all of them die. Since not ALL of the mobs will be
there in any given fight, it will report all attempts as fails. The only other way would be to have a separate
fight for every combination of faction champions (480 combinations for each faction, assuming 3 healers and
7 other... not sure if there's any more restrictions, but it's still an absurd number). I was trying to implement a
patch that will allow for an "endCount" parameter as suggested by pneumatus, but then realized the 10-man
modes had only 6 mobs instead of 10, and I don't think the LogSplit actually can determine 10- or 25-man
versions. Probably going to have to just leave it as an attempt instead of a victory.
I'll be back tonight after I test my twin val'kyr patch. If anyone wants the preliminary (pre-tested) version, it's
{
short => "twinvalkyrs",
zone => "coliseum",
long => "Twin Valkyrs",
mobStart => [ 34496, 34497 ],
mobContinue => [ 34496, 34497 ],
mobEnd => [ 34496, 34497],
timeout => 30,
endAll => 1,
},
Haven't seen the encounter, so more might need to be added... ill update tonight after raid.
Aug 25, 2009
issue 153
(Crusaders' Coliseum support) commented on by dark666105
- Also does anyone have the IDs for the twins yet?
Also does anyone have the IDs for the twins yet?
Aug 25, 2009
issue 153
(Crusaders' Coliseum support) commented on by dark666105
- would it be feasable to just do a mobEnd with all the IDs, or would it not end till
it has detected the "dead" IDs of the ones not even there? It makes me wonder if just
listing all the IDs wont work if an array of IDs could be created and just do a
mobEnd on that array. Which overall couldn't it technically be used for every fight?
Frankly I think this might be the only way to cleanly parse this fight.
would it be feasable to just do a mobEnd with all the IDs, or would it not end till
it has detected the "dead" IDs of the ones not even there? It makes me wonder if just
listing all the IDs wont work if an array of IDs could be created and just do a
mobEnd on that array. Which overall couldn't it technically be used for every fight?
Frankly I think this might be the only way to cleanly parse this fight.
Aug 25, 2009
issue 153
(Crusaders' Coliseum support) commented on by dark666105
- would it be feasable to just do a mobEnd with all the IDs, or would it not end till
it has detected the "dead" IDs of the ones not even there? It makes me wonder if just
listing all the IDs wont work if an array of IDs could be created and just do a
mobEnd on that array. Which overall couldn't it technically be used for every fight?
would it be feasable to just do a mobEnd with all the IDs, or would it not end till
it has detected the "dead" IDs of the ones not even there? It makes me wonder if just
listing all the IDs wont work if an array of IDs could be created and just do a
mobEnd on that array. Which overall couldn't it technically be used for every fight?
Aug 25, 2009
issue 153
(Crusaders' Coliseum support) commented on by dark666105
- would it be feasable to just do a mobEnd with all the IDs, or would it not end till
it has detected the "dead" IDs of the ones not even there? It makes me wonder if just
listing all the IDs wont work if an array of IDs could be created and just do a
mobEnd on that array.
would it be feasable to just do a mobEnd with all the IDs, or would it not end till
it has detected the "dead" IDs of the ones not even there? It makes me wonder if just
listing all the IDs wont work if an array of IDs could be created and just do a
mobEnd on that array.
Aug 24, 2009
issue 153
(Crusaders' Coliseum support) commented on by pneumatus
- {
short => "factionchampions",
zone => "coliseum",
long => "Faction Champions",
mobStart => [ 34441, 34444, 34445, 34447, 34448, 34449, 34450, 34451, 34453,
34454, 34455, 34456, 34458, 34459, 34460, 34461, 34463, 34465, 34466,
34467, 34468, 34469, 34470, 34471, 34472, 34473, 34474, 34475 ],
mobContinue => [ 34441, 34444, 34445, 34447, 34448, 34449, 34450, 34451, 34453,
34454, 34455, 34456, 34458, 34459, 34460, 34461, 34463, 34465, 344
66, 34467, 34468, 34469, 34470, 34471, 34472, 34473, 34474, 34475 ],
timeout => 30,
endAll => 1,
},
As a complete block, the above works but will show kills as tries.
{
short => "factionchampions",
zone => "coliseum",
long => "Faction Champions",
mobStart => [ 34441, 34444, 34445, 34447, 34448, 34449, 34450, 34451, 34453,
34454, 34455, 34456, 34458, 34459, 34460, 34461, 34463, 34465, 34466,
34467, 34468, 34469, 34470, 34471, 34472, 34473, 34474, 34475 ],
mobContinue => [ 34441, 34444, 34445, 34447, 34448, 34449, 34450, 34451, 34453,
34454, 34455, 34456, 34458, 34459, 34460, 34461, 34463, 34465, 344
66, 34467, 34468, 34469, 34470, 34471, 34472, 34473, 34474, 34475 ],
timeout => 30,
endAll => 1,
},
As a complete block, the above works but will show kills as tries.
Aug 24, 2009
issue 153
(Crusaders' Coliseum support) commented on by dark666105
- so has anyone come up with a complete block of code to put in to handle the faction
champions properly?
so has anyone come up with a complete block of code to put in to handle the faction
champions properly?
Aug 23, 2009
issue 153
(Crusaders' Coliseum support) commented on by wowstenas
- The line numbers are in the .diff. Looking at the LogSplit.pm file, it will be pretty
obvious when you get to the section with the other boss fights. Just copy and past
the block provided. The file tindelli provided on comment #4 is more complete than
the one I posted and has the first two bosses already included.
The line numbers are in the .diff. Looking at the LogSplit.pm file, it will be pretty
obvious when you get to the section with the other boss fights. Just copy and past
the block provided. The file tindelli provided on comment #4 is more complete than
the one I posted and has the first two bosses already included.
Aug 23, 2009
issue 153
(Crusaders' Coliseum support) commented on by SharpeE13
- @wowstenas and general
How do I go about using the code/lines that wowstenas has posted? I did use the .diff
file to patch and had no problem. Just dont know how to use the new code supplied.
@wowstenas and general
How do I go about using the code/lines that wowstenas has posted? I did use the .diff
file to patch and had no problem. Just dont know how to use the new code supplied.
Aug 21, 2009
issue 155
(Death Event: UNIT_DISSIPATES ) reported by jebuskrust
- Just wanted throw in a 3.2 event to the TODO list. I'm "assuming" this event
occurs in the event when boss dies if there are remaining adds still up. A
good example of this would be when fighting Kologarn's elementals while
destroying left/right arm.
Just wanted throw in a 3.2 event to the TODO list. I'm "assuming" this event
occurs in the event when boss dies if there are remaining adds still up. A
good example of this would be when fighting Kologarn's elementals while
destroying left/right arm.
Aug 21, 2009
issue 153
(Crusaders' Coliseum support) commented on by goodnuff
- As a temporary measure I have just set
endAll => 1,
and it parses correctly for me it just does not recognize a win vs an attempt.
As a temporary measure I have just set
endAll => 1,
and it parses correctly for me it just does not recognize a win vs an attempt.
Aug 20, 2009
issue 153
(Crusaders' Coliseum support) commented on by dark666105
- doesn't it detect if its a 10 man or 25 man when parsing normally?
doesn't it detect if its a 10 man or 25 man when parsing normally?
Aug 19, 2009
issue 153
(Crusaders' Coliseum support) commented on by tindelli
- @pneumatus
Well.... I was working on a patch for this... and then realized that on 10-man
there's only 6 mobs on 10-man. Open to suggestions about this, but I don't know of
a way to determine the initial number of enemies. Maybe I'm missing something.
@pneumatus
Well.... I was working on a patch for this... and then realized that on 10-man
there's only 6 mobs on 10-man. Open to suggestions about this, but I don't know of
a way to determine the initial number of enemies. Maybe I'm missing something.
Aug 19, 2009
issue 153
(Crusaders' Coliseum support) commented on by pneumatus
- I'd guess a patch would be required to create a flag similar to endAll used on Four
Horsemen have to signify that 10 need killing, perhaps something along the lines of
endCount => 10, but my Perl isn't good enough to fix it myself :<
I'd guess a patch would be required to create a flag similar to endAll used on Four
Horsemen have to signify that 10 need killing, perhaps something along the lines of
endCount => 10, but my Perl isn't good enough to fix it myself :<
Aug 19, 2009
issue 153
(Crusaders' Coliseum support) commented on by dark666105
- you could have it check on each attempt if 10 of the main mobs(not pets) go down to
set that as a win after all 10 are down. also check for 6 going down in 10 man.
you could have it check on each attempt if 10 of the main mobs(not pets) go down to
set that as a win after all 10 are down. also check for 6 going down in 10 man.
Aug 18, 2009
issue 153
(Crusaders' Coliseum support) commented on by tindelli
- Faction Champions:
{
short => "factionchampions",
zone => "coliseum",
long => "Faction Champions",
mobStart => [ 34441, 34444, 34445, 34447, 34448, 34449, 34450, 34451, 34453,
34454, 34455, 34456, 34458, 34459, 34460, 34461, 34463, 34465, 34466, 34467, 34468,
34469, 34470, 34471, 34472, 34473, 34474, 34475 ],
mobContinue => [ 34441, 34444, 34445, 34447, 34448, 34449, 34450, 34451, 34453,
34454, 34455, 34456, 34458, 34459, 34460, 34461, 34463, 34465, 34466, 34467, 34468,
34469, 34470, 34471, 34472, 34473, 34474, 34475 ],
timeout => 30,
},
I don't know a way to detect an actual win here... since there isn't a particular
mob that needs to die for it to count as a win. If someone has any insight, I'd be
glad to know
Faction Champions:
{
short => "factionchampions",
zone => "coliseum",
long => "Faction Champions",
mobStart => [ 34441, 34444, 34445, 34447, 34448, 34449, 34450, 34451, 34453,
34454, 34455, 34456, 34458, 34459, 34460, 34461, 34463, 34465, 34466, 34467, 34468,
34469, 34470, 34471, 34472, 34473, 34474, 34475 ],
mobContinue => [ 34441, 34444, 34445, 34447, 34448, 34449, 34450, 34451, 34453,
34454, 34455, 34456, 34458, 34459, 34460, 34461, 34463, 34465, 34466, 34467, 34468,
34469, 34470, 34471, 34472, 34473, 34474, 34475 ],
timeout => 30,
},
I don't know a way to detect an actual win here... since there isn't a particular
mob that needs to die for it to count as a win. If someone has any insight, I'd be
glad to know
issue 153
(Crusaders' Coliseum support) commented on by tindelli
- So.... for faction champions, I don't know of a way to detect when a win occurs.
Since the mobs are random each week, and since there's no predetermined order of
death...even a win will appear just as an "attempt".
Working on compiling a section that will apply for any/all of the possible NPCs. If
anyone (especially horde players) could post their logs for this fight, it would
help me with it tremendously.
So.... for faction champions, I don't know of a way to detect when a win occurs.
Since the mobs are random each week, and since there's no predetermined order of
death...even a win will appear just as an "attempt".
Working on compiling a section that will apply for any/all of the possible NPCs. If
anyone (especially horde players) could post their logs for this fight, it would
help me with it tremendously.
Aug 17, 2009
issue 153
(Crusaders' Coliseum support) commented on by dark666105
- Are the boss IDs the same as they were on the ptr? and if they are does anyone have
the ones for the bosses coming up so they can be added in time for when the encounter
is released?
Are the boss IDs the same as they were on the ptr? and if they are does anyone have
the ones for the bosses coming up so they can be added in time for when the encounter
is released?
Aug 15, 2009
issue 153
(Crusaders' Coliseum support) commented on by twinight
- Thanks, tindelli! I'd be a little lost without stasis at this point.
Thanks, tindelli! I'd be a little lost without stasis at this point.
