Ignoring the Poor Little White Guy vibes of the photo, he seems like a sweet guy.
Who's the husband? There are two guys on the right. One of them looks like a fag, but at the same time looks too young for Tim.
Oof that coeraive pregnancy anecdote is pretty rough in retrospect. Thank God for ttrpg safety tools now.
Would you ever want to roleplay again, Tim? I'd happily run something. FO1 and 2 were games I played everyday in the same era when I first discovered D&D, and a lot of those early lessons informed much of how I write and design TTRPGs now.
Tim said:Yeah, that pregnancy thing was weird even then. I never liked romances in RPGs, tabletop or computer, so that whole storyline came from a comment another player made about Catherine's druid agreeing to marry the Dirk the anti-paladin to save the party. That player said that she hoped that the druid and anti-paladin didn't consummate their marriage, so Catherine and I agreed to roll a die to see if she was pregnant. She was.
Later the party found a cursed belt that changed the wearer's gender, and it started a LONG uncomfortable discussion about what would happen if the pregnant druid put it on.
Romance in TTRPGs is fine, as long as the players agree that's the kind of game they want to play. Plenty of indie TTRPGs have that as a design focus. It's the lack of consent in the forced marriage and pregnancy that becomes an issue.
Tim said:Agreed. I should point out that the druid initiated the conversation with the anti-paladin, who was just going to attack the party, and suggested sacrificing herself so the party could live. I rolled a really high reaction roll from the anti-paladin, even before adding the druid's 18 charisma bonus, so he agreed. None of this was planned, and the players directed this interaction as much as I did.
Still, these things make me uncomfortable because you can never tell if everyone at the table is perceiving this situation the same way. I mean, here I was planning on a big battle in dark castle between the anti-paladin (and his men-at-arms) and the player party, and I ended up with the druid discussing which room in the castle to use as a nursery.
It was a weird night. But if anything, it underscores my point that the DM never knows what the players are going to do.
The beardo with the nose ring. Tim is into fellow bears.Who's the husband? There are two guys on the right. One of them looks like a fag, but at the same time looks too young for Tim.
Or Vault 76.They'd obviously have called the sequel Vault 14.
I talk about how Fallout was never a high-status project at Interplay until very shortly before it shipped.
What I find interesting in all this is that Brian Fargo was (and is) a true gamer and he actually played (and enjoyed) the games that he published. The rest of managment (most likely including Faergus) preferred Excel.Tim Cain said:I explain why I left Fallout 2 early in its development. TLDW: exhaustion, interference, lack of motivation.
What I find interesting in all this is that Brian Fargo was (and is) a true gamer and he actually played (and enjoyed) the games that he published. The rest of managment (most likely including Faergus) preferred Excel.Tim Cain said:I explain why I left Fallout 2 early in its development. TLDW: exhaustion, interference, lack of motivation.
Edit:
Brian Fargo was clearly Tim's fanand he insisted that Tim would work on Fallout 2. When Tim complained that some woman was making decisions on F2, Brian Fargo asked if he wants her fired :D. Tim also talks about how a simple "for >=" loop broke Fallout and forced them to delay a game by a couple of months.
Edit 2:
lol at Brian Fargo for cutting Tim Cain's bonus for not telling whose bug (for >=) it was.
Tim Cain said:I explain why I left Fallout 2 early in its development. TLDW: exhaustion, interference, lack of motivation.
Trying to punish an individual developer for a single bug (an off by one error which is one of the most mundane of programming mistakes) is pretty insane management. And the impact of the bug (i.e., delay of the release) is not a programming issue at all but a an issue with management for setting too tight deadlines in the first place. But of course management never wants to take any responsibility for that... so instead they lost two star employees.I don't see why Timmy was so upset over his smaller bonus. A bonus is just that, you're not entitled to one. It was his decision to take responsibility for the delay-causing crash bug and that means accepting the punishment for it. Fargo did nothing wrong there.![]()