[Plugin] Dungeon/Raid Death Support for Questing botbase

[EchoTiger]

[div=font-family:segoe ui;color:#6795DA;font-size:18pt;font-style:normal; -webkit-font-smoothing:antialiased;text-rendering: optimizelegibility]Welcome![/div]

This is a super simple plugin designed to allow death support inside of a dungeon or raid.
By default the Questing botbase lacks support for going through instance portals or loading screens, so this is an easy solution to fixing that.
This plugin was primarily created for the Azyul project as the majority of the Azyul profiles are dungeon-based.​

[div=font-family:segoe ui;color:#6795DA;font-size:18pt;font-style:normal; -webkit-font-smoothing:antialiased;text-rendering: optimizelegibility]FAQ[/div]

• Hooks into the Questing botbase. So it doesn't work on other botbases.
• Should support all dungeons and raids, and will revive by going into them regardless of which you're running.
• Supports both flying and ground-based deaths.
• Supports any 'go through loading screen' death in which your body is on a different MapID.
• Will not activate if the player dies outside of the instance portal to allow the native death routine to revive the player.
• Fully supports 'disconnections' so that if you die while disconnected, the plugin will be able to return you to the instance.

Simply install this as you would any other plugin. Paste it into your Honorbuddy "Plugin" folder and restart the bot.
Once the bot starts back up, enable the plugin by checking the box on your 'Plugin' menu.
Yellow text will appear on Honorbuddy's log to confirm the plugin is active. From there on out, the bot will enter a instance portal to revive if it dies in one.
​

[div=font-family:segoe ui;color:#6795DA;font-size:18pt;font-style:normal; -webkit-font-smoothing:antialiased;text-rendering: optimizelegibility]Download[/div]

v2
View attachment AzyulDDSupport.zip


v1
View attachment AzyulDDSupport.zip​

[div=font-family:segoe ui;color:#6795DA;font-size:18pt;font-style:normal; -webkit-font-smoothing:antialiased;text-rendering: optimizelegibility]Changelog[/div]

v2
- Added support for dungeons that do not have the corpse location directly on the instance load trigger.
- Added custom navigation for Pit of Saron since Flightor can't navigate the area properly.


v1
- Initial Release.​

 

[Azhemoth]

 

[Nieznany]

any future plans for raids ?

 

[EchoTiger]

any future plans for raids ?

The third bullet points out that it should work for any situation in which your corpse is on a different MapID.
Although I haven't tested it, in theory it should work for raids.

 

[smuoc]

Does this works for timewalking dungeon? Since there is a problem with Pit of Saron, when you die inside he does not fly back inside :/

 

[Stracrafter]

I had to replace
Navigator.PlayerMover.MoveTowards(StyxWoW.Me.CorpsePoint);

by Navigator.MoveTo with exact entrance portal coordinates of a required instance. And it works now! Thank you for useful plugin.

 

[EchoTiger]

Does this works for timewalking dungeon? Since there is a problem with Pit of Saron, when you die inside he does not fly back inside :/

I wrote a fix for this in the next update.

 

[EchoTiger]

I had to replace
Navigator.PlayerMover.MoveTowards(StyxWoW.Me.CorpsePoint);

by Navigator.MoveTo with exact entrance portal coordinates of a required instance. And it works now! Thank you for useful plugin.

I noticed some instances don't place the corpse location directly on the load trigger of the instance.

Given this, I've wrote the plugin to also walk to the corpse point -> then walk directly forward towards the instance.
This seems to have fixed the issue for those instances.

An update should be out soon once I get time to post it up.

 

[noobseals]

It doesn't work in Fireland...
How to make it move to specific coordinates by using Navigator.MoveTo? An example would be great, thank you!

 

[EchoTiger]

It doesn't work in Fireland...

Can you tell me the issue?
Some instance portals do not have your corpse location placed directly on the load trigger - and as a result, the plugin just stands right at the entrance of the portal.

I had made a fix for this, but forgot to release it here.

---

How to make it move to specific coordinates by using Navigator.MoveTo? An example would be great, thank you!

Navigator.MoveTo(new WoWPoint(123, 456, 789));

 

[noobseals]

Can you tell me the issue?
Some instance portals do not have your corpse location placed directly on the load trigger - and as a result, the plugin just stands right at the entrance of the portal.

Just as you said it stopped at the portal.
I used the MoveTo method Stracrafter mentioned, now it can go through the portal but the movement is weird. It seems it think the portal is an obstacle and always wants to go back when it is close to the portal.
Waiting for your updates!

 

[EchoTiger]

Just as you said it stopped at the portal.
I used the MoveTo method Stracrafter mentioned, now it can go through the portal but the movement is weird. It seems it think the portal is an obstacle and always wants to go back when it is close to the portal.
Waiting for your updates!

Updated the original thread with v2.

 

[noobseals]

v2 works! THANK YOU!

 

[Nazaruk]

v2 working like a charm

 

[Lbniese]

I'm using this at the moment while I farm raids and it works flawless so far!

 

[liquidsnake1989]

I'm using this plugin along with Zojak's fireland farm profile. Unfortunately from time to time my toons get bumped in the lava by those big rock-beasts in Firelands, and then they die.

The Death Handler plugin nicely flies the toon back into the raid, but that's where problems start. It seems, somehow, that the 'normal' profile (Zojak's one) thinks you are outside of the raid, because in the chat log I see a message that he tries to reset all instances, but he cant because obviously you yourself are still in it.

Zojak already told that at this moment he can't really update his profiles, but I think a lot of problems would be solved if it was possible for this plugin to leave the instance, once you entered it to revive your corpse. Maybe set it as an option, or I can adjust some code of the plugin for it... Im a programmer myself but I don't really know where to look for it (honestly haven't even looked yet )

Because now the bot will simply wait inside the raid forever

 

[EchoTiger]

I'm using this plugin along with Zojak's fireland farm profile. Unfortunately from time to time my toons get bumped in the lava by those big rock-beasts in Firelands, and then they die.

The Death Handler plugin nicely flies the toon back into the raid, but that's where problems start. It seems, somehow, that the 'normal' profile (Zojak's one) thinks you are outside of the raid, because in the chat log I see a message that he tries to reset all instances, but he cant because obviously you yourself are still in it.

Zojak already told that at this moment he can't really update his profiles, but I think a lot of problems would be solved if it was possible for this plugin to leave the instance, once you entered it to revive your corpse. Maybe set it as an option, or I can adjust some code of the plugin for it... Im a programmer myself but I don't really know where to look for it (honestly haven't even looked yet )

Because now the bot will simply wait inside the raid forever

For this sequence of events to happen, the profile would have to have some sort of death support built into it already.
Which if that's the case, this hard-coded death code would need to be stripped out of the profile.

This plugin pauses the profile code once a death occurs. Once the plugin revives the player, the plugin resumes the QuestOrder logic in which the bot will continue exactly where it left off prior to death.
If the profile immediately attempts to reset after reviving, then something in the profile code is making it abort the code it was executing prior to the death.

Instead of editing the plugin, a better solution would be to figure out what the profile is doing and remove it.
Unless you want it to reset the dungeon after death, then a 'exit dungeon' code could also be added to the plugin.

 

[liquidsnake1989]

I tried your theory and you seem to be right! I saw an entire custom DeathHandlerHook codeblock where a couple of different things happened, but when I removed that entire block it worked nicely. Thx!

 

[EchoTiger]

I tried your theory and you seem to be right! I saw an entire custom DeathHandlerHook codeblock where a couple of different things happened, but when I removed that entire block it worked nicely. Thx!

No problem, good luck!