Ironblade

My cousin was visiting a vintage clothing store in London and asked about the 'plaid pants' in the window. The salesperson had no idea what she was talking about and asked her to point it out; "Ah! The tartan trousers!"
In the UK, they had no idea what "plaid" meant and pants = underwear.

What kind of endgame do I want?
umm...... content? Really, anything is fine. I was never concerned about the lack of endgame content. I play at all levels all the time. My main character is built for exemping and has exemped as low as level 1.

So, from where I'm sitting: "We're getting new stuff? Cool."

'Semi frankenslot'

Frankenslotting is when you use IO pieces from various (cheap) sets to get the best performance from the power at a bargain rate, ignoring the existence of set bonuses.

In the sets that offer +recovery bonuses, it's always the first bonus. I have a defender (from before Inherent Fitness) who did not have the Fitness pool and had +34% recovery from sets (no unique IO's). If a power needed 4 slots, I put 2 from one set and 2 from another, to get 2 recovery bonuses in that power. He has a couple of powers 6-slotted with pairs from 3 different sets. (He also has a few powers with 5 pieces from the same set because I wanted the bonuses.)

Getting your recovery this way is *CHEAP*. You can slot the entire character for less than the price of one decent set. In some cases, you can slot the entire character for less than the cost of a single piece from a good set (like the Obliteration quad).

Part of it is the number of enemies using the Shield Defense set. With the ally buff, there are a lot of server side calculations. Whatever portion is caused by this, we're going to have to live with. They can't fix it without ditching the powerset for the Cimerorans.

I got a new version of this issue the other day.
1. Positron TF and the person assembling the team is level 12 so passes the star before we start.
2. Someone has an emergency and quits during the first mission.
3. We do the second mission and it repeats.

I explain the steps that should fix it. Leader and one other person immediately start logging. I wait to see if the leader logging will help.

Here's the good part: when those two people logged in, they were A NEW TEAM. They did not show the rest of us on their team and they did not appear on our team. They DID have the next TF mission ready to go. So, the rest of us re-logged. As we did so, each person dropped off the team stuck on the previous mission and became part of the new team with the correct mission.

Weird, eh? I wonder if this is what was happening all along, but I never saw it because we would usually have the entire team re-log at once.

Or you can have a bind that takes a screenshot with the UI and leaves it turned off when you're done.

bind ctrl+sysrq "screenshotui 1$$screenshot$$screenshotui 0"

Assuming you haven't changed anything else, the PrintScreen button (which is actually called sysrq) will take a shot WITHOUT the UI and Ctrl-SysRq will take a shot WITH the UI.