[PAID] Raid Studio: Bastion of Twilight

[WolfpackPB]

Having an issue where my 664 Fury Warrior is unable to kill Sinestra (With Tuanha or Singular), seems like it spends too much time running down adds in order to kill the eggs / her before the friendly NPC dies and it resets. When it fails it likes to just jump into the lava and try again throwing it into a pretty bad loop. Would actually be nice to have an option to be able to skip Sinestra in your Plugin.

 

[titanlock]

Having an issue where my 664 Fury Warrior is unable to kill Sinestra (With Tuanha or Singular), seems like it spends too much time running down adds in order to kill the eggs / her before the friendly NPC dies and it resets. When it fails it likes to just jump into the lava and try again throwing it into a pretty bad loop. Would actually be nice to have an option to be able to skip Sinestra in your Plugin.

this is the same exact thing that was happening with my 698 fury war. also it would be a great idea to let the plugin allow you to choose bosses to skip if needed.

also i recommend checking the targetting on the trash before cho'gall, warlock was single targetting the adds that the mages spawn from the portals, as opposed to just outright killing the mages and avoiding the adds existing in the first place.

warlock also had trouble getting out of the lava afte cho gall, nearly died summoning the pet instead of not dying.

 

[Studio60]

Having an issue where my 664 Fury Warrior is unable to kill Sinestra (With Tuanha or Singular), seems like it spends too much time running down adds in order to kill the eggs / her before the friendly NPC dies and it resets. When it fails it likes to just jump into the lava and try again throwing it into a pretty bad loop. Would actually be nice to have an option to be able to skip Sinestra in your Plugin.

this is the same exact thing that was happening with my 698 fury war. also it would be a great idea to let the plugin allow you to choose bosses to skip if needed.

I will send my Fury Warrior there to check it out. I am a bit confused that people seem to have trouble with this, because I ran the latest version many times and was really impressed with it. I will to run it from the store. Maybe the store is still running the old version. This has happened with other developer's products in the last few weeks.

The "end at boss x" option is something I am considering the the V2 version of the plugin, but I am not too keen on doing all the dependency work. The plugin would have to check things like Mount Runs against boss selections and dungeon paths... Might be simple for most raids, but in some cases it would get really ugly. And adding an option to skip a boss because the tactic doesn't work is kind of a loser's approach, because it is like I would have given up. Fixing the tactic to work with that class seems to be a way better move.

I have opened these two tasks in regards to your reports/requests:
- Bastion of Twilight (Sinestra) - Add profile reload on encounter failure
- Bastion of Twilight (Sinestra) - Revisit whelp focus on warrior

also i recommend checking the targetting on the trash before cho'gall, warlock was single targetting the adds that the mages spawn from the portals, as opposed to just outright killing the mages and avoiding the adds existing in the first place.

