MASSIVE ISSUE PLEASE HELP

[Emmanuel]

So I have a **Mostly** Stable fallout new vegas game with 140 plugins installed. I have Freeside open which is a nightmare (If you are reading this, DO NOT INSTALL FREESIDE OPEN. THAT MOD IS INCREDIBLY♥♥♥♥♥♥AND WILL RESULT IN ALL SORTS OF PROBLEMS).

So like I said. I have Freeside open but I recently installed New vegas bounties which is incompatible. I installed the patch but I found out it only works **if** you never visited Freeside before. The issue is that when confronting Jasper. He tells you to find out Ben's fate. You turn a corner in a alley only to find his dead mutilated corpse. A message prompt is supposed to show up and you get ambushed by Alex (The guy who you're hunting). But the prompt does not show up and so Alex does not show up. Can someone help me? I resorted to uninstalling but that caused tons of problems. I reckon if someone were to tell me the ID to skip the objective and spawn Alex. Then It would be fixed

[ElPascal]

Honestly, I'm kind of amazed your game runs at all, since 135 plugins is usually described as the hardcoded limit before the game falls apart. Don't have NVB installed right now, I suppose you'll have to look into the mod via GECK or FNVEDIT and see what the ID of your current quest is.

[Emmanuel]

I know that other people have fixed the issue (With no detail as to how). But I know that it involves going to FNVedit. And looking for the ID. But do they mean the ID of said modded quest or quest stage. Besides, I couldn't skip quest because that would skip the ENTIRE quest (no separate quests.) Then I need to know the ID of Alex (The NPC) Just in case if the script does not work. And yeah

[Samar3n]

Have you fixed it? Same problem here.

[Emmanuel]

Unfortunately you just have to remove Freeside open entirely


Besides there's literally next to no point in having that mod, all in all that mod is incredibly bad for your game and can result in tons of stablity issues which ♥♥♥♥ everything up

So uninstall and start new game and everything is good :D

[λτlαs]

you shouldn't use freeside/strip open mods anyway just as how you shouldn't use open cities mod in skyrim = they break a lot of stuff and the performance is trash

[Grimsdottir]

I'd recommend leaving the area. Fast travel if you can and go into a separate cell or hell. Even inside the kings building and save. Quit the game. Uninstall the Free side open mod. Relaunch the game and see if that fixes it.

[Samar3n]

Thanks for advice, I fixed it without uninstalling.

[shiby]

Originally posted by Rookie:

So I have a **Mostly** Stable fallout new vegas game with 140 plugins installed. I have Freeside open which is a nightmare (If you are reading this, DO NOT INSTALL FREESIDE OPEN. THAT MOD IS INCREDIBLY♥♥♥♥♥♥AND WILL RESULT IN ALL SORTS OF PROBLEMS).

So like I said. I have Freeside open but I recently installed New vegas bounties which is incompatible. I installed the patch but I found out it only works **if** you never visited Freeside before. The issue is that when confronting Jasper. He tells you to find out Ben's fate. You turn a corner in a alley only to find his dead mutilated corpse. A message prompt is supposed to show up and you get ambushed by Alex (The guy who you're hunting). But the prompt does not show up and so Alex does not show up. Can someone help me? I resorted to uninstalling but that caused tons of problems. I reckon if someone were to tell me the ID to skip the objective and spawn Alex. Then It would be fixed

I know it's been over two years since you posted this, but just in case you still need help or if anyone else stumbles upon this, I found a fix.

TLDR : setstage xx000ae1 70

you can simply skip the bounty of alex, not by completing the entire quest via console but rather "skipping" the part of ben and killing alex
sadly due to freeside open you won't be able to actually "kill" alex and his goons, technically he will still be dead and therefore removed from the game, you just weren't really there when it happened. he was killed by a ghost.

now, if we scroll to the bottom of the official mod-quest page, we can see the quest stages, up until 65. I assume they just didn't bother to go any further than that, but if you use the console command "setstage (questid) (queststage)" you can skip that stage as I said.
now, as it says on the page, the questid is xx000ae1, in XX you will have to insert the numbers of the plugin of new vegas bounties of it's mod index. no, not the load order, but the mod index, don't know why everyone always says otherwise. In my case it was 59.
the quest stage on the other hand is 70, as it ends at 65 on the mod page, the stage for where the bug with ben's corpse happens is 65-68, whereas the stage for alex's encounter as well as killing him is 67-70. So, if we go with setstage 70, it will effectively set the quest's stage to where you have to deliver alex's finger to randall.

