Level Shift Mapserver Crash/Reward Rollback Issue

Hi everyone, we are aware that some users are experiencing issues losing connection to the mapserver and/or losing their rewards after completing the Strike Target when a team member has a Rare Alpha boost, or when crafting the Rare on the mission map. We are currently investigating the issue, and we will keep you updated. For the time being, it is recommended that you unslot any Rares, and do not attempt to craft or slot a Rare while running the Strike Target.

Thank you all for your paience while we endeavour to resolve this issue.

This is not just limited to the Weekly Strike Target - see my post here.

I'd recommend not using a Rare Alpha slot at all inside of an instanced mission while Paragon Studios look into the issue.

Maybe it wasn't such a good idea to rush this out.. you know.. ?

Obviously the only people that were actually testing it on training room were less than a handful, and even then.. the Strike Target wasn't active. You really should have waited at least a week after this made it to test before rushing it to live.

I suggest you folks not plan so many overlapping events to avoid something like this again.

What a joke.

Thank you QA.

I had the Spiritual Partial Radial Revamp (tier 3 Spiritual) slotted and I got mapserved while trying to kill Eochai in Croatoa...

I'm curious as to what ATs are having this problem. A friend and I were discussing this over a global channel and the blasters have had no problems.

Hardly enough evidence to support any kind of conclusion, but I don't get to see the code, so conjecture is all I have. : )

I completed a LRSF after slotting my rare on my scrapper; no mapserving occured.

Running Cardiac Partial Core Revamp.

Ran many missions this morning (instanced, indoors, outdoors, etc), no mapserv. Ran an ITF an hour ago, me and an MM had rare (he had a Nerve one), resulted in epic team mapserve. Removed rares, did okay on mission 1. Mission 2, I put the rare back on with no mapserve for the rest of the TF.

I'm using a Crab with all 3 spider pets. Was thinking perhaps it may be related to some sort of player/pet level shift issue. Not sure.

I personally haven't had any issues with this aside from the ITF with that other MM. I'm always wondering if perhaps this is character specific or specific to a certain Rare(s).

In summary, "The problem is not me so don't ask me to remove my rare!"

Part of the problem here is NCSoft's policy that puts a blackout period on non-critical patches during and before scheduled events; the devs had to either release it now, or wait until after Spring Fling was over. At least this way, they get the feature out, and are permitted to do a hotfix to solve it.

Yeah, that's retarded, but the devs don't have control over this. That's from their overlords.

Quote:

Originally Posted by Arcanaville Softcapping an Invuln is fantastic. Softcapping a Willpower is amazing. Softcapping SR is kissing your sister.

Running STF on my blaster on Pinnacle Server Tuesday afternoon. Team had only 1 character with the level shift slotted - a Shields/Electric Tank. We got epic mapserved in the final mission just after taking down the third tower. After reforming a new team (I'm not sure if anyone was level shifted on that one) we got team mapserved 3 in the second mission - including once where upon logging in, two team members logged back in into the mission (not PI where the rest of us got dumped) but they were no longer part of the task force. Whatever this issue is, it is *bad* and made the TF unplayable.

And...

Quote:

Originally Posted by Mystic_Fortune Maybe it wasn't such a good idea to rush this out.. you know.. ? Obviously the only people that were actually testing it on training room were less than a handful, and even then.. the Strike Target wasn't active. You really should have waited at least a week after this made it to test before rushing it to live.

This.

This patch was on test for less than a week. According to the patch notes, all it contained was the Strike Target and the Rare/Very rare incarnate levels. However, since no Strike Target was ever announced, there was no way anyone could have tested any of it, Double XP or not.

This patch was rushed to live with inadequate testing. Period. Personally, I suspect that marketing is responsible for this, not the Devs, but I have no proof one way or the other to back up this conjecture. Regardless, it is completely unacceptable.

I'm a 78 month vet and have been here since almost the beginning. Speaking personally, and this is the first time I've felt this way, I feel let down by the folks who make this game. We can all argue about whether or not nerfs or changes are justified, but in the end they come down to game balance decisions.

But this problem is not due to a balance or design decision, this is just plain bad management decision making. The shame of it is that, I was so disgusted with the STF crashes, I took a friend of mine up on his offer of a trial code to join him in some other superhero MMO for a few hours - which I'm sure is exactly the opposite reaction that whomever is responsible for the decision to push this live untested was hoping for.

I was on 3 STFs last night, pretty much back to back to back.

STF #1 - I was hosting. There was one level 50+1 on the team (I think it was only one) and we had no issues aside from a little lag. We had one disconnect but the person returned shortly.

STF #2 - I was a member and was now level 50+1. No issues aside from a little lag.

STF #3 - See above.

For what it's worth, I had the Nerve Core Partial Revamp slotted and I was using my Fire / Kinetics Controller.

Sadly, no Hamidons were spawned due to dancing yesterday evening

[ @Zombie Fryer ][ @Zombie Smasher ]
| Home Server: Virtue |

Twitter: @ZFLikesNachos Save City of Heroes (Titan Network) [Successful "The Really Hard Way" runs: 4] [Click ^]

Dear Devs,

I just wanted to throw in that while this bug may be quite annoying, I still really appreciate you guys getting us new content as quickly as possible. I'm sure that things can be done in the future to keep large bugs like this from discouraging players, but don't let the complaints blind you all to the fact that we were all really really excited to see i19.5 go live yesterday, and more people had a ton of fun without issue than got mapservered.

~Masked Secretary of Champion Server

Currently running a Cardiac Partial Revamp, and no issues on a Dark/Dark Brute. Ever. Have run about 25 missions since slotting it, including an ITF.

Thank you, Devs, for all your hard work. I really appreciate it, and I know many others who do as well. I also understand that your crystal ball may be dusty, making it difficult for you to see into the future and anticipate every single problem that could possibly occur.

I heard about this problem before I ever ran one of my level shifted characters through a TF, but I did craft the rare ON the map for just about every character, and often slotted it on the map. There was never a crash involved.

Read my stories!

While I appriciate that this was put out before the Spring Fling event, and I appriciate the extended winter event, and I greatly appriciate DXP this past weekend, I do not enjoy the fact this was pushed to test during said DXP weekend. I was JUST about to move over there and start testing it on Tuesday only to find that it went LIVE (!!) I told my friends "This is probably gonna be a huge mistake, there's no way they had time to test this." And that's exactly what it was. I would highly suggest not doing that again in the future. Thanks.

Yeah it's not really the devs fault that this was rushed out. Methinks marketing or the NCSoft Overlords might have something to do with it.