By this, I don't mean the ranked statistics which were reset at the start of Ranked Season 1, but the games-won count for regular warzones. The ones that we've been building up since 1.2, or whenever you enabled tracking. Player Kills, Medals Earned, and MVP Votes Received are still there, but Total Wins stands at 0 (or however many you've won since the last patch). Not that anyone will ever see this short of us posting screenshots in the forums, but that's a bit annoying to have statistics we've been building up for close to two years wiped clean all of a sudden. I hope that these can be restored at some point.

I've done SM FE a few more times since I last posted in this thread, and have had no problems getting my achievement counter to go up for Jindo Krey. I always kill it the same way, just ignoring the ship, so I never get the immunity shield/self damage issue. I think the general hypothesis given by folks here is correct in that if the player is not giving the killing blow, then they are not credited with the achievement, seeing as we've had trouble with Revan, the Quesh WB, the Rakghoul Behemoth, and now this.

So, the real question is whether or not the mainstat relic is actually BIS if it's ever "fixed" to only proc every 40 seconds?

Yeah, clarification on what this means, please? Obviously double SA is going away again, but don't tell me you're reverting to your original stance that regarding these relics where two proc relics (say, the SA/DV combo or Shield/Redoubt) lock one another out for the duration of their activation? Or does it mean that they can activate within, say two seconds of one another, but just not at the exact same time? Or does this mean that one SA relic will no longer proc twice when doing damage and healing within the 20 second window? Or something else entirely? The patch notes on relic changes tend not to be too descriptive, but they make a big difference on whether or not we all need to grind new relics.

I, on the other hand, haven't had a problem with earning achievements for this flashpoint. I've completed SM a few times over the last two months and just finished HM, all of which gave me the achievements for Jindo Krey. There are two things that I can think of: 1) In my case, I soloed both SM and HM, entering manually from Ilum and not using Group Finder, which could be a possibility. Were both of you using GF to run the flashpoint? My HM counter for Krey has one less than the other bosses and this may be because I ran HM through GF once recently, because I'm pretty sure it updated properly when I soloed it for the first time post 2.0. 2) Jindo Krey's support ship, at some point before 2.0, was bugged where the ship did way more damage than it should have. I usually down Krey before the turrent destroys the ship (since I'm the only one clicking and it's faster to attack Krey while the ship is shooting missiles at me, as he doesn't go immune, at least until the damage gets too high). Are you killing Krey or the ship first?

I haven't updated myself in a while and now have 23685 achievement points and 9 reputation legends. Also a reminder, if not made obvious by the flurry of rep posts above, that today is the earliest that you can get Legend for a new reputation faction (Strike Team Oricon/Dread Executioners). (I'll update achievement points when Photobucket isn't undergoing maintenance and I can see everyone's percentages.)

The first question has been long since put to rest via an official post. Legacy of Crafting does increase your chances of getting an extra item on non-augmentable items. See here: http://www.swtor.com/community/showthread.php?t=492276&page=2 And the other two seem to work how the poster above me replied. I'm not sure what debates you're citing here.

Mugennana (3/36/7) Telekinetics 3022

Fixed, thanks. 2.4.2 only has a few relevant bug fixes, including: I don't know if the first fix will help and operations boss achievements that folks have been having issues attaining or not, though hopefully it does. Note that the second fix does not yet make Beastmaster available, as they are still working on fixing the othe two bugged Ilum achievements.

I can't get your screenshot to come up for me (tried it in a few browsers). Mind re-linking this using a different photo-upload service?

Hmm, my EV still stands at 100%, so not sure what's going on there. They had supposedly fixed all of the achievements for EC, though I guess not. I haven't ever run 16m HM/NiM for EC, so I can't verify if those ever worked or not (since they're ridiculously hard to find a good group for, unless you have a huge guild). And unfortunately, while it seems that at one point CS did grant bugged achievements, most reports indicate that they no longer do so.