now, you may not have alex's finger, but that doesn't matter, you just say "Yes" and you will get the money for the bounty and move onto the next, as if you had normally continued the quest without any quest rewards.

so, all you really have to do is use the setstage command with the questid and numbers of your mod index for nv bounties as well as the number 70 at the end for the right stage. Obviously, use this command after talking to Jasper and going to the dumpsters, not before talking to jasper.
in my case, the command was as followed: setstage 59000ae1 70
I also recommend doing the same command but with 66-68 as numbers instead of 70 at the end before, to get rid of the "find out ben's fate" stage in the pipboy.
after that I could fast travel back to randall and give him the non existing finger, get the money and continue with the next bounty as usual.

sorry for the really long description, i'm not good at explaining stuff but I wanted to kinda show how I even go to that fix as there's really not *that* much magic involved.

[Emmanuel]

Originally posted by shiby:

Originally posted by Rookie:

So I have a **Mostly** Stable fallout new vegas game with 140 plugins installed. I have Freeside open which is a nightmare (If you are reading this, DO NOT INSTALL FREESIDE OPEN. THAT MOD IS INCREDIBLY♥♥♥♥♥♥AND WILL RESULT IN ALL SORTS OF PROBLEMS).

So like I said. I have Freeside open but I recently installed New vegas bounties which is incompatible. I installed the patch but I found out it only works **if** you never visited Freeside before. The issue is that when confronting Jasper. He tells you to find out Ben's fate. You turn a corner in a alley only to find his dead mutilated corpse. A message prompt is supposed to show up and you get ambushed by Alex (The guy who you're hunting). But the prompt does not show up and so Alex does not show up. Can someone help me? I resorted to uninstalling but that caused tons of problems. I reckon if someone were to tell me the ID to skip the objective and spawn Alex. Then It would be fixed

I know it's been over two years since you posted this, but just in case you still need help or if anyone else stumbles upon this, I found a fix.

TLDR : setstage xx000ae1 70

you can simply skip the bounty of alex, not by completing the entire quest via console but rather "skipping" the part of ben and killing alex
sadly due to freeside open you won't be able to actually "kill" alex and his goons, technically he will still be dead and therefore removed from the game, you just weren't really there when it happened. he was killed by a ghost.

now, if we scroll to the bottom of the official mod-quest page, we can see the quest stages, up until 65. I assume they just didn't bother to go any further than that, but if you use the console command "setstage (questid) (queststage)" you can skip that stage as I said.
now, as it says on the page, the questid is xx000ae1, in XX you will have to insert the numbers of the plugin of new vegas bounties of it's mod index. no, not the load order, but the mod index, don't know why everyone always says otherwise. In my case it was 59.
the quest stage on the other hand is 70, as it ends at 65 on the mod page, the stage for where the bug with ben's corpse happens is 65-68, whereas the stage for alex's encounter as well as killing him is 67-70. So, if we go with setstage 70, it will effectively set the quest's stage to where you have to deliver alex's finger to randall.

now, you may not have alex's finger, but that doesn't matter, you just say "Yes" and you will get the money for the bounty and move onto the next, as if you had normally continued the quest without any quest rewards.

so, all you really have to do is use the setstage command with the questid and numbers of your mod index for nv bounties as well as the number 70 at the end for the right stage. Obviously, use this command after talking to Jasper and going to the dumpsters, not before talking to jasper.
in my case, the command was as followed: setstage 59000ae1 70
I also recommend doing the same command but with 66-68 as numbers instead of 70 at the end before, to get rid of the "find out ben's fate" stage in the pipboy.
after that I could fast travel back to randall and give him the non existing finger, get the money and continue with the next bounty as usual.

sorry for the really long description, i'm not good at explaining stuff but I wanted to kinda show how I even go to that fix as there's really not *that* much magic involved.

Damn this post just brought a whole heap of nostalgia

I've stopped being into New Vegas mods since I've had a million more playthroughs since this one but I might get into it again

However thank you for being an absolute legend for figuring all of this stuff out. Lord knows I couldn't have figured it out

Thanks man

[Salamand3r-]

Note that if you play again, there are actually open strip and freeside mods that don't break the game nowadays.

[Mr. Reck]

Got the ID for Alex: aaAlex. So use player.placeatme aaAlex

[Mr. Reck]

You can use FNVedit to look into the mods assets for future reference.

[Smokey]

Originally posted by Reckypoo:

Got the ID for Alex: aaAlex. So use player.placeatme aaAlex

You're a lifesaver!

[Blake]

This thread was quite old before the recent post, so we're locking it to prevent confusion.