Random Thoughts – Randocity!

Fallout 76: Where to find Deathclaw Hide

Posted in botch, business, video game design by commorancy on February 6, 2020

NukaColaPA-fIf you’re trying to complete the Possum challenge for Leatherworker, you’re probably looking for Deathclaw Hide. Let’s explore.

Possum Challenges

The one thing about the Possum Challenges is that there’s always this “one thing” you can’t seem to find (or do). With the Leatherworker challenge, this one is no different. I have no idea why Bethesda feels the need to make these challenges drastically more difficult by limiting the ability to find the things you need. For example, the Possum Electrician challenge is entirely broken. There’s no way to actually succeed with this challenge because the ‘Restore power to a Power Plant’ challenge won’t complete no matter how many times you “Light Up” the Poseidon Power Plant.

Fallout 76_20200206065538

With pretty much every other animal in the game, you can find their hide on them when you kill them. Perhaps not all of the time, but at least 50% of the time. This would mean you need to kill a minimum two of these animals to find its hide.

With the Deathclaw, unfortunately, Bethesda took Deathclaw Hide off of a Deathclaw’s drop list which you only find out after spending time and ammo to kill several Deathclaws. So, no longer does a Deathclaw drop Deathclaw Hide. This makes the Leatherworker Possum challenge nearly impossible… until you know where to look.

Fallout 76_20200206065455

Thanks, Bethesda.

Rant Mode On

At this point, I can’t believe this is an oversight. In fact, I believe that it isn’t. I believe these changes are intentional by people within Bethesda. To consider this unnecessary change as anything more than accidental in among so many other “accidental” changes is naïve. There is absolutely no way Bethesda is this mistake prone. No way! No company makes so many mistakes in writing code. No one does this. One or two mistakes here and there I can accept as accidental. With Fallout 76, it’s been a series of mistakes after a series of mistakes after even more mistakes.

In fact, it’s almost like Fallout 76 came to exist through a series of mistakes. No one (let alone a company as big as Bethesda) makes that many “accidental” mistakes and still produces a semi-functional product. No! These changes are not accidental, incidental or unintentional. No company operates like The Keystone Cops (too young for this reference?   ⃪ click here).

These mistakes are definitely intentional! They have been introduced by Bethesda’s engineers intentionally. Why? I don’t know. Perhaps job security? No company I’ve seen introduces bugs intentionally… except Bethesda and software engineers hoping for …

Job Security

What exactly is “Job Security” in the software and technical professions? I’ll explain.

Many technical staff are not confident in their own skills or abilities. Their job insecurity sees them play games to make themselves appear “more valuable” and, thus, help their prospects with job security. Everyone wants to be considered a valuable team member. Unfortunately, playing this “job security” game in the way described below is highly unethical, but few technical staff see it this way.

By Technical Staff, I’m referring to software engineers, software designers and software coders. I also include systems administrators, systems engineers and systems architects as well. All of these technical roles have the ability to play such games to help increase their perceived “value” to the company.

No one wants to be considered obsolete by their employer. To that end, many software designers, engineers and even systems administrators, choose to keep their jobs secure by engineering their own continued necessity. How do technical employees engineer their own continued necessity? By introducing system breaking bugs. If things are “broken”, the company will continue to need someone to “fix” it.

How this situation manifests is that these folks break small things here and there. They don’t break the whole system, though they could very easily do this if they wanted. No, instead, they engineer breakage in small tertiary components. They engineer situations that are just problematic enough to be annoying, but not problematic enough to keep the product from working entirely. Though, I have worked with some folks who will and have chosen to break the entire system, bringing down the entire product for several hours.

There’s a fine line when considering breaking small things versus large things. Breaking the whole system is a firing offense. If you break the entire system such that no one can use it for hours, that’s something that will get at least one person fired. This doesn’t afford job security. Just the opposite, in fact. Breaking the entire system will get someone fired.

