We have detected that cookies are not enabled on your browser. Please enable cookies to ensure the proper experience.
Results 1 to 17 of 17
  1. #1

    [Plugin] Epic Battle Plugin

    EpicBattlePlugin displays useful information for all Epic Battle spaces. This includes which quests you can expect to get during each wave, how much longer a wave has until it will end, how much longer until the side quest starts for the current wave, and how long your traps have before they disappear. You can download EpicBattlePlugin from LOTROInterface here.

    IN THE CASE A PHASE FAILS TO START CORRECTLY DUE TO BEING OUT OF RANGE OF ITS CALLOUT, YOU CAN MANUALLY START A WAVE/PHASE BY RIGHT CLICKING THE WAVE LABEL.

    Quote:
    Issues with Minas Tirith Epic Battles
    Similar to Pelargir, the main problem with the Minas Tirith epic battles is that callouts do not occur in a global chat channel, they happen in the "say" channel, so if you are not close enough to the source, there is no way for the plugin to know when you have moved to the next phase of the battle. In these fights, Gandalf does most of the callouts, so you need to be near him to get them. Unfortunately they is just not a better mechanic for knowing when the fight has progressed to the next phase.

    Unlike all the epic battles that came before it, Minas Tirith epic battle quests do not specify if they are a fellowship or small fellowship version (solo/duo Defence of Minas Tirith and small fellowship Defence of Minas Tirith are both called The Defence of Minas Tirith). I was using this difference to know if you were doing a solo version or a non-solo version. Without this difference, there's not much else for me to use to get which instance you are in, other than checking how many people are in your fellowship party, which is what I have currently done. However, I dislike having to use this API calls because they are buggy (if you stay in a fellowship and have people enter/leave enough, it can get out of sync last time I checked, which means the number of people in your party may be wrong), and accessing the player's fellowship use to cause crashes, and I had a crash yesterday while running Minas Tirith when I tried to add myself as target assist, which is exactly the crash I remember from the Smaug days and my Smaug plugin. If there are enough reports of problems with this method, I will remove it and add a simple pop up dialog box that asks you which instance you are in when you enter a Minas Tirith epic battle. Not ideal, but would definitely be preferable to crashes.

    Minas Tirith Epic Battles WILL NOT WORK IN FRENCH OR GERMAN CLIENTS.

    Epic foes, similar to Pelargir, will have their timers next to them in the plugin so you can see how long you have before you lose platinum. Unlike Pelargir, however, the epic foes spawn 5 or 6 seconds after the quest starts, so I conservatively added 4 seconds to the 30 second timer, so do not be alarmed when you see more than 34 seconds on the countdown even though you are suppose to kill them in 30 seconds.

    Luckily, it seems the waves are pretty consistent (quests and lengths being +/- 30 seconds on normal runs), so timers are relatively accurate.

    Quote:
    Issues with Retaking Pelargir
    While I have added support for Retaking Pelargir, unfortunately the instance is very inaccurate due to a number of factors.

    The first is that the "callouts" for each wave, the ones my plugin use to know when things are happening, are not global, they are "said" in the regular "say" channel, which means if you are too far away from the speaker (normally Elrohir or Elladan), you will not get it in the chat channel and thus the plugin will not know what is going on. This mainly affects Phase 1 (winch) and Phase 3 (Aragorn's flank). If you do not receive the chat callout, you can right click near the Wave label and/or numbers, and manually start the wave.

    The second is that the duration of each phase is very inconsistent. For example, the winch phase can last anywhere from ~320 seconds to ~460 seconds (from what I have seen). There doesn't seem to be a good indication of why this is either. So the "Wave Ends In" timer simply cannot know how much time is actually left. This affects the 2nd and 3rd phases greatly, because it alters how long you have until the side quest, epic foe, and secondary foe start. By a large margin. And, the timing of events changes greatly if you drop hooks and/or use the ballista/catapults. For example, the 2nd phase seems to start around when Elrohir says "Pillagers, everywhere. Let us rout them, then. Aragorn wishes to face the entire Corsair host." However, if you immediately left the winch phase before Aragorn shouts out "Excellent work, join us at the piers!", the wave won't actually start until after that shout out has occurred, so there's a long delay between when the plugin thinks the phase started and when it actually start. And unfortunately, the "Join us at the piers" does not show up in chat, so there's no way to track when it happens.

    All in all, the "Wave Ends in", and the quest timers will NOT be very accurate at all.

    However, the timers next to the epic/secondary foes will be at least mostly accurate in how long you have left to kill that foe before you lose platinum. Note that these timers start when the quest starts or when the text appears on screen for the secondary foe, and not when someone first touches the boss, so they should be a bit more accurate than using combat timing.

    If, in the future, I discover a better method for determining times in Pelargir, I will make revisions accordingly.

    Features:

    • Displays which wave you currently are on, and if any other waves have started.
      A green label behind the wave number indicates that is the current wave you are on.
      A yellow label behind the wave number indicates that the wave has started, but you have not finished the current wave.
      A red label behind the wave number indicates that the wave has ended.
      A black/dark grey label behind the wave number indicates that the wave is not used in the current Epic Battle instance.
    • Display which quests you will get during each wave.
      Most of the Epic Battle spaces have a set side quest order depending on which "side" you get first. For instance, in Solo Helm's Dike, if you get the Western side first, the quest order will be Stone Obstruction during the western assault, Statue of Helm Hammerhand during the eastern assault, and then either Flames at the Gate or Powder at the Gate during the final wave (3rd wave is always random between those two quests). So the window will display the first two quests and then display RANDOM for the 3rd quest.
      Similar to the wave labels, the quest labels will change colors depending on which is the next quest. The current quest will be green, the previous quests will be red, and any quest not used during the epic battle you are in will be dark grey.
      For quest orders that cannot be known (due to either the quest being random or due to the raids random order), you can hover over the quest to get a list of all possible side quests during that wave.
    • Shows how long until the wave ends.
      Depending on the Epic Battle you are in, the waves have a pre-determined maximum duration, and even if you don't kill every orc in the wave, the wave will end at that time. It's roughly 10 minutes for most of the solo/duo ones, and upwards of 15 minutes for Deeping Wall raid. Most of these should be correct, but Helm's Dike 6 man and Deeping Wall raid may not be. Please note this is a MAXIMUM and the wave may end earlier if you speed it up using catapults or if you don't knock over ladders. Also be aware that certain random factors can sometimes cause the duration to be a bit longer, however this timer should generally be correct +/-30 seconds.
    • A kill count of the wave.
      This is an ESTIMATED number of mobs you have killed during the current wave. It estimates this using a "kills per second" ratio that I have calculated from running the instances. It will also add in any mobs you kill that are still out in the battlefield, using catapults or ballistas.
    • Estimated time until the side quest starts for the current wave.
      Side quests don't start on a timer, they start at a certain kill threshold in the wave. For example, if there's 100 orcs total in a wave, and you need to kill 25% of them to start the quest, then once 25 orcs have died (regardless of how you killed them and how long it took), the quest will start. However, I have noticed that the mobs have to reach the soldiers before the side quest will start, regardless of how many you have actually killed. Also, I also feel that it depends on which mobs you kill can cause the side quest to start sooner or later. This timer should be used only as an estimate and is probably going to be off +/- 30 seconds, especially if you use catapults (in Deeping Wall for example). It will be more accurate in the more static instances (Deeping-coomb, Glittering Caves), because you can't really affect the wave.
    • Shows your traps and how long they have until they expire.
      The OLDEST trap will be on the left (closes to the trap label), and as they expire, the other traps will move to the left to take its place. *Traps may expire before their timer runs out if the traps max trigger count is reached. The default trigger count is 5, but can be increased to a max of 22 with the trait. The plugin cannot know if a trap has expired in this way, so the timer may still be counting down even if the trap is gone.
    • You can manually set an Epic Battle to start by right clicking on the top bar of the window. You will need to do this if you have already completed the main quest for that instance today.
    • You can manually start or end a wave by right clicking the Wave label or any of the wave numbers.
      If you start a new wave, the current wave will be ended.
      You can use the above features (start a new Epic Battle instance and wave starting) to see which quests are possible, without having to run an instance.
      Sometimes you won't get the wave callouts (this happens to me in Helm's Dike Fellowship and Deeping Wall raid a lot), so you can manually start the waves this way.
    • You can minimize the window by double clicking on the platinum medal in the upper left hand corner. This will minimize the window into that medal, which you can then double click again to bring the window back up.
      The plugin continues to run while it is minimized, so you can use it even if it is minimized.
    • An Options Window has been added. It can be brought up by typing "/ebp options" (without the quotes) or by right clicking anywhere on the main window, and selecting Options. The Options Window has the following settings:
      Opacity: Set the opacity of the main window. When you minimize the window, the medal ignores opacity (so you can find it again).
      Scale Window: Allows you to make the window smaller. You can also scale the window by moving your mouse to the lower right hand corner, and clicking and dragging the green box that appears.
      Always Load Minimized: If checked, when the plugin is loaded, the window will load minimized.
      Minimize Window After Battle: After the plugin has determined a battle is over (or you left one), it will minimize the window.
      Maximize Window for Battle: When an epic battle starts, the plugin will maximize the window if it is not already maximized.
      Make Additional Save Calls: If checked, the plugin will save more often. Use this if you notice the window position is not being saved.
    • Vindar Patch added to begin support for foreign clients. German clients should now be able to use EpicBattlePlugin and have it work on their clients. Thanks to Burgus for translations!
    • No dependencies.


    Future Plans:

    • Continue working on the information needed, including max duration of waves, and approximate side quest start timers.
    • Add additional features as desired and appropriate.


    Known Issues:

    • The plugin uses the bestowed main quest when you enter an Epic Battle space to know which one it is and which size it is. You will have to manually set the Epic Battle instance if you do not have that main quest (due to completing it already) or if you don't have EpicBattlePlugin loaded when you first enter the instance.
    • The trap timers will only count down when a wave is in progress, but will correctly end once another wave starts.
    • Due to the plugin listening for certain callouts during the fights, if for some reason you don't get that callout, it can cause the plugin to be incorrect. For example, I've noticed in Deeping Wall Raid you can be far enough away from the people who shout out which side is being attacked to not get the callout for that attack. This causes the plugin to not realize the attack is happening, and means you will have to manually set the wave to start.
    • Because the information in the Epic Battles in not exact (the side quests don't start exactly at the same time or kill count each time), the timers and kill counts will never be an exact measurement of what is going on in the instance. Please only use those numbers as guidelines.


    You may contact me with any problems as I continue working on the plugin. If you notice that an Epic Battle instance seems to always be way off on the timers (either the max duration timer or the quest start timer), let me know. I'll need which instance it is, what side the timer is wrong on, and which wave. So for example, if you notice that in Helm's Dike solo, when you are on the western side during the 2nd wave, the side quest always starts way before the timer counts down to 0, let me know and I'll see if I can find a better estimate.

    Version History:

    Version 1.4
    • Fixed a type with the word "Defense" in the Helm's Dike quest since LOTRO uses British English.
    • Added Minas Tirith Epic Battles.
    • Removed a chat printout in the Pelargir Epic Battle.
    • Deeping Wall - Raid will now display the 3rd quest once the 2nd wave has started, since the 3rd quest is known at that point.
    • Added a local version history text file to the plugin folder.
    Last edited by Stever1388; Jan 09 2016 at 01:00 PM. Reason: Updated to v1.4

  2. #2
    I have updated EpicBattlePlugin to v1.1, which is its first non-Alpha release. It features a ton of new options that can be set, and should be relatively accurate for the wave duration timer and the quest starting timer, within +/-30 seconds for either. You can download EpicBattlePlugin from LOTROInterface here.

  3. #3
    Join Date
    Jun 2011
    Location
    Over the Top
    Posts
    712
    Hello Are you going to update your awesome plugin with the new Big Battle ?
    Cheers.


  4. #4
    Join Date
    Aug 2010
    Location
    your mind
    Posts
    3,880
    While this is one of the most useful plugins of the half dozen I use, and it gets used daily, I might wait until Pelargir is finalized before updating to include it, as one side quest still not in, and other calls are not implemented yet (like announcing named NPCs arrivals).

    Similarly the fellowship sized version is due in the future, and since the ability to move barricades was removed, there's not as much setup that time matters for. The notes on lotrointerface make it sound like the author is busy, so if there is time to update it, might make sense to wait until the fellowship version is in the game and the solo/duo is not going to change again/require further update/work.
    Link to our community LOTRO store google spreadsheet pricelist and conversion rates, please contribute too!: https://goo.gl/wxPqCm

  5. #5
    Quote Originally Posted by Anolus View Post
    Hello Are you going to update your awesome plugin with the new Big Battle ?
    Cheers.
    Do you really need it?
    The first part is always the same and then you have 3 possible quests at the piers, troll or protecting citizens or killing pillagers. Plus the "boss".
    After that is either minstrel or archer and again the "boss". Nothing much to set up and if you do need to set that single balista you can actually carry around, you have enough time to do so. Personally I still havent found any use for it.

  6. #6
    Join Date
    Oct 2010
    Location
    Australia
    Posts
    89
    Agreed,
    Not really needed till the fellowship version.

    There are three things all wise men fear: the sea in storm, a night with no moon, and the anger of a gentle man.”

  7. #7
    Join Date
    Jun 2011
    Location
    Hungary
    Posts
    66
    If you really want an updated version, you can use my own modified EBP.
    http://lotro.bunny.hu/bigbattle_plugin.html (download=LETÖLTÉS)
    It is expanded version with some new feature and Pelargír is also added. It is made for hungarian players but only the quest hints is hungarian everything else english, so everyone can use it. If Steve decide he never want to continue this superb plugin, I will be piblish my version to the lotrointerface. But till there is chance to Steve doing his own version I do not want to make an other plugin with same functions based on someone jobs.

    (ps: If you want to read my page you can use google translate )

  8. #8
    Join Date
    Jun 2011
    Location
    Schleswig-Holstein
    Posts
    694
    Will there be adapted for Pelargir? I use the latest version of Bunny and have adapted it so that it goes on the German client. As far as the plugin is wonderful, but just right timing in the plugin not what the quest to tackle at Pelargir etc. Would be nice if it is further developed. I'll be there at the end, for me just missing the end levels in LUA scripting so flawlessly Does it work in Pelargir.

  9. #9

    Update

    I do plan to update the plugin eventually to include Pelargir stuff. It's going to have some additional information that other quests don't have (namely, how much time you have to kill each boss), so I'm waiting for the few fixes they are added with the next patch (more time to kill some epic foes, call-outs for the secondary epic foes), and also the fact that I am pretty busy with other, non-LOTRO, related projects. I also have another plugin for the Deeping Wall raid to help organize classes into the groups and where they need to go for each side quest. It's still in alpha but I'd like to get it released as well at some point.

  10. #10
    Quote Originally Posted by Stever1388 View Post
    I do plan to update the plugin eventually to include Pelargir stuff. It's going to have some additional information that other quests don't have (namely, how much time you have to kill each boss), so I'm waiting for the few fixes they are added with the next patch (more time to kill some epic foes, call-outs for the secondary epic foes), and also the fact that I am pretty busy with other, non-LOTRO, related projects. I also have another plugin for the Deeping Wall raid to help organize classes into the groups and where they need to go for each side quest. It's still in alpha but I'd like to get it released as well at some point.
    I appreciate the work you've done on this plugin, but I'm wondering if you're going to work on it anymore. It has been over a year since your last update.

  11. #11

    Pelargir is now supported!

    I am proud to announce that I have (finally) added support for Retaking Pelargir. This is an initial release which has been semi tested, and the fellowship version is still wonky with the numbers it shows. Over the next week I will be testing and refining everything a bit more.

    The main addition is that for each epic foe during each phase, the plugin will show how many seconds you have left to kill the epic foe before you lose platinum on that epic foe. However, many of the timers are not correct, and once they are, the actual time you have left may be slightly different (probably +/- 2 seconds or so).

    Enjoy!

  12. #12
    Join Date
    Aug 2010
    Location
    your mind
    Posts
    3,880
    Funny, a kinmate was just asking if RP support had been added, if nothing else than to have the tripwire cooldown timers available, heh, thanks for your continued work on this!
    Link to our community LOTRO store google spreadsheet pricelist and conversion rates, please contribute too!: https://goo.gl/wxPqCm

  13. #13
    Join Date
    Jun 2010
    Posts
    2,312
    Stever,

    I tried this the other night in a 6 man Pelargir and it completely freaked out and just started spamming the chat window. I think everytime something died it would spam. I had to unload it for sanity.

    I went back to using Bunny's modded version which works fine most of the time (although not perfectly - it is not really updated for 6 man)
    Chromite/Grumbletocks/Grumbletunes/Schrade on Landroval, Chromite on Arkenstone, Appendage on Brandywine

  14. #14
    Quote Originally Posted by ChromiteSwiftpaw View Post
    Stever,

    I tried this the other night in a 6 man Pelargir and it completely freaked out and just started spamming the chat window. I think everytime something died it would spam. I had to unload it for sanity.

    I went back to using Bunny's modded version which works fine most of the time (although not perfectly - it is not really updated for 6 man)
    Yeah the 6 man version is bonked, apologies for that. The next build will have that fixed as well have better numbers for everything. Should have it out towards the end of the week.

  15. #15

    Pelargir Fellowship fixed

    I have fixed the issues with Pelargir fellowship, so that should not work. Please be aware of the following:

    Issues with Retaking Pelargir
    While I have added support for Retaking Pelargir, unfortunately the instance is very inaccurate due to a number of factors.

    The first is that the "callouts" for each wave, the ones my plugin use to know when things are happening, are not global, they are "said" in the regular "say" channel, which means if you are too far away from the speaker (normally Elrohir or Elladan), you will not get it in the chat channel and thus the plugin will not know what is going on. This mainly affects Phase 1 (winch) and Phase 3 (Aragorn's flank). If you do not receive the chat callout, you can right click near the Wave label and/or numbers, and manually start the wave.

    The second is that the duration of each phase is very inconsistent. For example, the winch phase can last anywhere from ~320 seconds to ~460 seconds (from what I have seen). There doesn't seem to be a good indication of why this is either. So the "Wave Ends In" timer simply cannot know how much time is actually left. This affects the 2nd and 3rd phases greatly, because it alters how long you have until the side quest, epic foe, and secondary foe start. By a large margin. And, the timing of events changes greatly if you drop hooks and/or use the ballista/catapults. For example, the 2nd phase seems to start around when Elrohir says "Pillagers, everywhere. Let us rout them, then. Aragorn wishes to face the entire Corsair host." However, if you immediately left the winch phase before Aragorn shouts out "Excellent work, join us at the piers!", the wave won't actually start until after that shout out has occurred, so there's a long delay between when the plugin thinks the phase started and when it actually start. And unfortunately, the "Join us at the piers" does not show up in chat, so there's no way to track when it happens.

    All in all, the "Wave Ends in", and the quest timers will NOT be very accurate at all.

    However, the timers next to the epic/secondary foes will be at least mostly accurate in how long you have left to kill that foe before you lose platinum. Note that these timers start when the quest starts or when the text appears on screen for the secondary foe, and not when someone first touches the boss, so they should be a bit more accurate than using combat timing.

    If, in the future, I discover a better method for determining times in Pelargir, I will make revisions accordingly.

  16. #16

    Updated to v1.4 - Minas Tirith Epic Battles!

    I have updated the Epic Battle Plugin to now include the Minas Tirith Epic Battles, with the following note:

    Issues with Minas Tirith Epic Battles
    Similar to Pelargir, the main problem with the Minas Tirith epic battles is that callouts do not occur in a global chat channel, they happen in the "say" channel, so if you are not close enough to the source, there is no way for the plugin to know when you have moved to the next phase of the battle. In these fights, Gandalf does most of the callouts, so you need to be near him to get them. Unfortunately they is just not a better mechanic for knowing when the fight has progressed to the next phase.

    Unlike all the epic battles that came before it, Minas Tirith epic battle quests do not specify if they are a fellowship or small fellowship version (solo/duo Defence of Minas Tirith and small fellowship Defence of Minas Tirith are both called The Defence of Minas Tirith). I was using this difference to know if you were doing a solo version or a non-solo version. Without this difference, there's not much else for me to use to get which instance you are in, other than checking how many people are in your fellowship party, which is what I have currently done. However, I dislike having to use this API calls because they are buggy (if you stay in a fellowship and have people enter/leave enough, it can get out of sync last time I checked, which means the number of people in your party may be wrong), and accessing the player's fellowship use to cause crashes, and I had a crash yesterday while running Minas Tirith when I tried to add myself as target assist, which is exactly the crash I remember from the Smaug days and my Smaug plugin. If there are enough reports of problems with this method, I will remove it and add a simple pop up dialog box that asks you which instance you are in when you enter a Minas Tirith epic battle. Not ideal, but would definitely be preferable to crashes.

    Minas Tirith Epic Battles WILL NOT WORK IN FRENCH OR GERMAN CLIENTS.

    Epic foes, similar to Pelargir, will have their timers next to them in the plugin so you can see how long you have before you lose platinum. Unlike Pelargir, however, the epic foes spawn 5 or 6 seconds after the quest starts, so I conservatively added 4 seconds to the 30 second timer, so do not be alarmed when you see more than 34 seconds on the countdown even though you are suppose to kill them in 30 seconds.

    Luckily, it seems the waves are pretty consistent (quests and lengths being +/- 30 seconds on normal runs), so timers are relatively accurate.

  17. #17

    Problem with v1.4 Download

    For some reason the upload I did for the new version didn't go through - I must not have selected the file to upload it or I didn't select the "update version" so it didn't process correctly, just my text changes did. Hopefully now it should be good to go. Sorry about that!

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

This form's session has expired. You need to reload the page.

Reload