1. Keldroc

    Keldroc
    Member

     
  2. Boarderlands 3
     
  3. Jinfash

    Jinfash
    Member

    I need to see comparison videos and an explanation from Gearbox.
     
  4. BernardoOne

    BernardoOne
    Member

    The typo will be on the console versions too.
     
  5. Blade Wolf

    Blade Wolf
    Member

    OH MY GOD
     
  6. Manu

    Manu
    Member

    YES
     
  7. Pasha

    Pasha
    Member

    Man is the AI really controlled by external .ini files? Thats crazy!
    Is this the same case for Borderlands?
     
  8. Kain

    Kain
    Member

    This sounds like the people who wrote the code never even touched the game itself and the testers probably raised all the flags but the publisher didn't care/didn't have budget to fix it.

    What you call a mess.
     
  9. deepFlaw

    deepFlaw
    Member

    Oh. Oh no.

    As a programmer, typos like this scare the shit out of me.
     
  10. LowParry

    LowParry
    Member

    So. I can play it now?
     
  11. Gonna be honest, I skimmed the fuck out of that and saw long strings immediately below the path to the ini and my mind instantly went to file paths.
     
  12. Heid

    Heid
    Member

    The explanation is probably they rushed to launch with a borked build and didn't wanna pay their people for the time it'd take to find a typo.
     
  13. "Whelp I guess we just suck. Oh well, no need to double check everything post launch"
     
  14. Smash Kirby

    Smash Kirby
    Member

    Someone should bring this to the attention of Jim Sterling, it has been a while since he covered Colonial Marines.
     
  15. LAM09

    LAM09
    Member

    That's crazy
     
  16. Fury451

    Fury451
    Member

    5 years later, a single typo is fixed, raising the game from poor to mediocre.

    Pitchford vindicated.

    I bet that typo fix didn't resolve the fanfic story though
     
  17. FyreWulff

    FyreWulff
    Member

    Reminds me of when I accidentally break the fuck out of a build with the ol' accidental = instead of ==
     
  18. op_ivy

    op_ivy
    Member

    absolutely crazy
     
  19. AwakenedCloud

    AwakenedCloud
    Member

    What a shocking Revelaiton!
     
  20. principal

    principal
    Member

    so this works? any proof?
     
  21. Ombra

    Ombra
    Member

    I agree. The hate is silly. who ever mis-wrote that line of code had a brain fart that doomed peoples careers. its more sad than humorous.
     
  22. Twilight Suzuka

    Twilight Suzuka
    Banned Member

    I guess it's good that patch sizes are getting smaller ....
     
  23. Jarmel

    Jarmel
    Member

    In a fucking ini file.

    jesus
     
  24. Dorfdad

    Dorfdad
    Member

    Especially after all the damning AI complaints wouldn’t they fire up a retail copy and say hmm this looks odd and investigate? Simple mistake cost them money I’m sure!!
     
  25. tbyte64

    tbyte64
    Member

    Do people ITT understand that they don’t pay programmers by the letter? It literally doesn’t matter how many letters fixes the bug, what costs money is the several days to investigate the bug, understand the code, rebuild, re-run QA, redeploy, etc.

    Yes it’s still puzzling why Gearbox was penny pinching so hard on this game that they couldn’t fix this bug, but the nature of the bug and how many letters it is is completely irrelevant.
     
  26. data

    data
    Member

    If it did, sad.

    If it didn't, best alien movement displayed in a game for the longest time and it was intentional too :D
     
  27. VariantX

    VariantX
    Member

    Essentially those versions are fucked forever and ever because no one is going to spend money to fix that one letter on a game that has zero sales potential on the platforms they're on which are also dead.
     
  28. Im sure I should be amazed

    or sad.

    Im sadmazed
     
  29. ChrisJSY

    ChrisJSY
    Member

    I don't know what's worse, this or specifically having a test environment to test something, acknowledge what you are testing isn't working and ignore it, pushing it to live and letting it rot for years and doing it hundreds of times.
     
  30. Dusk Golem

    Dusk Golem
    Local Horror Enthusiast Moderator

    The surprising thing isn't a single typo breaking elements of the game, I think anyone who's done any level of coding knows the dread of the infamous, "find the single mistake in my code that's breaking everything," and it being in an external file means it's less likely they'd check there initially to find the mistake.

    But it is very surprising that they must've known the AI wasn't working as intended and shipped it in that state, maybe they figured something broke in development they couldn't fix, but the solution is humorous/ a bit sad. I know with bug fixes you can't fix everything, so you do have to prioritize what to fix, but this seems like such an important part of the game to fix, that them not prioritizing fixing this just seems insane to me.

    It also reminds me of those periods something in a game I'm working on that SHOULD BE WORKING just absolutely isn't, I recheck my code, I feel like I've done everything, only to find there was one simple external mistake I made that fixes everything. Given I don't ship my games in that state, my games aren't nearly as complex as something like Colonial Marines, but I'm also one person and they're a hired team, but yeah.
     
  31. tbyte64

    tbyte64
    Member

    Probably under extreme crunch too, knowing how this game was released, making it even more understandable.
     
  32. molnizzle

    molnizzle
    Member

    Not as fun as spelling!
     
  33. Cess007

    Cess007
    Member

    As a QA myself, it pisses me off when people come and post things like this is QA fault.

    QA doesn't review code, nor .inis and I can assure you there's a bug logged somewhere about the poor AI in a Gearbox database
     
  34. Thats programming, the dudes who created the algorithim were probably in their own box. Someone came to check it out and it did what they wanted. The game was probably put all together at the last minute and the people who developed it were either gone or occupied with other things so it wasn't caught.
     
  35. MikeHattsu

    MikeHattsu
    Member

    AA game
     
  36. panecasio

    panecasio
    Member

    Are there any comparison videos out yet? I'm interested in seeing how this changes things.
     
  37. convo

    convo
    Member

    It is a mundane mistake but a costly one, if they ran out of time to find the mistake it just makes it more tragic not that it would have saved the game completly. 5 years later this is just a funny reminder to check your code for any typos.
     
  38. Dusk Golem

    Dusk Golem
    Local Horror Enthusiast Moderator

    Yup, QA aren't programmers, they're not looking at the code of a game.

    I also know several people in QA, QA finds bugs all the time and report them, but it's up to the actual teams if they choose to fix it or not. Most bugs get a marking from the QA team of how crucial they are to fix, but there's MANY examples of QA telling the teams a bug is a bigger deal, and the leads not prioritizing it to focus on other things instead. It's not feasible for a game team to fix every bug in a game, there's not the time and money for that, but some stuff they neglect they really shouldn't, and often QA DID report it, just the leads didn't prioritize it.
     
  39. Hate

    Hate
    Member

    Is it appropriate to say lazy devs?
     
  40. Dusk Golem

    Dusk Golem
    Local Horror Enthusiast Moderator

    No. That shows a gross misunderstanding of what likely happened here.
     
  41. Venture

    Venture
    Member

    So the consoles are using a .ini file or the equivalent behind the scenes? I could see how someone might just copy and paste parts of it from the PC build without paying any attention to it.
     
  42. data

    data
    Member

    I wouldn't say that.

    Probably had a budget and time constraint and who would expect it wouldn't be a problem with the code but a configuration file.

    Even the modder took 5 years to find this even when the ini was open for all to see.
     
  43. Orb

    Orb
    Member

    I reviewed this game at launch and I’m sorry to say that this is not nearly enough to “fix” it
     
  44. Corporal

    Corporal
    Member

    Sweet ogly mogly. How. Why. That's just hilariously terrible. How fitting that the fix took several MONTHS to propagate outside a tiny modder blog.

    I'm just sad that development must've been so borked that even a (likely) error log or exception upon encountering the parsing error didn't alert the devs to this critical yet easily fixable bug. I know it's tempting to just tune out the various warnings these modern code behemoths barf out by the bucketload, but shouldn't that have been one of the first things to check? And I don't know just how strict their engine script parsing is, but shouldn't this have thrown huge amounts of critical errors in succession for using an object that was either nonexistent or uninitialized? Meaning, the dev in question would have gone through their own changelog with a fine comb, probably with half the team riding his ass for breaking the AI?

    What a mess.
     
  45. Einchy

    Einchy
    Member

    Yeah, I mean, it's a funny story and all but is there any proof that it actually "fixes" the AI issues? I'd love to see a comparison.
     
  46. Fix is a strong word. It might make it a little better but let's not get carried away, the game still has many problems that this doesn't fix and is still a kick in the balls to all Aliens fans.
     
  47. Oh my god, this is legitimately such an unfortunate mistake. Fuuuuuuck
     
  48. juicyb

    juicyb
    Member

    This is incredible
     
  49. Soul Unison

    Soul Unison
    Banned Member

    Wha... Did you not read the OP?
    Like, Jesus, do you expect people to personally dictate the forum to you?
     
  50. Doom_Bringer

    Doom_Bringer
    Member

    intellisense ftw

    funny this happened in a modern IDE environment, but it sounds like bad naming convention.