Level Stuck during Strike Force
It's not a bug. TF/SFs are level-locked when you start them.
Task Forces
Quote:
I believe it was done to prevent this type of scenario:As of the 10/28/2009 patch, Task Forces that are not Flashback or Architect are level locked at the time the Task Force is created. |
A lvl 50 (or higher than the TF) starts the TF, but DC's at some point through the TF.
The star is given to somebody lower than the maximum lvl of the TF and everybody is EX'd to that lvl for the next mission, despite the foes being higher.
I'm sure there was probably an exploit or other issue this was intended to fix as well, but the point is that it IS intended (for now).
Basically, if you don't want to fight a lvl 25 at lvl 23, then wait until you are lvl 25 or get a lvl 25 on your team to host it for you.
Thanks for the info, annoyingly I have plenty of +25 villains that could have led the SF, but didn't think it would be an issue because 'We'll be only facing +1/+2 after mission one.'
How wrong I was.
@Drakmarth & @Drakmarth2
Avatar by S. Wall
#415877 - An Uncivil War: Preclude - Looking for Feedback
The bug is that sometimes the level lock doesn't work. Just as Drakmarth stated, I've also seen TF's where everyone goes up a level when the leader levels.
Paragon City Search And Rescue
The Mentor Project
Quote:
it was also to prevent the scenario of a group of lvl 35 poeple lking 1 lvl 50 down to 35 then starting an ITF, if the lvl 50 stayed LK'd through the entire sf, then the last mish he could un lk and be a lvl 50 in a lvl 35 mish and easily solo rommy (rommy would be only a lvl 36 if he was spawned before the 50 unlk'd)
It's not a bug. TF/SFs are level-locked when you start them.
Task Forces I believe it was done to prevent this type of scenario: A lvl 50 (or higher than the TF) starts the TF, but DC's at some point through the TF. The star is given to somebody lower than the maximum lvl of the TF and everybody is EX'd to that lvl for the next mission, despite the foes being higher. I'm sure there was probably an exploit or other issue this was intended to fix as well, but the point is that it IS intended (for now). Basically, if you don't want to fight a lvl 25 at lvl 23, then wait until you are lvl 25 or get a lvl 25 on your team to host it for you. |

Going to try and explain this as best as I can, unlike the subject which was just poorly conceived in my head.
I led a Silver Mantis Strike Force last night with a Level 23 brute, not my brightest idea I know as SF enemies are set to maximum level of the SF 0/+1 (in this case L25\26s), but I was close to leveling so thought it wouldn't be a problem for long. How wrong I was.
I got my 24th level and found myself still staring at Orange, Red and Purples. I checked my level in the corner and the number 23 remained. How odd I thought, as I'd done SFs and TFs since SSK was introduced and I was certain that I've never seen this problem crop up before. I mean just this last weekend I was on a team for the first three TFs and I'm sure the team leader leveled and with him the team level rose.
We finished the mission in the end and I collected a new power, I was level 24 indeed, but found the corner was still showing 23 in the corner and confirmed with the other teammates that yes they were still level 23 (cue accusing glares).
From there we managed to pummel our way through the various +2s and +3s and I leveled again to 25 and still no change to the Team level.
This didn't stop us from succeeding in the SF, though it took longer than excepted, much debt was claimed and after I spoke to Mantis the final time the Team Level in the corner jumped to 25. So no permenant problem, but I just find it odd that the level set it self to 23 and remained that way for the rest of the SF despite my leveling twice, surely that can't be intentional.
I'm just glad I wasn't Level 22 or else I may have been found and killed by my teammates.
I tried to do a quick search to see if this had been noted before, but my search-fu during work hours is weak and wiry. I've also sent a Bugged this through the regular channels.
Is it already a well known issue and I'm just crazy? Or has anyone else experienced this recently?
@Drakmarth & @Drakmarth2