Fallout 4

they did on pc where they fucked everything up. The consoles seemed to get all the love but still somewhat b0rked. Newest patch resolves some console issues but pc is still a festering turd and haven't seen anything to the contrary yet.

Seems to be mostly the BOS quests that are bugged, had to reload to get Danse to acknowledge me, The Lost Patrol is still bugged and the woman won't accept me handing in the quartermaster quest. We'll see if getting to BOS part of the story fixes it, if not then I'll just load up my mini nue launcher.

Knight Astlin's holotape. Never spawned on his body and the quest marker is pointing me at a terminal on Abernathy Farm where tatos should be growing lol. Searched the whole area, even in build mode and it definitely isn't there. I know it can be turned in to Kells later instead of Danse so maybe his arrival will cause it to spawn.

They will never replace it. They have too much tooling built around it.

I did try and start a game recently but just found the jank, the menu system, the poor flow of the story at the start, the dead eyes and dialogue just unacceptable. The best parts was actually reading the info on the computers dotted around the place, felt it would have been better just as a text adventure. Probably being a bit hard on it to be fair but overall it did nothing to hook me into the world.

That's such a weird stretch...

I play Satisfactory all the time. Object permanence and it's just Unreal engine.

I had the same experience with FO4. Felt very unadventurous.

It feels like it was made for the mass market, can't have RPG stats or complex choices. use to be on some forums  back then  and those gamers really didn't like stats to guns or speech checks for alternative ways to complete missions

I don't really get why people say they need to stick with the engine to maintain mod support. If they made a new engine, wouldn't they just build it with mod support in mind? The whole point of creating a new engine would be to tailor it to their needs. Are people just porting their mods to each new game?

Back when id made new engines for Quake, Quake 2, 3, etc, they were very similar when it came to modding (probably the last time I knew anything about modding) and going from one to the next never had a detrimental affect on the modding scene - on the contrary

I feel like the people who have been modding for their games for decades would enjoy the process of learning how to mod for the new engine. Also, you would think with a new engine, the kind of mods that just fix things would be less necessary

Surely they could have some people low key working on a new engine, even if they didn't intend to use it for the game they're currently working on?

Agreed that it's not just a quick lift and shift that people seem to think it is, but even so they've had bloody ages to plan the move.

CDPR seem to have managed it pretty well in comparison, although I guess it'll be a good few years before we see the proof of the pudding there.

The thing with tooling like that is for something like this you end up having to maintain your own tooling if you're the only one using the engine. So you get a benefit project to project of familiarity but an overall drag of doing maintenance (or not) of said tooling.

CDProject Red have clearly made a decision to ditch theirs to use more standard Unreal stuff. That said a bunch of tooling can be made in an engine agnostic way, to some extent.

iI think if your security value is more than double the food and water value, then attacks rarely happen. Raiders want to attack camps with more resources and less security, unfortunately