Wha... Did you not read the OP?
Like, Jesus, do you expect people to personally dictate the forum to you?
intellisense ftwOh. Oh no.
As a programmer, typos like this scare the shit out of me.
I'm not sure you understand how many thousands of warnings you get in a project this size, 99% of which you can safely ignore.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.
Jesus Christ people, what the fuck alreadyWho fuckin programmed this shit? Who needs to be fired? And how did the community figure this shit out before a well budgeted development studio with five years to pour over the code looking for issues? What in the jolly Jiminy fuckin hell is goin on over there?!?
It would be easy to just blame someone for the typo but so many things must have gone wrong first for this to actually ship. Developers must have seen how broken AI was and pretty much no-one wants to ship broken stuff. Usually there are simple practices to avoid these things like actually handling parsed values/raising errors if something crucial is missing, logging things and having some sort of automated test set that can be run after changes and verified to work without errors and so on.Who fuckin programmed this shit? Who needs to be fired? And how did the community figure this shit out before a well budgeted development studio with five years to pour over the code looking for issues? What in the jolly Jiminy fuckin hell is goin on over there?!?
Reminds me of some of the things that I have seen broken in closed game tests or show builds that were massively improved hours or days later. I know that this sometimes occurs with conventions in particular because the latest build at a show is sometimes delivered through the crunch of a "hell week" (as some devs I know call the week before a convention) and they end up fixing it after active show hours (when they have had a moment to breath and stop staring at the code for a week straight).This is the kind of mistake that's made during crunch and will never be caught during crunch.
I've worked QA, it's their job to identify problems, not discover the cause.
But feel free to "WELL ACTUALLY" at people who know development better than you.
jfc gaming side has been a tire fire this summer. If you all want to understand why Price lost patience and blew that dude on twitter up you can see it illustrated perfectly right here.
that's seriously what I'm thinkinghow did the motherfuckers who made this shit, and made the AI, and expected it to run a certain way
how did they just not...follow up and look and say "something isn't right"
They probably followed up on it thoroughly. They just missed it because it wasn't in the code.how did the motherfuckers who made this shit, and made the AI, and expected it to run a certain way
how did they just not...follow up and look and say "something isn't right"
People asking why QA didn't catch this: QA almost 100% certainly caught the effects, there's probably a super high priority bug in the QA database about AI not working. QA doesn't code. They find bugs, they replicate them, they do compliance, they file them away for the programmers to fix.
People asking why IDEs/compilers didn't catch this: it's an external .ini file. Shit's not compiled, it's just a plain text file.
It's just a typo.
They probably followed up on it thoroughly. They just missed it because it wasn't in the code.
The real travesty is that it was made to shipped like that, not that the error happened or didn't get resolved.
The correct value is, yes. There's probably dozens of references to "Tether"s in the game code, it apparently being such an integral part of AI behaviour. But when the game is initialised it runs the .ini file to determine certain values for the engine during this session, and suddenly the game itself isn't setting assigning the "pawn" objects to tethers, but to "teathers" and those don't exactly exist.Layman question here, but if it is on the ini file, isn't, at the same time, somewhere in the code?
This is one of the most unbelievable things I've ever heard of in game development. Absolutely mind-boggling.
Layman question here, but if it is on the ini file, isn't, at the same time, somewhere in the code?
Also, because .inis tend to be local to your machine, it's possible and likely that developers did not have the bug locally.It's a spelling mistake in an external file that goes through no type of error checking. That is super believable. In fact, this is one of the most common types of bugs.
Amp version of the page is a bit messy on desktop. Normal link for those who want it: https://www.pcgamer.com/all-this-ti...pid-ai-may-have-been-caused-by-a-single-typo/For those who were asking for it, PC Gamer put up an article with comparison videos and a firsthand account of their experience with the fix.
Spoiler: They also noticed the improvement.
It's understandable that it could happen in the first place, but not that the typo remained there for half a decade before being noticed. I mean, the devs surely must have noticed at some point that the game footage people were capturing of the game's AI was off compared to what they'd put in the game.It's a spelling mistake in an external file that goes through no type of error checking. That is super believable. In fact, this is one of the most common types of bugs.