Or make it so that you can just spend only one point while in the queue. Agreed that this is annoying while leveling alts. I'm so used to doing it that I totally forget that I can't spend that point until I'm a minute or two into the queue, and then have to get out just to spend the one point.

Some nice updates coming in 2.4.1 regarding achievements, which make two titles (Loremaster and Gearhead) and a number of multi-step long term achievements available. Relevant notes are as follows: The following seems to provide hints as to where to find two of the three new lore entries (I don't know about the Taris one). If you do happen to run across these lore objects, your fellow achievement hunters would be much obliged if you posted coordinates. That's it for these notes. Looks like I'm going to have to start pugging EC NiM again, as the speeder from Kephess is literally the only one that I don't have. Ugh...

Mugenni - 2527 (Pyro 4/6/36) http://www.torparse.com/a/452727/time/1381359615/1381359915/0/Overview 4 piece PvP set bonus, mostly 66 enhancements, 72 mods, otherwise 69s around besides the offhand Mugennana - 2885 (Balance 5/5/36) http://www.torparse.com/a/454185/time/1381477102/1381477435/0/Damage+Dealt 3 78s, 2 75s, otherwise 72/69s Neither of these parses have them, though what's the official position on parses with double SA relics?

The editing/character limit issue on the forums has now been fixed, so everything should be up to date.

It also doesn't help that I can't see the NPC for a few seconds after I zone in. I unfortunately have an older computer (yes, I wish I could upgrade) and it take the NPC a second or two to render, by which time its health has already dropped a lot (yes, cast your AOE, but that only helps so much until I can actually click on the NPC to do some healing). The same thing happens in the Raptus fight--I get stuck at the splash screen for too long and one of the first times I did it I saw my UI flash up for a second before I got killed by Raptus in the present without any time to hit my bubble or anything, since my healer agro on 16m with a sage overpowered everyone else's. Of course, I dropped agro before coming out of the transition after that, though then a DPS who had the highest agro about got splatted thereafter, since the tank was either just too slow in reacting, or also had a slower computer. These sorts of area transitions in the middle of ops fights are rather annoying for those of us with slower machines. The transition during the Styrack fight (after killing your companion) with the slow-rendering giant apparition was never as bad since I could either just start casting AOEs as a DPS, or not really worry much as a healer (since no one should be taking damage at that point), and that the damage requirement, beyond a really bad and undergeared group (or once in a while when S&V was fresh) wasn't that taxing.

Noting the problem in this forum for better visibility. Original thread is in the Customer Service forum here. In short there is a bug preventing anyone from editing a post that (we think) has too many characters, or even sending a long private message. This has occurred for myself and 6 other users. This returns an error message every time, and unlike the previous "Site traffic too high, try again later message" that was returned when you tried to edit something the last few weeks, posts are no longer updated at all. This affects most of the leaderboards out there, fan fiction threads, private messages, and perhaps folks trying to make longer posts generally. The error reports look something like: Thanks for your attention to this matter.

Would love to update the leaderboard, though for some reason I get an error message when I try to update the OP (tried with two different browsers, other posts in this thread can be edited normally), so stay tuned... UPDATE: Looks like it's not just my problem, but that they did break something with regards to editing or sending large messages. See here. Don't let that stop anyone from updating until it gets fixed, though. I have a word document that I will be updating in the meantime to post when the problem is fixed.

You realized there's a thread three under yours that addresses the same issue, right? It's probably bugged. The easy answer is to take one of your heal-to-full-capable DPS and have them go into the healing challenge with your healers (your DPS will still probably be fine). The challenge also starts when the first person enters, so make sure your folks on green all enter at the same time. Either way, even with failing the healing challenges, you can still get the boss down on SM.

Bump back to the main page and an update for me, now up to 22,280. Everything should be updated and reorganized.

I haven't done it on HM (progression starts tonight), but I have done it on 8m SM and it hits ridiculously hard if you're not prepared for it and don't have fairly top-tier healers (i.e., will stop most pugs in their tracks). We had to remove one healer from our raid and I had to take over, though I now realize they probably weren't doing that bad. I took my last 3 logs where I got it each time, looking at the Damage Taken tab on TORparse, which yielded the following information for my Sage: (Not sure why the 5k ticks in the last log, but that's still pretty damn hard.) This is uncleansable by anything besides my god bubble and just requires much better gear/coordination than a SM ought to. By comparison, Mass Affliction from the Corruptors, which is cleansable, hit for a paltry 798 internal - 1141 internal according to my logs. Here's a link to my log if you want to see for yourself (it's listed as Affliction NOT Mass Affliction near the bottom of most logs on damage received).

I’ve only ever had this bug happen to me in ops since about 2.3, though I can’t say I’m 100% sure that it’s merely confined to them. This has occurred twice, once in S&V 16m SM and once in Dread Fortress 16m SM, and it also happened to another member of the party during the course of DF. The first time it happened was on Styrack when I got sucked into the nightmare to fight my companion. Once he was dead, I exited the area only to find myself stuck running forward. Fortunately, I was on a Juggernaut, so I could still contribute some DPS, though I either had to hold my back key down to not move (and therefore not attack) or run in circles while I attacked (avoiding the box of death while the large apparition was out, etc). This persisted for a good 2.5 minutes before it was somehow cancelled. The second time was yesterday on my Sage, when after wiping on the 2nd boss of Dread Fortress, I entered the quick travel portal, only to have my character immediately begin to run forward without my being able to stop the motion. I had to log out (and get then re-invited) to the group before the effect went away. A second person in the two had the exact same problem two pulls before, otherwise I would think that it was my own hardware. I tried toggling my auto-run keybind, hitting the other direction keys, jumping, typing “/stuck,” getting pulled by a friendly sage to no avail. Either logging out or something unknown to me stopped my character from running. The only common factors in my limited sample size seem to be 16m SM ops, everything else (faction, class, race, body type were different, though both were female characters).

Ditto here as well and I have also dumped my cache. Rather annoying when I'm proofing a post or update and need to edit multiple times (since that's never been a strong point of my writing).

Updates for 2.4 look like the following: -Locations points changed from 13335 to 12265, for 1070 less points with the removal of Black Hole and Section X lists. -There is a brand new Dailies tab with 2180 points available. This includes Black Hole (formerly part of Planetary: Corellia), Section X (formerly part of Planetary: Belsavis), CZ-198, and the new Oricon daily area -Operations increased from 3740 to 4140 for an additional 400 points with the two new operations. Currently there are only achievements for 8m/16m SM and HM listed. -Total points from all achievements are now capped at 33,525 (barring those that are currently unavailable due to bugs) -New reputation factions to max out to legend: Strike Team Oricon (Republic) (Republic)/.Dread Executioners (Imperial) I’ll have to wait for folks to update their scores so I can figure out how the Planetary standings look now. Mine increased about 5% with the removal of the dailies items, since I hadn’t done very many of those. Since I have no way to tell who did or didn’t do those before-hand, I’ll have asterisks placed on Planetary scores that haven’t been updated recently, pending temporary removal if not updated again within a few weeks. Bioware reorganized the achievements tabs again, so I’ll reformat my tab rankings to reflect the new order, so the leaderboard is easier to follow. Additionally, I’ll convert the current Operations rankings by hand (+/- 1%, since I don’t know exactly how many points you all have). This reformatting/recalculating will be up within a few days. Not sure why there weren’t any new PvP achievements added, though perhaps in the future. I do wish Bioware would stop adding achievements after-the-fact (see CZ-198) when we’ve all already ground out certain areas more than we would already like. No other large relevant bug fixes besides fixing the Elysium Thranta on Alderaan, which will give access to a H4 and a good mob farming spot.

Here's the that worked for me on Balmorra (don't have to go in an instance). It involves some platforming and a companion.