Breaking tiny tertiary pieces isn’t a firing offense (at least as long as the engineer doesn’t go blabbing about what they did). In fact, breaking something small is usually seen as unintentional by most bosses. After all, a boss might think, “Why would they break this tiny thing intentionally?” For this thinking logic, such small things are assumed to be a bug.

Many software engineers (and similar people in similar lower level positions) take advantage of this flawed managerial thinking logic and choose to break underlying, but very small components. Why? As this section states, job security. If small things are continually broken, the company will need someone who “knows that code” to fix it. Hence, continued employment for that person. Yes, it’s a shitty thing to do, but people also want to remain employed. When you hire bright people to write code, you also hire their scheming minds. Expect them to take advantage of such internal managerial flawed rationales to their own benefit.

How does this relate to Deathclaw Hide? It relates because the person who manages this specific portion of Fallout 76 wants to remain employed by Bethesda. If they break something small, Bethesda will eventually turn to them to ask them to fix it once enough people complain. See, job security does sometimes work… as long as they don’t get caught at it. It seems that too many employees at Bethesda are playing the “Job Security” game at the expense of Fallout 76. After all, this video game is already mostly a piece of junk. No one is going to see a few more mistakes as any more than “par for The Whitespring golf course”.

Rant over.

So where can I find Deathclaw Hide?

I’m coming to that. I wanted to rant a little about Bethesda before I got to this point. Since Deathclaw Hide no longer spawns on Deathclaws after you kill them, you must rely on loot containers and via other means.

Unfortunately, it seems that the same engineer who removed Deathclaw Hide from the loot drop list for Deathclaws also seems to have removed it from the drop list for regular containers as well. This means you won’t find it in toolboxes, wooden containers, coolers, safes or any other similar containers. I know. I’ve spent days culling through every container I could find looking for it. Deathclaw Hide doesn’t even spawn in Deathclaw nests!

I even went looking in non-conventional places. I started searching through Scorchbeast nests. Specifically, the nests in Watoga. I rationalized that Scorchbeast nests tend to turn up unusual bones and stuff. There is a nest on top of Watoga’s Municipal Building (where Mayor for a Day is located). There is also a nest on top of Watoga’s Civic Center. While these nests both spawn all sorts of goodies, such as Scorchbeast Hide, Scorchbeast Brain, Scorchbeast Meat and Scorchbeast Heart, it doesn’t spawn anything related to Deathclaws.

However, the Scorchbeast Guano piles will occasionally spawn Deathclaw Hands. Unfortunately, these don’t count towards the Possum Leatherworker challenge, even though Deathclaw Hands provide 3 leather. Go figure.

After spending time making various runs to these Scorchbeast Nests, I then had another thought.

Fissure Sites

I realized that I was going about this all wrong. Around the lip of every fissure is an array of dead animals. I also realized long ago that existing already-dead carcasses in the game spawn the hide of the dead animal.

While a Bethesda engineer decided to remove Deathclaw Hide from the live Deathclaw drop list, he/she forgot to remove it from the already dead carcasses that you can find around Appalachia. For example, there’s an already dead Yao Guai at the Abandoned Waste Dump. This permanently dead carcass spawns Yao Guai hide. If you ever need Yao Guai hide for any challenge, make your way to the Abandoned Waste Dump and pick it up. No need to kill anything. Just loot and be done.

This is why I began thinking, “Where can I find already dead Deathclaw carcasses in this game?” That’s when it dawned on me to visit the fissure sites.

Sure enough, there are already dead Deathclaw (and other) carcasses around the lip of fissures. Deathclaw Hide still spawns on these already dead Deathclaw carcasses. Yay! No need to run around killing Deathclaws if we don’t have to, eh? If you’re looking for Deathclaw Hide, you’ll want to visit the lip of the fissure sites to loot these already dead Deathclaws. The difficulty, of course, is that these fissures tend to spawn a crap ton of Scorched and at least one Scorchbeast, in addition to irradiating you. Be prepared with RadShield, RadX, Radaway or Power Armor and also be prepared to take out the enemies… or, alternatively, use the Sneak card to sneaky sneak your way in and out without being easily detected.

