Jump to content

Jazra

Members
  • Posts

    103
  • Joined

Everything posted by Jazra

  1. We've been using the first method for many weeks now and it's worked perfectly for us. We usually have one if not two PT dps in our raids with one being assigned the job to taunt as soon as the Incinerate Armor starts casting. He does just about the same thing, positioning wise, that the Double Destruction soakers do, which is jump in front of the tank. As soon as the the Incinerate Armor debuff is cast on our PT dps taunter, the FB tank taunts back and the taunter goes back to his position with the rest of the dps on FB's side. Really the only thing to worry about is if the tank taunts back fast enough from the dps taunter. Because while casting Incinerate Armor, the taunter takes at least one hit, which is fine, but taking a second after the debuff goes off is a one shot. So as long as you have speedy taunters, that are quick on their feet, it's a very easy and simply solution to get around tank swapping.
  2. My opinion is that they'll release Nightmare mode for EC as well as the revamped Nightmare Modes that they said they were doing for EV and KP as a package deal for the August content. Then 1.4 will be the first F2P patch with Terror from Beyond because it is advertised under the F2P page. My two cents.
  3. I gave them more information... They are very much aware of this problem. I've gotten a personal response regarding it and there are multiple threads about it.
  4. Yes, this is the most common way it's done. Usually what we do as well.
  5. Personally I've never done it with only three healers but I'm sure it's very possible. My question to you is, why would you? You can five heal it with three tanks and not hit enrage if your dps is pulling their weight.
  6. This is due to instance switching. When there are multiple instances of the same encounter you have the ability to change instances on purpose or by accident, which seems to be what has happened to your group. To prevent switching instances, after a wipe, leave one person dead inside the instance and have the rest of the group respawn at med center. Leaving one person inside at all times saves your placemarker in the instance. Once the players go back inside the instance have the last person respawn and come back inside the instance. You should be at the same place.
  7. Three solutions: 1. Bring a Jugg with more common sense than to use an AoE inside the shield. 2. Have your Jugg with no common sense stay on Firebrand during Defensive Systems. 3. Put your Jugg with no common sense on Stormcaller and make him kite.
  8. HM Denova is still very possible to clear on a Tuesday, even with the persistent lag. I would definitely say that T&Z is the hardest fight to clear with the lag. But being the first boss, with the least amount of trash to clear before it, it is very easy to switch instances until you get in one with a smaller amount of people before or after you start pulling. On your second and third points, yes it is a bit of a hassle because it takes more time for everyone to run back, but you should never encounter an issue with trash respawning as long as you keep someone inside the instance, everyone but that one person return to med center, and have the first person back inside the instance to call it out so the last person can return to med center and get back inside as quickly as possible. Have a member with a fast load time to be the person to stay inside if you're that pressed for time. I do agree that these issues need to be worked out, but the encounter is by no means impossible.
  9. This has been the subject of other threads (here) and is currently being looked into. Gave them more information
  10. This happened to us as well on an alt run last week. It was an 8 man Story Mode EC. We cleared to Vorgath, wiped from bad RNG and all but one of us released (so as to make sure it didn't toss us in a new phase, forcing us to clear trash again). When attempting to run back in, all but I think two of us that released could not get back inside the instance and encountered the same error message "[server Admin] : Permission to enter on he1034, access denied: could not move player to selected area." After that happened, we were all unable to move, unable to see anyone outside of the instance, unable to see general chat, and our health bars were stuck at 1. I tried multiple times to /stuck and reset my UI. Nothing worked. One person in our group re-logged to find the entire fleet a massive grid and then said they were falling through space. The only thing that fixed the issue for me was to alt+f4 out of the game and start it back up. When I got back in, I was standing inside Denova. But by that time we had called it a night. I believe it is the servers closing down one instance and not allowing anyone back inside of it. This really is a huge problem due to the fact that any wipe you have throughout the night might require resetting the instance or moving to a new one, forcing us to reclear unnecessary trash. Hopefully this can get a serious look at, and we'll receive a fix soon.
  11. Yes, I agree that the lag last night was much worse than last week. I say the lag was the worst on SC&FB. I couldn't see my castbar most of the fight which made me want to rage since I was healing on SC. It was very uncomfortable not knowing if my heal was going to go off before a soaker died. Hopefully Bioware can work this out before I have to deal with that again.
  12. This is already being discussed in the following thread: http://www.swtor.com/community/showthread.php?t=433057
  13. This is just silly. Why change something that wasn't broken? Especially if the change is a step back from what we had. This needs to be looked at again and restored back to what it was.
  14. No, this was changed in 1.2. You no longer have to complete normal mode flashpoints before jumping into hard mode. They also removed the daily lockouts on all hardmode flashpoints.
  15. When there are multiple instances of the same encounter this can happen after a wipe. We learned this in HM EC on Tuesday when a repair break was called. The only way to avoid this is by leaving one person inside the instance at all times.
  16. This happened to us as well in 16 EC on Tuesday. We got switched from instance two to instance four which made us have to clear all the trash after T&Z up to FB&SC again. Unfortunately it didn't respawn the chests. lol
  17. Experienced this on Tuesday as well while clearing 16 HM. The most I saw was five instances of EC. It was quite funny though as a healer, it keep me on the edge of my seat just hoping nobody got caught standing in stupid. We also went back in Wednesday night to clear SM and with only one instance and 43 people, there was still quite a bit of lag.
  18. Had a great time yesterday hanging out at the SWTOR booth and listening to all the Q&A's. Will be seeing all the devs again on Sunday!
  19. Exact same thing happened to our title timed run last night. And the same thing that happened last lockouts. We've been screwed out of our title and loot two weeks in a row for KP. Thank you Bioware.
  20. Yep, got our Infernal title first try last week and KP bugged us. Did it again tonight, we hit a bug on the 4th boss and wiped, went in again and the 3rd boss spawned and then wouldn't let us in the instance so we were forced to reset. Cleared it in 1 hour 36 minutes. No title. Not to mention we only had one exotech and a schematic drop from Bonethrasher and then not a single piece of Rakata or Columi due to the fact we had master loot on. No extra chest either....
×
×
  • Create New...