We have detected that cookies are not enabled on your browser. Please enable cookies to ensure the proper experience.
Page 2 of 2 FirstFirst 1 2
Results 26 to 32 of 32
  1. #26
    Join Date
    Oct 2007
    Posts
    649

    Re: 2.5.5 Major Bug - NPCs level 1, one-shotted, instance failed

    Well whatever they decide to do with the instance, I hope they do it soon. I reached
    my 5 instance per hour limit just trying to get a Brogur that was over level 17. So now
    I get the honor of trying to find another 2.5.5 group. This last group took me two days
    to find At least my instance timer will be reset by then!
    "People keep comparing Lemmy to God... He's cool and all but he's no Lemmy." - Unknown

  2. #27
    Join Date
    May 2007
    Posts
    1,020

    Re: 2.5.5 Major Bug - NPCs level 1, one-shotted, instance failed

    Past history suggests we'll see a hotfix sometime in the next 2 weeks to fix the biggest issues--some known, and probably an exploit fix or two. Then, again based on the past history, I'd expect patch1 sometime in early January.
    Various Hobbits, Thwilda the dwarf lass, and Gnersk, Stalker

  3. #28
    Join Date
    Jan 2007
    Posts
    4,382

    Re: 2.5.5 Major Bug - NPCs level 1, one-shotted, instance failed

    This is not something they can let go for 2 months (like some other things). I would say they will fix it 'Soon' er rather than later.
    Kinships: Fifth Star Vagabonds on Crickhollow (Dotswith); Random Access on Arkenstone (Dottiel)

  4. #29
    Join Date
    Sep 2010
    Posts
    68

    Re: 2.5.5 Major Bug - NPCs level 1, one-shotted, instance failed

    Be careful of bug fixes that make new problems. I recall one patch in another game's attempt to fix some game breaking bug. And it did something no one expected. It removed the entrance/exit door to a public area.

    *giggles at the thought of everyone in the Bree craft hall being trapped there due to the door vanishing*

  5. #30
    Join Date
    Oct 2007
    Posts
    256

    Re: 2.5.5 Major Bug - NPCs level 1, one-shotted, instance failed

    given how many people are now stuck in getting a legendary trait, I think much sooner hot fix rather than later is in order.
    [charsig=http://lotrosigs.level3.turbine.com/0e215000000003e46/01006/signature.png]undefined[/charsig]

  6. #31
    Join Date
    Sep 2007
    Posts
    895

    Re: 2.5.5 Major Bug - NPCs level 1, one-shotted, instance failed

    Quote Originally Posted by Shukar View Post
    Y'know, when I interview folks for programming jobs at my company, I look for people who think like this. So we can AVOID hiring them.
    Anyone with common sense wouldn't say this at an interview.
    [color=#9A32CD]Third Marshal Adrina the Battlemaster Rank 12 Rune-keeper[/color]
    [color=#1E90FF]Emedyl R7 Captain, Ritah R7 Burg, Harwyn R7 LM, Camacho R6 Captain[/color]
    [color=#FF3030]Deeman R5 Guard, Kemli R5 Champ, Bigcheese R5 Mini
    Morderon R4 Champ, Cronks R4 Warden, Deaman R4 Hunter[/color]
    [color=#FF7F24]Murauz R7 BA, Dreykahn, R7 Reaver, Morzug R7 Warg, Renamedske R5 Spider[/color]

  7. #32
    Join Date
    Dec 2008
    Posts
    618

    Re: 2.5.5 Major Bug - NPCs level 1, one-shotted, instance failed

    Quote Originally Posted by Shukar View Post
    Y'know, when I interview folks for programming jobs at my company, I look for people who think like this. So we can AVOID hiring them.
    I'm not sure if you noted that I was being tongue-in-cheek or are agreeing with me.

    I'm a senior engineer who writes software that is used in the storage back-ends for high availability transactional systems (we have several stock exchanges, several credit card processing companies, and few other odd-balls such a 9-1-1 system as customers) so i certainly know about statements like that. I also know how hard it is to find programmers that do too.

    For instance in our business *every* place an error can occur we have to check. We have had to let more than one person go because they are happy to let errors accumulate if the they think they will just not do anything bad and there is a great deal of source I have to patch because of this too (we run linux on our devices). For instance it is common to not check a return value of memory copy operation and catch the error later on when you examine that memories value - can't do that as we enter an "undefined" state and have to quit. We also have all sorts of rules about how verifies on writes with caching work - it gets fairly complex and you really have to think about how things can fail. Frankly I look more for people who know how to break things (note this is subtly different than break things - I mean look at a system, say I'm going to do this and it is going to fail this way, and then have it happen), if they can do that chances are they are great at fixing them too. Too many know how to do things when everything works right and get that attitude of "It's just five lines".

    One of my questions is to ask them if they would feel comfortable if their mother (or their child if they have one) just got shot in a robbery and their phone call to 9-1-1 occurred in that moment of time between the error occurring and the 10 statements later where you catch it. A good programmer that has never had to work in that type of environment quiets down, thinks for a moment, and answer "No, I wouldn't". Reality is that our solutions *do* work in some 9-1-1 call centers and that is a real situation. It still surprises me the number that say they would feel just fine as it doesn't matter, nothing bad can happen.

    Of course the game world isn't mission critical and can't be run that way, however it still amazes me how little tiny changes can escalate so far. Even in high school I knew better than "Its just five lines of code", although I will say in a previous life I wrote a great deal in PERL and note that five lines of code can be a significant program in some environments
    [charsig=http://lotrosigs.level3.turbine.com/032020000001e7a02/01003/signature.png]Brianwald[/charsig]

 

 
Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

This form's session has expired. You need to reload the page.

Reload