Unfortunately, you will only find one hide per carcass. Even then, it doesn’t always spawn. But, it spawns more often than anywhere else. Fortunately, there are 9 fissure sites around Appalachia that you can visit and check out the dead Deathclaw carcasses. At least one of them will have a hide. If you server hop, you can probably find all 5 of the hides that you’ll need to complete the Possum Leatherworker challenge.

I have found that the fissure sites are the most reliable places to locate Deathclaw Hide in Fallout 76. That is, until another engineer chooses to remove Deathclaw Hide from the loot drop list for these already-dead Deathclaws at the fissure sites, too. 😕

Good Luck.

If this article helped you, please leave a comment below. If you know of the location for other dead Deathclaw carcasses around Fallout 76 (besides fissures), please let me know where you found it in the comments below.

↩︎

The Microsoft Botch

Posted in botch, microsoft, redmond, windows by commorancy on January 14, 2009

Well, what can I say?  Microsoft has been one series of botch jobs after another recently.  I guess every company goes through a spate of problems, but this series of problems seems a bit excessive (and avoidable). Consider that Windows ME more or less started the botches (ignoring Microsoft Bob).  But, after ME they had the successful 2000 and XP series… then Vista.  Vista is the albatross that Microsoft would like to soon forget.  But, that’s not all of their problems.  We’ll come back to Vista.  

The Office botch

Office 2008 for the Mac has been a huge bust (just check the reviews on Amazon) by the users because of the lack of VBA (among other compatibility issues).  Then, there’s Office 2007 for Windows, which some developer in their infinite wisdom decided to use Microsoft Word’s HTML parser to render HTML emails!  So, when you’re viewing HTML emails in Outlook 2007, there are page breaks!  I’ll say that again, “page breaks”.  You read that correctly.  Since when does anyone paginate web sites?  What makes Microsoft think that people want to see web pages paginated?

That doesn’t even take into account the entire GUI change they made between Office 2003 and Office 2007.  Sure, 2007 is supposed to look modern and streamlined.  But, instead, the new GUI ends up with a huge learning curve and is basically incompatible with previous versions of Office.  Instead of doing actual work, now you have to chase down the function you need because it’s not where it used to be. The addition of the stupid round Windows Flag button instead of an actual menu bar is completely assinine design.  Let’s hope that whomever thought up that innovation no longer works in Redmond.  There are some things that just need to be user tested and this product clearly wasn’t.

The Zune botch

Consider the Zune 30GB had a leap year bug that caused the entire unit to completely freeze up.  This required the owners to wait until the battery completely drained to reset the unit.  That and wait until after the new year, otherwise it would refreeze.

The infamous Xbox 360 overheating botch

To this date, Microsoft STILL has no clue what’s causing the issue or how to resolve it.  They *think* it’s related to heat so they’ve added a heat sink to try and help the issue.  Even still, they had to take a huge financial hit and extend the Xbox 360 warranty out to 3 years from its original 1 year.  

The Origami botch

“What was Origami”, you ask?  Nuff’ said.  If you really want to know, read this Wiki article.

Tablet Computers

Um, where are they today?  No where. People don’t want to lug tablets around.  They didn’t want to lug them when Grid was around.  What made Microsoft think people would want to lug them around 10 years later?  Oh right, I guess they thought they would because that oh-so-heavy tablet was running such a wonderful touch screen version of Windows.  Doh!

The IE7 botch

Ignoring Microsoft’s constant security flaws as a botch job, although some of them certainly qualify, another is Microsoft’s decision to remove the ability to uninstall IE7 after you install Service Pack 3 (SP3) on XP.  So, for an IE repair that should have taken all of about 15 minutes, you’re now saddled with the task of whipping out the Windows installation media and running repair on the entire operating system (broken or not).  Thanks Microsoft.

