Jump to content

Apparition

Members
  • Content Count

    1068
  • Joined

  • Days Won

    2

Apparition last won the day on December 16 2019

Apparition had the most liked content!

Community Reputation

858 Excellent

2 Followers

About Apparition

  • Birthday January 12
  1. Oh, I agree. Just that it's been thirteen months now with no fix in sight, so I figured some sort of guide would be helpful until it is fixed.
  2. The league bug has been on Homecoming since it launched thirteen months ago. I had hoped that it would be squashed by now, but alas. Unfortunately, most Homecoming players don't know that the league bug exists, and even fewer know how to work around it. Here is my guide. What is the league bug? Should a league leader invite someone to join his or her league who isn't already on a team, the game sometimes (seemingly at random), won't actually place the player in a team. The league window will show that the player is on a team, but if that player opens his or her team window, that player will see that he or she is not actually on a team. There is no way for the league leader to know however, unless that person realizes it and mentions it to the league leader. The ramifications for the league bug don't impact Hamidon raids. The league bug definitely hits it, but few people notice because you actually don't need to be on a league to get your rewards from Hamidon raids. You only need to get in your attack chain. The real problems are with Rikti mothership raids (both zone and instanced), and Incarnate trials. For zone Rikti mothership raids, people show as on a team in the league window, but actually aren't. If that person is on a level 40 Controller, they're not being sidekicked up to level 49. Up against level 54 Rikti, that is one very dead level 40 Controller. In addition, those affected by the league bug in zone Rikti mothership raids don't get full Vanguard merits. There have been many zone Rikti mothership raids where, at level 50+1, I would only get 550 - 700 Vanguard merits when most on the raid got double that. Why? Because the game only counted the Rikti I personally damaged, not the others that the league window showed were on my team, as I was not actually on a team. The league bug also causes players to be booted from instanced Rikti mothership raids and Incarnate trials. Some league leaders lock their teams and their league, but some people are not actually teamed despite the league window showing otherwise. Once the trial starts, those who aren't actually teamed are booted because the team they are supposed to be on is locked. The player order and player teams are also jumbled as a result. After some experimentation, I came upon a method to work around the league bug, and a second but similar method was provided by @GM Solace. How to work around the league bug: 1a. Ideally, the league leader should invite team leaders directly to his or her own team first, (invite to the team, not to the league). Then split them off to separate teams, (one or two for Incarnate trials, two to five for Rikti mothership raids). This will result in creating the league. Then each team leader should directly invite people that want to join to his or her team, (not to the league). or 1b. The league leader keeps his or her own team small at first... three to five people. Then the league leader invites people that want to join directly to his or her team, (not to the league). Once joined, the league leader should move the new league member to the appropriate team. Only shortly before starting should the league leader fill his or her own team. This is the method that I use, personally. 2. Do NOT lock the league, and do NOT lock teams on the league. On the extreme off chance that, even with step 1a or 1b, a player is impacted by the league bug, this will still allow him or her to zone in to the instance. Otherwise, if the person is impacted by the league bug and he or she is not actually on a team, he or she will be spat out when the league zones. Zone Rikti mothership raid league leaders only need to use either step 1a or step 1b to work around the league bug, as no instance is involved. Instanced Rikti mothership raid and Incarnate trial league leaders however must use both steps 1a or 1b and 2 in order to work around the league bug. Using this method, I have not once ever had an instanced Rikti mothership raid drop someone upon zoning in, nor "blow up" teams, and I've run multiple instanced Rikti mothership raids per week since it was added to the game in October 2019. I hope that this guide helps, and will hopefully lead to more players getting their due Vanguard merits in zone Rikti mothership raids, and lead to less league breakage on instanced Rikti mothership raids and Incarnate trials.
  3. But my point is that the league bug also negatively impacts zone MSRs, just in a different and less obvious way. Most zone MSR leaders and players are entirely unaware of it because most people aren’t paying attention to their team window nor their Vanguard merit count. For everyone to get the due amount of Vanguard merits, zone MSR leaders should be forming up leagues the exact same way I form them for instanced MSRs. Zone MSRs are only easier, but certainly not foolproof, if they are formed without concern of the league bug and making sure everyone involved gets their due Vanguard merits.
  4. I've never played Staff before, and haven't played Electric Armor since prior to sunset, so I'd appreciate any feedback on this build. It's pretty much specifically meant as a lean, mean, Rikti killing machine. Villain Plan by Mids' Reborn : Hero Designer 2.7.2.10 https://github.com/Crytilis/mids-reborn-hero-designer Click this DataLink to open the build! Level 50 Mutation Brute Primary Power Set: Staff Fighting Secondary Power Set: Electric Armor Power Pool: Flight Power Pool: Speed Power Pool: Fighting Power Pool: Leaping Villain Profile: Level 1: Precise Strike -- SprBlsCol-Acc/Dmg:50(A), SprBlsCol-Dmg/EndRdx:50(3), SprBlsCol-Acc/Dmg/EndRdx:50(11), SprBlsCol-Acc/Dmg/Rchg:50(23), SprBlsCol-Dmg/EndRdx/Acc/Rchg:50(37), SprBlsCol-Rchg/HoldProc:50(43) Level 1: Charged Armor -- UnbGrd-ResDam:50(A), UnbGrd-ResDam/EndRdx:50(3), UnbGrd-Rchg/ResDam:50(13), UnbGrd-ResDam/EndRdx/Rchg:50(31), ImpArm-ResPsi:40(37), GldArm-3defTpProc:50(43) Level 2: Guarded Spin -- SprBrtFur-Acc/Dmg:50(A), SprBrtFur-Dmg/Rchg:50(5), SprBrtFur-Acc/Dmg/Rchg:50(13), SprBrtFur-Dmg/EndRdx/Rchg:50(31), SprBrtFur-Acc/Dmg/EndRdx/Rchg:50(39), SprBrtFur-Rech/Fury:50(43) Level 4: Lightning Field -- SprAvl-Acc/Dmg:50(A), SprAvl-Dmg/EndRdx:50(7), SprAvl-Acc/Dmg/EndRdx:50(19), SprAvl-Acc/Dmg/EndRdx/Rchg:50(33), SprAvl-Rchg/KDProc:50(39), FuroftheG-ResDeb%:50(46) Level 6: Conductive Shield -- TtnCtn-ResDam/EndRdx:50(A), TtnCtn-ResDam/EndRdx/Rchg:50(9), TtnCtn-ResDam:50(19), TtnCtn-EndRdx:50(34), StdPrt-ResDam/Def+:30(40), ImpArm-ResPsi:40(46) Level 8: Eye of the Storm -- Arm-Dmg/Rchg:50(A), Arm-Acc/Dmg/Rchg:50(9), Arm-Acc/Rchg:50(21), Arm-Dmg/EndRdx:50(34), Arm-Dam%:50(40), FrcFdb-Rechg%:50(46) Level 10: Fly -- BlsoftheZ-Travel/EndRdx:50(A), BlsoftheZ-ResKB:50(11) Level 12: Staff Mastery Level 14: Super Speed -- BlsoftheZ-ResKB:50(A) Level 16: Static Shield -- UnbGrd-ResDam:50(A), UnbGrd-ResDam/EndRdx:50(17), UnbGrd-Rchg/ResDam:50(17), UnbGrd-ResDam/EndRdx/Rchg:50(34), ImpArm-ResPsi:40(40) Level 18: Grounded -- Ags-Psi/Status:50(A) Level 20: Serpent's Reach -- Apc-Dmg/Rchg:50(A), Apc-Acc/Dmg/Rchg:50(21), Apc-Acc/Rchg:50(23), Apc-Dmg/EndRdx:50(36), Apc-Dam%:50(42) Level 22: Lightning Reflexes -- Flight-I:50(A) Level 24: Hover -- BlsoftheZ-Travel/EndRdx:50(A), BlsoftheZ-ResKB:50(25), LucoftheG-Def/Rchg+:50(25) Level 26: Innocuous Strikes -- SprUnrFur-Acc/Dmg:50(A), SprUnrFur-Acc/Dmg/Rchg:50(27), SprUnrFur-Dmg/EndRdx/Rchg:50(27), SprUnrFur-Acc/Dmg/EndRdx/Rchg:50(36), SprUnrFur-Rchg/+Regen/+End:50(42) Level 28: Energize -- DctWnd-Heal/EndRdx/Rchg:50(A), NmnCnv-Heal/EndRdx/Rchg:50(29), Prv-Heal/Rchg:50(29) Level 30: Afterburner -- LucoftheG-Def/Rchg+:50(A) Level 32: Sky Splitter -- Hct-Dmg/Rchg:50(A), Hct-Acc/Dmg/Rchg:50(33), Hct-Acc/Rchg:50(33), Hct-Dmg/EndRdx:50(37), Hct-Dam%:50(42), FrcFdb-Rechg%:50(50) Level 35: Power Sink -- EnrMnp-Stun%:20(A), PrfShf-EndMod/Acc:50(36) Level 38: Hasten -- RechRdx-I:50(A), RechRdx-I:50(39) Level 41: Kick -- Empty(A) Level 44: Tough -- UnbGrd-ResDam/EndRdx:50(A), UnbGrd-Rchg/ResDam:50(45), UnbGrd-ResDam/EndRdx/Rchg:50(45), UnbGrd-Max HP%:50(45) Level 47: Weave -- LucoftheG-Def/EndRdx:50(A), LucoftheG-Def/EndRdx/Rchg:50(48), LucoftheG-Def/Rchg+:50(48), ShlWal-ResDam/Re TP:50(48) Level 49: Combat Jumping -- LucoftheG-Def/EndRdx:50(A), LucoftheG-Def:50(50), LucoftheG-Def/Rchg+:50(50) Level 1: Brawl -- Empty(A) Level 1: Prestige Power Dash -- Empty(A) Level 1: Prestige Power Slide -- Clr-Stlth:50(A) Level 1: Prestige Power Quick -- Empty(A) Level 1: Prestige Power Rush -- Empty(A) Level 1: Prestige Power Surge -- Empty(A) Level 1: Fury Level 1: Sprint -- Empty(A) Level 2: Rest -- IntRdx-I:50(A) Level 4: Ninja Run Level 2: Swift -- Flight-I:50(A) Level 2: Health -- Mrc-Rcvry+:40(A), NmnCnv-Regen/Rcvry+:50(5), Pnc-Heal/+End:50(15), Prv-Absorb%:50(31) Level 2: Hurdle -- Jump-I:50(A) Level 2: Stamina -- PrfShf-EndMod:50(A), PrfShf-End%:50(7), EndMod-I:50(15) Level 1: Combo Level 1 Level 1: Combo Level 2 Level 1: Combo Level 3 Level 12: Form of the Body Level 12: Form of the Mind Level 12: Form of the Soul Level 0: Born In Battle Level 0: High Pain Threshold Level 0: Invader Level 0: Marshal Level 50: Musculature Radial Paragon Level 50: Degenerative Core Flawless Interface Level 50: Ion Core Final Judgement Level 50: Ageless Radial Epiphany Level 50: Longbow Radial Superior Ally Level 50: Assault Radial Embodiment ------------ | Copy & Paste this data into Mids' Reborn : Hero Designer to view the build | |-------------------------------------------------------------------| |MxDz;1625;756;1512;HEX;| |78DA6594CB4F135114C6EF7406A10FA050DAF214DA027DC1D0AA2C7C85A05013A50| |68351E3A669EA804D2A25ED90E8D2852B378ACF851A105071E19FE23B6AA27B3506| |75A15157F574BE93CE249DA4F99D7BEEF7DD7BEEABE98B53AE67472E4F08C979B89| |02D9733874ACBBAD6945ED6B37ABEB8280BFA1AE9D76DE43369ADA069EA9C9E9D9F| |CFA4F20BE7F5FCE2422FBAA6B4796DB1ACA9D3052DA797F2B9CC64E942B1249CB3C| |562414D15AA628711CF2D69DAB966A4790897D19AD1B24BD4F04C2FE573EA6429A7| |D320E96C59D74A973AA98471FA3D0F08FE2A0DE29A22445211B6EBA06305F4DD000| |76F82B15BE07AD526B1F7970CEF6FD0F507DCF9171C8C92304CDE5D68BFA07925F6| |4AABC8296BEC7DC8DE757078038C6D821BE492D92BDF432D3BEE83ED0FC08155707| |80D1C9D8077935C0DEC6D884946AE69146C57C1C01818F613FBC8CBB5BF0CE0E8AA| |DEC6BD36D2D845D33EB0633F183800860FDA30EF15D049463BBC92FD23728E4FE02| |B1AD7899A2A21D23543279AB9FF11B55AD1AFB4F23EBB799FDDBCCF01DEE730D7FA| |98D46DF088B671ACE71DCDE3C1D88A6794EB5641DF18184A80D124E67E426A2F8FE| |30D09A3CF4E35FA318ECDCF6BE9E45A3BBD98EB3DCDD5C57375B97006DD2DCC5630| |E406A36DE016A97B78DC9EE3923157EF49E637D9A0F0D191F0FEF4F15C1F68AE7E3| |E97FE30EA1F8830A3E0608CD715479D493E97A7E40A1A97B82205AF52CE4375DD86| |3648EB1CC2DAA5A138D63ECCB4515F84EB8854E8133265E250CB713E9D113E9D113| |E9D917F7CD349ABB256756385631EA697790C5A1F6913D0DA12AC4D763059DBABD4| |5E71F5125135B1BA4C42A9BD56BA8ABC0B75AADD75993D759994395265A6AE7756E| |14ECA483D7C63DCF46291AB6C3B6A2F5F487CA37E9839593A8A1BAC9CC2E9B604F8| |DF601BFC6EF547E0FF69E66CD20AD6B6E30ED83200CD675FADD2CA174BFCD512BFB| |6BCC437D598F36F2DF10947F53E203E6D89CF58E2B39678869E5C92E394DF8CBB3A| |CCF86E55C3E37BBC667E2B68E6FF038AC307B0| |-------------------------------------------------------------------|
  5. Like @Black Zot, that is because the people forming the leagues either don't know how to work around the league bug, or don't care to for whatever reason. Since Homecoming started, leagues can easily be bugged. It impacts everything... Hamidon raids, zone MSRs, instanced MSRs, and iTrials. It's just least noticeable on Hamidon raids. If the league leader directly invites people to the league (not the team, the league), there's a chance that the game will place the player in the league, but not on a team. The league window will show that player is on a team, but if that player opens up his or her team window, that player will see that he or she is not actually on a team. There is no way for the league leader to know, unless the person realizes it and informs the league leader. The league bug impacts zone MSRs by dramatically reducing the number of Vanguard merits for some people. They think they're on a team because the league window shows that they are... but in reality, they are not. So they're only getting Vanguard merits for the Rikti they have directly attacked. This happened to me very consistently whenever I joined other people's zone MSRs from May through July of last year. It lead me to start leading my own MSRs again because the vast majority of MSR leaders on the Excelsior server organized leagues in ways that directly resulted in the league bug. For instanced MSRs and iTrials, the league bug results in, as you have seen, people being dropped from the league and/or whole teams being blown apart upon entering the instance. There are two things you have to do to work around the league bug. This should be done for both zone MSRs and league MSRs, as well as iTrials. 1a. Ideally, the league leader should invite team leaders directly to his or her own team first, (invite to the team, not to the league). Then split them off to separate teams, (one or two for iTrials, two to five for MSRs). This will result in creating the league. Then each team leader should directly invite people that want to join to his or her team, (not to the league). 1b. The league leader keeps his or her own team small at first... three to five people. Then the league leader invites people that want to join directly to his or her team, (not to the league). Once joined, the league leader should move the new league member to the appropriate team. Only shortly before starting should the league leader fill his or her own team. This is the method that I use, personally. 2. Do NOT lock the league. On the extreme off chance that, even with step 1a or 1b, someone is impacted by the league bug, this will still allow him or her to zone in to the instance. Otherwise, if the person is impacted by the league bug and he or she is not actually on a team, he or she will be spat out when the league zones. (You see this a lot with iTrials.) Using this method, I have not once ever had an instanced MSR drop someone upon zoning in, nor "blow up" teams, and I've run multiple instanced MSRs per week since it was added to the game. Now ideally the league bug would be fixed so these two steps wouldn't be needed, but as I said it impacts both zone MSRs and instanced MSRs (as well as iTrials), so there's no real difference there.
  6. But that only happens if you lock the league prior to start. I've run over one hundred instanced MSRs, and that has never happened.
  7. I really wasn’t trying to turn this into a “them vs. us” thing. I just wanted to raise awareness that the instanced MSR exists, someone does in fact regularly run it and has been since it became available, and that it is a perfectly viable way to run the MSR and is not “wrong.”
  8. That doesn't matter to me. Before sunset, and from July through September of last year, I always restricted my zone MSRs to level 35+ as it was originally designed.
  9. On October 1, 2019, the instanced Rikti mothership raid was added to the game. It's a trial for 16 to 48 players that you can form in any zone, although the best bets are either Kallisti Wharf or Pocket D due to their zone caps of 200 PCs. I've run two or three per week since then on the Excelsior server, one every Thursday evening, and one or two on the weekends. Unfortunately, I appear to be the only person that runs them on Homecoming, which is a shame. As far as I am concerned, the only legitimate reason to run a zone MSR is the Unabashed badge. The instanced MSR is superior to the zone MSR in every other way. There is much less lag, there is a guaranteed Rikti Drop Ship spawn, everyone in the instance can get Vanguard merits no matter how far away they are from the rest of the team, and everyone has to be level 35+, so if there is a full league you should get more Vanguard merits than a zone MSR. Regardless, since I am the only person that appears to run them, most people are unaware that it exists. So forming an impromptu instanced MSR on the weekends takes a while. While I was in the middle of forming an impromptu instanced MSR in Pocket D this afternoon, someone started advertising a zone MSR on the LFG channel. I sent the person a tell, explaining that I've already been forming a MSR in Pocket D. He sent me a tell back saying that MSRs are formed in the RWZ, not Pocket D. After I sent him that tell, he started spamming the LFG channel with his zone MSR advertisements once per minute, effectively trying to drown me out. After several minutes with no new people coming, some people began quitting and went over to the RWZ. I had to call the raid. I've since sent the person leading the zone MSR tells, trying to explain that there is, in fact, an instanced MSR. He sent me a reply back, stating again that I was forming the MSR in "the wrong zone." So, as a public service announcement: You can, indeed, form Rikti mothership raids in other zones outside of the RWZ. It is also in many ways superior to the zone MSR.
  10. Yep. I've done a Lord Recluse Strike Force with no enhancements, no inspirations, players debuffed, and enemies buffed. This was on a Sonic Resonance Corruptor mind you. My endurance was pretty much non-existent. :D
  11. I don't think it'll work. First off, you're attempting to take away choices from people that like to run level 50 TFs at +0, (like many speed runners that I know). Secondly, even at +3 or +4, you still don't need much teamwork nor coordination like I said.
  12. Team leaders can already set difficulty at those levels, and beyond. I run TFs and trials below level 30 at +1x8 (even Positron and Synapse), below level 50 at +2x8, and usually run level 50 TFs and trials at +3x8. Even at those difficulty levels, you still don't need much teamwork nor coordination.
  13. I'm pretty sure that everyone wants to secretly be a Mastermind and imagine other players as their pets.
  14. I was badge hunting in Echo: Atlas Park when I noticed Ms. Liberty front and center. If Ms. Liberty is still in the Atlas Park echo, why not put Back Alley Brawler back in the Galaxy City echo? The Galaxy City echo feels empty without boomin' BABs.
×
×
  • Create New...