So the mages should be killed first. Fair enough. I have opened this task in regards to your report/requests:
- Bastion of Twilight (Cho'gall) - Increase targeting priority for summoners in trash groups

warlock also had trouble getting out of the lava afte cho gall, nearly died summoning the pet instead of not dying.

I have opened this task in regards to your report/request:
- Bastion of Twilight (Sinestra) - Disable combat behavior before jumping in the lava, reenable it afterwards

 

[Studio60]

So I was able to address these two issues and they will be fixed in the next version, which I plan to submit today or tomorrow depending on how quickly I can issue fixes on other raids.

- Bastion of Twilight (Cho'gall) - Increase targeting priority for summoners in trash groups
- Bastion of Twilight (Sinestra) - Disable combat behavior before jumping in the lava, reenable it afterwards

But I was not able to reproduce the whelp problem. I upgraded my Fury warriors gear to 680 + enchants so I would be able to beat Valiona & Theralion on 25HC and then went on to Sinestra.
It happened exactly the way I set it up in last week's update: The bot kills the first 5 whelps in a few seconds and 4 resurrect due to the puddle that is forming beneath the first one. The bot moves a few steps to the side and kills 4 of which 3 resurrect. He then moves away again and kills the remaining 3 which don't form a puddle and that's all that is happening with those whelps. In phase 2 (after the eggs are destroyed) the whelps are ignored to kill Sinestra before she kills the character. The helping NPC had 50% left.

If this does look a lot different I am tempted to ask you to clear your cache before you try the next time: Honorbuddy:HelpDesk:Cache corruption problems. The profile updates should go through by themselves, but the issue you describe sound like what happened before I fixed it so the only explanation that comes to mind is that you are running an old version...

 

[WolfpackPB]

Sorry the issue is not with whelps for me. Here is what happens when I engage...

Attack Sinestra, Whelps Sapwn, Kill Whelps properly, All Adds are Killed properly, Eggs become vulnerable, Kill egg 1, get distracted with adds between egg 1 and 2, eggs become invincible without killing egg 2, lose the fight

I cleared my cache and gave it another shot and it failed the same way, singular and tuanha. Gave it an attempt with my Blood DK to see if it happens on all my toons but it's a little low on gear and couldn't push her to P2 in time.

EDIT: It is true that I'd rather see it fixed rather than optionally removed but you may want to think about adding in the boss kill options. I can't imagine it would be difficult, just tedious, since each boss seems to have it's own profile. Primarily useful in Cata raids for characters without the gear to clear, but may be able to do 3/4 of the instance.

 

[Studio60]

Sorry the issue is not with whelps for me. Here is what happens when I engage...

Attack Sinestra, Whelps Sapwn, Kill Whelps properly, All Adds are Killed properly, Eggs become vulnerable, Kill egg 1, get distracted with adds between egg 1 and 2, eggs become invincible without killing egg 2, lose the fight

I cleared my cache and gave it another shot and it failed the same way, singular and tuanha. Gave it an attempt with my Blood DK to see if it happens on all my toons but it's a little low on gear and couldn't push her to P2 in time.

I have never seen a case where the bot started focusing other mobs between eggswith Singular. I ran the raid half a dozen times just yesterday and the attacking of the eggs is a forced targeting in code. If you can provide me with a log where this happens with Singular, I will try to reproduce it, but I assume this happened with Tuanha. And then I can't do anything about it. Tuanha may offer good DPS, but is very, very flawed product when it comes to obeying orders from profiles. It seems to constantly override the points of interest that are set for it and that is a Tuanha problem which you would have to discuss with him.

EDIT: It is true that I'd rather see it fixed rather than optionally removed but you may want to think about adding in the boss kill options. I can't imagine it would be difficult, just tedious, since each boss seems to have it's own profile. Primarily useful in Cata raids for characters without the gear to clear, but may be able to do 3/4 of the instance.

I will consider it, but it is not as simple as you might think. If I wouldn't want the profiles blown out of proportion with dozens of conditions in each single file I would have to add this functionality to the companion instead which would still mean moving the profile loading-logic out of every single profile plus having to create custom logic for raids with wings. If for example a user were to disable Rotface in ICC (Boss #6), the bot would have to also skip Professor Putricide (Boss #7) and the Lich King (Boss #12). There are a lot of permutations and hundreds of test runs on all raids to be done to make sure this works right. And on the other end it leads to option bloat which will in turn increase support requests, because users just don't get it. Then I will get support requests asking me why boss A is not killed when boss B is deactivated and I would have to go on tangets to tell them how Blizzard sets up raids. This feature has a big, big question mark next to it. I am not ruling it out, but it is not on my "do it now" list as there are dozens more pressing tasks at hand.

 

[WolfpackPB]

I have never seen a case where the bot started focusing other mobs between eggswith Singular. I ran the raid half a dozen times just yesterday and the attacking of the eggs is a forced targeting in code. If you can provide me with a log where this happens with Singular, I will try to reproduce it, but I assume this happened with Tuanha. And then I can't do anything about it. Tuanha may offer good DPS, but is very, very flawed product when it comes to obeying orders from profiles. It seems to constantly override the points of interest that are set for it and that is a Tuanha problem which you would have to discuss with him.

This is with Singular and Tuanha, I'll try it and post a full log later this afternoon; sorry should have just done so in the beginning.

I will consider it, but it is not as simple as you might think. If I wouldn't want the profiles blown out of proportion with dozens of conditions in each single file I would have to add this functionality to the companion instead which would still mean moving the profile loading-logic out of every single profile plus having to create custom logic for raids with wings. If for example a user were to disable Rotface in ICC (Boss #6), the bot would have to also skip Professor Putricide (Boss #7) and the Lich King (Boss #12). There are a lot of permutations and hundreds of test runs on all raids to be done to make sure this works right. And on the other end it leads to option bloat which will in turn increase support requests, because users just don't get it. Then I will get support requests asking me why boss A is not killed when boss B is deactivated and I would have to go on tangets to tell them how Blizzard sets up raids. This feature has a big, big question mark next to it. I am not ruling it out, but it is not on my "do it now" list as there are dozens more pressing tasks at hand.

True Enough, a simpler solution could also be a per dungeon logic that after X failures / deaths (defined by user) the bot will then skip the instance; so players could say after 1 death don't attempt H Dragonsoul anymore because I know I can't kill Ultraxion. Though that may run into issues for winged raids where you'd say start with military wing in Naxx, fail, then lose out on the other wings that your character is capable of.

 

[WolfpackPB]

Ok, log posted, this starts with my Warrior in the instance already and ends after the first despawn. Thanks for looking into this.

View attachment 3048 2015-12-06 22.22.txt

 

[titanlock]

ill try it with cleared cache. i tried on multiple computers as well so im not sure its cache related my warlock also wasnt very good at sinestra, same sort of issues, would ignore the eggs and whatnot.

 

[Studio60]

I already figured it out and have a fix ready. Just want to do one final run.

 

[Studio60]

Version 1.0.151208.1 has been submitted and is now awaiting approval.

[B][U]1.0.151208.1[/U][/B]
[B][I]Cho'gall[/I][/B]
- Twilight Portal Shapers are now focused when killing trash
[B][I]Sinestra[/I][/B]
- Fixed use of movement speed increasing abilities
- Character now leaves the lava faster after falling down to Sinestra's Lair
- Profile will now be reloaded if the encounter resets
- Fixed targeting priorities to handle eggs becoming immune again

 

[Studio60]

Version 1.0.151208.1 has been approved and is now live.

[B][U]1.0.151208.1[/U][/B]
[B][I]Cho'gall[/I][/B]
- Twilight Portal Shapers are now focused when killing trash
[B][I]Sinestra[/I][/B]
- Fixed use of movement speed increasing abilities
- Character now leaves the lava faster after falling down to Sinestra's Lair
- Profile will now be reloaded if the encounter resets
- Fixed targeting priorities to handle eggs becoming immune again

 

[titanlock]

report

fury war now handles sinestra omlet time properly! thank you.

 

[Studio60]

Sinestra Omelette Time! Haha, I love it.

 

[kamanori]

Hi. My charrectors are pretty much all with okay gear now, so i am now starting to make them do 25m heroics in cata. The ones i've tried so far have went smooth, eksept my gladiator warr.

I am using the guide linked below, since my friends says that its the best one, but still, it dies at Sinestra.

My warr's ilvl is 670, and have the enchants which the guide says to use, and have pretty much the stats the guide recomends on his gear.

Here are my warrs stats unbuffed


Does anyone have any ideas? just too low ilvl, or? any input would help,so thanks in advance^^


http://www.icy-veins.com/wow/gladiator-warrior-pve-dps-stat-priority

 

[Studio60]

Hi. My charrectors are pretty much all with okay gear now, so i am now starting to make them do 25m heroics in cata. The ones i've tried so far have went smooth, eksept my gladiator warr.

I am using the guide linked below, since my friends says that its the best one, but still, it dies at Sinestra.

My warr's ilvl is 670, and have the enchants which the guide says to use, and have pretty much the stats the guide recomends on his gear.

Here are my warrs stats unbuffed
View attachment 194481

Does anyone have any ideas? just too low ilvl, or? any input would help,so thanks in advance^^

http://www.icy-veins.com/wow/gladiator-warrior-pve-dps-stat-priority

Most of the time these things are about DPS. If it is not that, it is about selfheal. So if you want to upgrade your gear go for the weapons first and get a 695 baleful empowered 1H weapon as a gladiator the shield is also important, but you can't get a good one from Tanaan. An option would be crafting. The level 5 of 6 Shield is reasonably cheap to craft. Then go and get the Mark of Supreme Doom from Kazzak and equip it when running that raid. On Sinestra there is a lot of damage coming in once the eggs are destroyed. This might kill you, but having the boosted selfheal might save you.

 

[kamanori]

Most of the time these things are about DPS. If it is not that, it is about selfheal. So if you want to upgrade your gear go for the weapons first and get a 695 baleful empowered 1H weapon as a gladiator the shield is also important, but you can't get a good one from Tanaan. An option would be crafting. The level 5 of 6 Shield is reasonably cheap to craft. Then go and get the Mark of Supreme Doom from Kazzak and equip it when running that raid. On Sinestra there is a lot of damage coming in once the eggs are destroyed. This might kill you, but having the boosted selfheal might save you.

Thanks alot, dident know about the shield being that important, always though it was the wep, no matter what class or spec, unless if it was a protection warr ofc, but besides that ^^

But ty, will look at crafting a shield. I am currently running around with the honor pvp shield with crit and mastery, so yeah, it could be a lot better ^^'

And fear not, ever since i read a comment you made on the cata bundle regarding the trinket, i have tried to get it on all my chars. So far I have it on my pala, and oh my daim, it's pretty god damn ridiculous in old raids XD

As always thats for the help ^^

 

[titanlock]

currently having issues on a 680 feral druid. its not returning to melee range and instead trying to chase down eggs, right after killing the eggs. this causes the toon to get "wreck" which is a dot that ramps up really fast and kills you quickly. if you just have it run back to sinestra before taking the adds they should all come to you and avoid the dot

 

[Studio60]

currently having issues on a 680 feral druid. its not returning to melee range and instead trying to chase down eggs, right after killing the eggs. this causes the toon to get "wreck" which is a dot that ramps up really fast and kills you quickly. if you just have it run back to sinestra before taking the adds they should all come to you and avoid the dot

The priorities are a bit of a gamble. Some classes fare better by ignoring the whelps, others need to kill them etc. I'll look into it.

 

[titanlock]

The priorities are a bit of a gamble. Some classes fare better by ignoring the whelps, others need to kill them etc. I'll look into it.

sorry but this cannot be the case. my 705 frost dk which was farming this np before is having the same issue. the adds in the fight are a joke why does it even bother with them after the eggs?