Note that Microsoft’s justification for this IE change stems apparently from some files that SP3 installs.  The SP3 installer may overwrite either IE7 or IE6 files that, were Microsoft to allow removal of IE7, might leave the system in an unstable state if you were to use IE6.  Well, hello, you guys wrote the software!! So, instead of actually taking the time to write SP3 properly to still allow software removal of IE7, you take the easy way out and leave the system owner saddled with a huge task just to repair IE7 when it breaks.

Why does this matter?  Been living in a cave?  IE7 is not completely stable.  Much of the time the search provider installation process doesn’t work.  You try and you get ‘Errors on page’ and the search providers cannot be loaded.  Then you have the ‘Save Your Settings’ problem.  Once you install IE7, it asks to save default settings.  Yet, much of the time this process won’t save settings and always continues to present this panel on startup.  I’ve searched and searched and have been unable to find a workable solution to either the search provider or the save defaults issues.  The ONLY workable solution (uninstall/reinstall) was conveniently taken away by Microsoft in their infinite wisdom.  So, instead of a 15 minute fix, it now takes 2-3 hours to completely repair the system, reinstall windows updates and test everything.  Of course, it is possible to remove SP3, but at what risk to the system?  These things rarely work once you’ve installed apps on top of the system after an SP is installed.  In other words, be prepared to have things begin breaking and applications to need to be reinstalled.

The bottom line is that Microsoft made this change to make things easy for Microsoft.  For the end user, however, they will now incur high priced repair bills simply because Microsoft decided to make things easy for themselves.

The Vista botch

Well, what can be said about Vista that hasn’t already been said?  Vista has so many user interface problems, lackluster performance, the overreaching and underperforming Aero system and the constant flickering between various modes and resolutions that make Vista seem more like Windows 3.1 than it does a mainstream OS.   Combine this with constant driver issues, Vista is completely unsuable for any real purpose.  You’re forever repairing it instead of actually using it.  Vista also requires a hefty powered system to even perform decently.  So, it’s no wonder businesses didn’t adopt it.

Combine all of this with the marketing of Vista, it’s just been a disaster.  For whatever reason, Microsoft decided to put out 5-8 different version of Windows Vista… 3-4 of which were targeted at home consumers.  This is more confusing for consumers than it is helpful.  This should have been paired down to 1 to at most 2 versions.  Consumers don’t want 4 choices in an OS.  They also don’t want to pay $400 for an operating system.  Yet more botch.

Windows 7 botch or not?

If Microsoft adopts Vista’s codebase to build Windows 7, this product will be no better than Vista and will likely end up being yet another botch.  Vista’s codebase for the driver subsystem is a complete disaster (and continues to be a problem even as of this blog article).  By taking Vista’s codebase for Windows 7, Microsoft ensures that Windows 7 will be just as problematic as Vista.  The interface is only half of Vista’s problem.  People can overlook the GUI learning issues when the components under the hood simply work.  But, they don’t.  For example, one of the most significant problems that Vista suffers from is “Display Driver has stopped responding and recovered”.  Ok, now what is this?  We’ve never ever had this issue before.  Granted, maybe it prevents the blue screen of death, but having the display driver stop responding means what exactly?  And, why is it now that the video drivers are just now having this problem.  Using Vista’s codebase practically assures this issue to contiinue in Windows 7.  So, 7 will end up just as driver problematic is Vista.

Suffice it to say that Microsoft is going through a bad way.  Perhaps they’ve had an exodus of people who actually knew where to take things. But, Windows has become such a bloated hodge-podge piece of trash, I don’t know if Microsoft can honestly salvage it.  Vista and Windows 7 may end up being the death knell for this operating system.  By Microsoft basically botching their two flagship products (Office and Windows), I don’t know if they will be able to recover easily.  Combine this with stupid programming mistakes (like the Zune) and clearly, Microsoft has major internal issues that need to be addressed.

Whatever the issue, I don’t see this botch trend ending any time Zune (pun intended).

Tagged with: , , , ,
%d bloggers like this: