People generally seem to say their game freezes with this game. We’ll see how many more pop up as I continue to hunt for those few remaining Achievements… A funny glitch, but not as harrowing as the Alpha Male Deathclaw one.
Last night, Boone found himself trapped inside a bunch of desks in Vault 3 for too long, switching between melee and ranged weapons with strange determination. I made a bee-line for Novac and haven’t gone back to Sloan yet. The Alpha Male Deathclaw glitch had left its mark for certain. No sniffling sound, and that’s when I saw her, Snuffles, slumped over, unmoving, unmovable. The Deathclaw was gone, my status stated I was safely, and all was quiet. Carefully, cautiously, I went back outside. The third time, I turned 180 degrees, and went back inside the building, praying nothing followed me–nothing did. The game loaded up with my latest auto-save, which was me exiting the building, and the Deathclaw still spawned. With one swipe, it murdered Snuffles and then took Rhaegar down. …to discover, to my and Snuffle’s horror, that an Alpha Male Deathclaw, probably the toughest enemy in all of Fallout: New Vegas, had spawned directly in the middle of Sloan.
I headed into one of the shacks in Sloan to ask about how to make Deathclaw omelets, hoping to nip this weird status glitch in the butt. The status continued to change back and forth, too. As I crept closer, I noticed the status changing to and then despite no enemies being nearby at all. What, you don’t know who Snuffles is? Why, she’s Sloan’s personal mole rat, a friendly one too. Leaving Goodsprings, I headed out towards Sloan because I knew that I could at least get a few snippets of EXP from fixing one of the generators and healing Snuffle’s injuries. I was just beginning to scope out the landscape with Rhaegar, my fourth playthrough character, trying to locate some of the more pertinent locations so that they would be ready for fast-traveling.
I just can’t seem to escape writing about ’em. And this one’s a doozy. Continued abuse of our services will cause your IP address to be blocked indefinitely.I’m going to be talking about a spectacular glitch from Fallout: New Vegas today, one so amazing in its horribleness and mind-fuckery that I had planned to draw a journal comic about it, but my wife beat me to the punch, which is fine as it’s a great l’il comic that captured the infamous event perfectly:Ĭlick for a bigger version, yo. And yeah, I like to sit on the floor when I play. Please fill out the CAPTCHA below and then click the button to indicate that you agree to these terms. If you wish to be unblocked, you must agree that you will take immediate steps to rectify this issue. If you do not understand what is causing this behavior, please contact us here. If you promise to stop (by clicking the Agree button below), we'll unblock your connection for now, but we will immediately re-block it if we detect additional bad behavior. Overusing our search engine with a very large number of searches in a very short amount of time.Using a badly configured (or badly written) browser add-on for blocking content.Running a "scraper" or "downloader" program that either does not identify itself or uses fake headers to elude detection.Using a script or add-on that scans GameFAQs for box and screen images (such as an emulator front-end), while overloading our search engine.There is no official GameFAQs app, and we do not support nor have any contact with the makers of these unofficial apps. Continued use of these apps may cause your IP to be blocked indefinitely. This triggers our anti-spambot measures, which are designed to stop automated systems from flooding the site with traffic. Some unofficial phone apps appear to be using GameFAQs as a back-end, but they do not behave like a real web browser does.Using GameFAQs regularly with these browsers can cause temporary and even permanent IP blocks due to these additional requests. If you are using Maxthon or Brave as a browser, or have installed the Ghostery add-on, you should know that these programs send extra traffic to our servers for every page on the site that you browse.The most common causes of this issue are: Your IP address has been temporarily blocked due to a large number of HTTP requests.