When you get the x settlement is being attacked misc quest you show up, one settler goes hostile and has a synth component on them and the attack never happens.

Ahh this Bug, ok sry.

Oh really. PA has good stats. That's about it, as others have pointed out well stroked regular armor can be as strong.

VATS you push a button and tell the game what to hit. There is no comparison, except perhaps for those threatened by their own inadequacy. It's a built in cheat.

When Bethesda patches the game for DLC everyone gets the patch not just DLC purchasers.

Bugs you say? Good good sheogorath has done his work here. Now we wait for beth and there boring sane fixes.....more like braking patches

Did you actually say endgame? There is no endgame in the fallout series lol....This isn't Borderlands or any other FPS with a boring system with artificial difficulty levels just to slam your hear against. And running the same garbage over and over...

We can talk about cletches or a briken sidequest out of 500 ok...but if major perks and skills do t work because someone put 2000% in instead of 20 and the such - sorry but this is inacceptible for such a project...such obvious fails wouldnt be accepted anywhere else or could you deliver such results at work? There seems to be absolutly 000000 quality control at bethesda or how are such obvious bugs explainable? Its just lazy and disrespectful.

endgame is when you have top tier gear and perks. PA is good until you have legendary items then it's a hinderense.

I use PA thematically. If a settlement calls for the Minutemen, it's cool to show up in shiny mechanized clothes with MM logo on the chest.

Every time I read about this, I wonder: what have users actually done to document this "bug." I've seen some on here say "it is just a typo."

I have no idea, so I regard it as white noise. Having a strong opinion about something you really do not have solid empirical proof about is not my style. Developers and QA people are likely to share that style if they are professionals.

Do you have any idea what the typical process is for fixing a bug?

Let me give you an unstructured hop through.

1. The User (that is us, btw) encounters an anomaly and submits a ticket.

2. That ticket is given a severity level, compared to other tickets pertaining to the same anomaly, and given a priority. Basically, the more reports on the anomaly they have, the higher the priority, the more severe the problem is, the higher the priority.

3. The ticket (along with others pertaining to the anomaly) is sent to testers to reproduce. That is to say, they try to get the bug to manifest itself on THEIR hardware. Once they do, they send the ticket to the appropriate developer, with the documentation to recreate the bug.

4. Once the bug is corrected by the Developer, the fix, the documentation to recreate the bug, and documentation on how the bug was fixed are sent to QA. QA will test the bug fix and if they are satisfied the fix is scheduled for the next patch if code lock has not occurred or the patch after that if code lock has occurred. It should be noted that QA's testing can anything between very simple to full blown regression testing depending on the nature of the bug and the nature of the fix.

We aren't done yet.

5. After QA, the fix is sent to those fine people that actually create the patch files. Once code lock occurs, they send the whole patch file back to QA for final testings and start building the next patch file with bug fixes that came in after code lock.

6. This round of QA testing is primarily designed to make sure that applying the patch file won't break the game, and checks are done to make sure that the bug fixes are actually in the patch file. The testing on the bug fixes is no where near as rigorous as the initial testing, and is mostly just to verify a fix's presence.

Some commentary on the above:

