Also, I have no idea why I'd ever want to side with the Voodoo Boys who set you up to be a suicide bomber over the '''evil''' government agent who doesn't lie to you at all, is completely straight with you, tells you the truth and keeps his promises. Only an idiot would listen to Johnny's advice (who is completely wrong about the entire situation). Fuck them off-brand Haitian motherfuckers.
You might just say, "Well, then they could have put that time and money elsewhere" No. No they wouldn't have. I'm not letting those polish faggots get any more excuses. Shit, they could have hired a Source Porn animator to do the fucking thing and get a whole fucking minigame (literally) for probably how much money they spent modeling their 'sex scenes'.
Because games have to be movies these days I suppose.
EDIT:
God these bugs are infuriating. In 5 minutes:
>The map itself was busted in an area because the areas were shown as 'open' when in reality they were blocked off in the game. Other areas were not like this. The designers did not sync the quest markers properly to the map, so you ran around in circles. Either that or the map/quest were different and never updated and synched it to the new quest.
>Quickhacked and short-circuted not one, not two, but three enemies who all were electrocuted and just stood stock still, upright, with 0 HP in an idle animation as if they were alive, but were dead, their items lootable from their upright bodies
>Last guy alive was 'hiding' behind cover, as in, his skeleton fucked up and he was on his side in the ground at about a 45 degree angle shooting at me.
>Gunned down the survivor to only have "POSITION BEING REVEALED" as if I was being hacked, stuck on my screen at 0 percent done, out of combat, with its obnoxious beeping noise, forcing me to quit back to the main screen.
>Lip synching stopped working for an NPC, so he was there talking to me. His expressions changed with his dialogue, but the lip synching did not update, so he was staring at me with ANGRY FACE while his voice lines were going.
I'm just fucking astonished at how bad this is. Imagine how bad it must have been previously that they didn't ship it out. I have honestly not had a game like this in such a long time.
EDIT2:
Another thing I just realized, the hard way.
About...five minutes after all the glitches I encountered in five minutes...my game broke. Well, to be fair, it didn't so much as break as "We fucked up this door, so it won't open for you, so you can't progress anymore". I tried reloading a save. I tried quitting out and re-launching. Nothing. So I was like, "fuck it, I'll just turn on the console and punch in no clip mode." Wwweellll...............
Cyberpunk 2077 DOESN'T have a console. Not one you can add in XML files. Not one you can turn on. It, flat out, does not have one. And the only way to add one is through a mod.
And....
It doesn't have a noclip mode.
You have to...mod in....no clip. I wish I was joking. I wish, in the year of our Lord 2020, that a game would not have a feature of a game in 1990 had. A noclip function. Fuck you dumb Polish niggers. This is now a 5/10. And yes, I am taking a full point off for not including a fucking console and having to mod in noclip. How in the fuck do people think this thing is going to be moddable without a fucking console, without fucking noclip that you have to add in YOURSELF.
This will not be easy to mod, mark my fucking words. I'm more convinced of that now than ever. Eventually I got it to work by reloading a save from a different area and getting a transition. Because this glitch (Seriously, get this) carried over a modifier from the map where there were screens on doors and it opened them after a quest flag. That flag was never disabled and stuck around, so it added screens on ALL doors. I wasn't actually trying to open a door, I was trying to open a quest flag. Jesus christ. It was from the first glitch in my five minute glitches.
The problem was, the game was reading the map as open, when the quest flag was improperly enabled. So because the quest flag was frozen 'on' but the game considered the quest complete, the map did not sync properly with the game state. So, I was wrong. The map WAS correct. It was the entire play area that was wrong. So the game is for sure having problems enabling and disabling flags for quests and synching them to the game state. By the way, this was on the first run through of this section. So it isn't like a Q&A tester wouldn't have found this if some...any....decent Q&A was done.
