Missing door to Bukot/Saruman

[Neverwhere616]

Day 8, still no fix announced. Awesome.

[oogabooga227]

Turbine (Celestrata) has acknowledged this (Wednesday, 14 March): "We are aware of this issue and we are looking into it everyone. When I get any more information, I'll let all of you know as soon as I can."

http://forums.lotro.com/showthread.p...47#post6046447

That's the problem with different threads on the same issue

Yeah, but the issue is Turbines history with hot fix patches never happening in what most people consider an expeditious fashion. When the only worthwhile raid breaks, you'd like to believe that a hotfix would be in place within 24-72 hours. I hate trying to compare LotRO to other games, because comparisons are generally unfair, but if this was another unnamed MMO, I'd have a hard time seeing a raid remain unplayable for over a week.

[Azerog]

Yeah, but the issue is Turbines history with hot fix patches never happening in what most people consider an expeditious fashion. When the only worthwhile raid breaks, you'd like to believe that a hotfix would be in place within 24-72 hours. I hate trying to compare LotRO to other games, because comparisons are generally unfair, but if this was another unnamed MMO, I'd have a hard time seeing a raid remain unplayable for over a week.

Since we couldn't get into the shadow last Saturday we ran Helegrod. That place was so broken it got us to wondering if they may have shut down the tower on purpose. There were lines all over the place that the mobs would just not aggro over, and pets would not cross. You would try it and the pets would just desummon. As an example; Giant wing boss fight, the giant adds just stayed at the entrance and the snow beasts never came in and the giant boss keep losing it's target all you did was burn it down. Drake wing, you could walk right past 90% of the mobs and they wouldn't aggro, on the boss none of the mobs would attack you.

If this is occuring in ToO Shadow and Saruman you can imagine how it would trivialize those fights and encourage 1st age farming.

My thought then is that something deeper is broken and they need to fix that before they reopen ToO.

[Neverwhere616]

http://forums.lotro.com/showthread.p...day-March-21st

9 days for a fix to the only raid worth running. Stay classy, Turbine.

[anteku]

Drake wing, you could walk right past 90% of the mobs and they wouldn't aggro, on the boss none of the mobs would attack you.

My thought then is that something deeper is broken and they need to fix that before they reopen ToO.

We did Drake and saw exactly the same thing. I thought they replaced all of the mobs with Draigoch's kinfolk.

You might be right about a something deeper being broken.

[swordmonkey]

http://forums.lotro.com/showthread.p...day-March-21st


Looks like they might be fixing it. Won't know until patch notes come out.

[Mysterion]

Thread was discussing lag follow to read more

We're aware of the issues. In Fact we should have it resolved tomorrow with a small update. We're also taking the opportunity to address some of the Warden issues, and issues in the Isengard raid.

[Sapience]

We have a patch that will be released tomorrow that will address door issue and a couple of other other small issues as well.

[Mysterion]

^^ or just read that

[swordmonkey]

We have a patch that will be released tomorrow that will address door issue and a couple of other other small issues as well.

Cool, at least we'll have a shot at shadow and saruman this lock cycle.

[Yula_the_Mighty]

Seems pretty likely to me that they built U6 on top of the vanilla RoI build.

This situation is a common issue with software. What happens is that you finish a major release like Update 4. Two teams start up (Update 5 and Update 6) using the same base software. Now you get all these forks in the software modules. It is very easy in Clear Case when doing a code merge to destroy changes in the other forks when the module is modded in multiple forks.

Clear Case naturally handles the situations where the mods were only done one fork. It is easy to merge forks when there is no overlap.

Clear Case will not help your software development house with all the unexpected interactions. It will allow you to blow yourself up really easy by clicking the option that says use my version causing other important changes to be removed from the Code Base.

You got the situation where the development, testing and QA department are over loaded. Management says release on time. You get a lot of I only got two minutes. Quick Glance. Looks like I can ignore these 5.2 changes in this module. Testing does not have the resources to verify that all the 5.2 changes are in the Update 6 candidate because they are under the gun to finish testing the Update 6 features.

There is a second source of errors. Every module has to be added to the load definition. If the module was in the Update 4 base load. Modded in Update 5.2. A developer not only has to merge it into the Update 6 line. They have to mark the merged module for inclusion into the build. The load build team as to approve the inclusion.

Where I work that is another problem. I will try and include a variant of a module into the load. We are not taking that module. Too much risk of surprises. But But But. The customers are going to change to Grumby dwarf. Fine. If you are right Yula. The customer will complain. We will look into adding it as an out of cycle fix. I can remember cases we went for years because we could not get the module into the load launch load definition.

You really have to work in software development on live products to understand some of the issues.

Note - As usual - I am basing my comments on my personal experiences. As to the applicability to Turbine, no idea. It always interesting to see "less than successful" live deployments from another company. Describe how Yula and peers managted to make the same kind of botch of it.

[Yma]

We have a patch that will be released tomorrow that will address door issue and a couple of other other small issues as well.

So Sapience, what happened to the door? Now you can tell us... was some bugan burglar? Have you caught the culprit, will there be any justice for us (and for the poor Saruman... just imagine weeks without being able to exit from Orthanc!)?

[ArcaneLore]

As compensation for anyone who has at least one character who has completed at least 4 wings of TO on t1 or better. I suggest 1 free first age weapon per account appropriate to the highest level character in the account if it's VIP. Second age if it's premium. If it's free, at least it did not cost you anything. Maybe 3rd age for f2P. We can always hope.

[timmyloo22546]

As compensation for anyone who has at least one character who has completed at least 4 wings of TO on t1 or better. I suggest 1 free first age weapon per account appropriate to the highest level character in the account if it's VIP. Second age if it's premium. If it's free, at least it did not cost you anything. Maybe 3rd age for f2P. We can always hope.

no thanks. People who would have been running T1 during this broken door issue were never missing out on first ages to begin with.

[YesMaam]

As annoyed as I was as everyone else about the locked door I must say I'm happy its being fixed before the reset, that means I only missed one lock. But UGGGGH lol.