The "fix" for the Headshot Perk is simple, true enough. And it affects everyone who gains the Perk (at least, I know it affects me when I bother to raise MacCready's affinity). But its severity level is likely to be very low and its priority is likely to be at or near the bottom. Depending on the number of bugs reported and how low of a priority the Headshot Perk, it may not ever get to the top of the pile to be fixed. That does not mean a low priority bug can't get fixed. There is a process sometimes referred to as Slipstreaming.

Slipstreaming occurs when a higher priority bug is being worked on and someone notices that the section of code, data table, whatever that is being worked on is the same that needs to be modified for the "simple to fix" low priority bug. If permission is requested and granted to roll both bug fixes into the same code change. then the low priority bug will be fixed along with the higher priority bug. This is not unusual, it happens all the time, but the requirement is there that it be done in conjunction with a higher priority bug.

There is another way that a low priory bug fix can occur. There is a process that is quite often called Cowboying it. This is when someone takes a ticket out of order, makes the changes without authorization and hides the fix in another fix. The important thing to note about doing this, is that it is never submitted to QA for testing. It can't be without the Developer running the risk of being required to explain why they are working on a priority 7 bug when they are up to their ass in priority 3 bugs. Untested bug fixes, breed more bugs.

If you encounter an anomaly and do not report it, it isn't officially a bug unless someone else reports it. In other words, if nobody has reported the Headshot bug, it is very likely that it is not even in the bug tracking system. The number of tickets generated on a bug has an effect on the priority of the bug. If ten people submit tickets on the Headshot Perk, and 30 people submit tickets on falling through the world when exiting the door at Med-Tek, which do you think is going to be looked at first? By not submitting a bug report, you are basically telling BGS it isn't all that important.

One final thing. I have encountered the Headshot bug. I have not submitted a ticket on it. Why? Because, I don't use VATS all that often. It has very little impact on my game. I really don't care if it gets fixed or not. Yes, I know that it bothers some people, a lot. But those people also need to understand that not everyone is as upset about it as them. I am no different than the majority of users when it comes to bugs. "If your problem is not my problem, then your problem is less important than mine." Most people might not have actually said or written anything similar to that, but damned near everyone has thought something it at one time or another.

VATS are not perfect, however. Your chance to even hit in VATS depends on Perception, your distance from the enemy, and how the enemy is moving. Plus, there's no reason to judge people based on how they play, using the options the game gives you. You don't use PA or VATS, and that's perfectly fine, but no one is inferior because they choose to use PA or VATS in their playthrough. It would really feel like "cheating" if this was a multiplayer game with everyone fighting each other - then people would complain about it being OP and unfair.

That's just my two cents.

But I LOVE the extra zero's.

Nothing better than one-shotting a Primus or a Matriarch with a headshot using an unmodded 10mm.

Thank you.

This is pretty much the instruction manual that I received from the developers on the other game forums I moderate for, but you said it much more succinctly.

Seriously. Thank you.

But I was under the impression that, if you do not play the game exactly as the person instructing you tells you to do it that you are a loser and do not know how to play the game. After all, THEY are the only ones that matter. Their issues are the only ones that are important and the rest of the folks that do not play EXACTLY as they tell us it should be played need to "Git Gud" and get with the program or put the game down and never return because we are an embarrassment to all gamers.

Am I wrong?

Haha, you are making me think of the frustration I felt when me and my brother would play World of Warcraft, and my brother would constantly tell me I was playing a class "wrong". XD

Just playing WoW means you were doing it wrong. EQ is the only right way.

So did anybody report those, crushingly important bugs yet? Or are we just having fun?

Send me a list and all the backup and I'll be happy to send them in for y'all. It might take a while though 'cause all that backup is bound to be huge! That and, apparently there are a stack of bugs to reach the stratosphere.

Have some cheese. Well said.

The main one that frustrates me: every time I click my left mouse button I hear this loud crack noise and Cait (who is standing in front of me) spouts a little red paint spout and shouts "Hey! Whattaya doin'!?"

Left Mouse is the "kiss and/or embrace button" isn't it?

Cool story, yes none of the aforementioned bugs are gamebreaking by definition, yes other more important issues take priority. However they do affect the gameplay of a significant amount of players namely everyone that uses melee and VATS as their primary way of fighting. All of what you said would be indeed relevant if the fix consumed a significant amount of time. If you're telling me the entire patch gets derailed by 1 programmer spending less than 10 minutes to change some values in the .esm then all the more reason to doubt Beth's work process.

You are free to disagree with me all you want.

No, I am not saying that the entire patch would get derailed just because one programmer goes rogue for 10 minutes.

I am saying that if the programmer, does make an unauthorized fix, that fix will not be tested and becomes a potential source of new bugs.

And before anyone says that the "fix" too simple to screw up, if the fix is that simple, then the original entry would be that simple. This means that the bug does not exist and everyone that is claiming they are experiencing it is just suffering from a shared hallucination.

{Edit}

You also have to consider, that in a bug tracking system. If a bug is fixed but not tested, it will remain in the system waiting for someone to be assigned to fix it. If anyone does get assigned, the first thing they are going to do is try to watch it in operation. If the bug is fixed, they will never get the bug to manifest itself. So the developer is looking at a bug report saying it is broken, he/she can't see how it is broken and they can spend hours trying to find out how it is broken. So this 10 minute fix of yours turns into an hour and 10 minutes, or more. That is time that COULD have been spent dealing with another bug that needs fixing, but instead is being spent chasing a bug that no longer exists.

No it's a fairly accurate description of what happens. Your 'cool story bro' is just rude.

Fix is that simple though, proven by the people in nexus who actually fixed it. There was even a thread here in GD a while ago about someone who looked in the .esm and found all kinds of values being mistaken/not even assigned at all, for instance: higher ranking deathclaws having less hp than lower ranking ones iirc among other stuff. So yeah, my points stand.

It is fairly accurate and generally correct like I myself acknowledged in the rest of the post that you failed to quote, however it doesn't apply to this case for the reasons I have stated. Also for me being rude: tough.