The forum has been set to read-only mode. For community discussion and questions, head over to our Discord: https://discord.taleoftwowastelands.com

Bug: Starting in NV prevents doing 'Trouble on the Homefront'

General help and technical troubleshooting. Ask for help here if you can't find an answer in the FAQ.
Post Reply
User avatar
WalkerMx
Posts: 8
Joined: Sat Apr 30, 2022 7:18 am

Bug: Starting in NV prevents doing 'Trouble on the Homefront'

Post by WalkerMx » Fri Aug 26, 2022 7:40 pm

If when starting a new game, you choose New Vegas, you cannot do 'Trouble on the Homefront.'

The door that leads into Vault 101 leads to the Intro Sequence version, even after completing "The Waters of Life."

As far as I can tell, this is because CG04 ('Escape!') starts MS16 ('Trouble on the Homefront'), which then switches the doors when the time is right.

If you start in New Vegas, CG04 is skipped, preventing the doors from being switched.

Running "SetStage MS16 0" in the console corrects this.

Adding this line to TTWStartScript fixed the bug on a new character.

User avatar
RoyBatty
Gary
Posts: 7742
Joined: Sun Apr 27, 2014 10:26 am
Location: Vault 108

Re: Bug: Starting in NV prevents doing 'Trouble on the Homefront'

Post by RoyBatty » Sun Aug 28, 2022 12:19 pm

It's intentional.
Image

User avatar
WalkerMx
Posts: 8
Joined: Sat Apr 30, 2022 7:18 am

Re: Bug: Starting in NV prevents doing 'Trouble on the Homefront'

Post by WalkerMx » Sun Aug 28, 2022 6:29 pm

Ah, I see.

So then, should the radio signal that starts the quest not play if you start in New Vegas? This is what happened to me, and is why I was confused.

I believe, if you return to DC, and you've already completed MQ05, TTWFNEnableDCWasteland does:

Code: Select all

	if ( GetStageDone MS16 200 == 0 && GetStageDone MQ05 200 == 1 )
		MS16Vault101ExternalRadioREF.Enable
	endif
Maybe, instead do something like:

Code: Select all

	if ( GetQuestRunning MS16 == 1 && GetStageDone MQ05 200 == 1 )
		MS16Vault101ExternalRadioREF.Enable
	endif
I know this is probably a fringe case, but I hope it helps.

Edit: I actually don't think it's the TTW script that's letting the radio broadcast. The edit might prevent it from broadcasting when it shouldn't, but now I'm not sure what's setting the broadcast state to 1 if TTW doesn't let MS16 start.

Edit #2: It looks like the default BroadcastState for MS16Vault101ExternalRadioREF is 1, meaning, if it's enabled, the radio channel is available and the emergency message plays, starting MS16 with stage 10.

Post Reply