Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Second time Suggs dies, the game locks up during the 10mm firing animation.
So, if for whatever reason he does, the game can't handle that and crashes, trying to refer to null data. I remember something similar with New Vegas involving noclipping and trying to kill an NPC inside the Ultraluxe before he performs his scripted event; killing him in his off-world holding cell almost immediately makes the game implode on the spot. After his scripts run, he's perfectly fine to be killed because there is code that says so.
Factor in this update first shipped with literal missing meshes with weapons firing debug error objects, and tons of broken spaghetti code that has affected the base game functionality, and Suggs being broken isn't all that surprising.
Just for all those peeps who were confused like me.
He Suggs.
It sure Suggs if you kill him twice.
Kill this guy twice and the game freezes or blue screens. That's a bug not an exploit.
Why would you kill in the first place?
Well, my encounters with him has been fine. But I don't try to kill him or use his workbench. lol.