Battlezone Forums

So I'm stuck here, i've restarted the mission a few times but I can't get Shabaev to put out the nav point for the archers.

I put up the jammer and lure stuff in and ISDF just start sending unlimited units to my base. I've manually tried to get archers to destroy the base power but it never triggers anything.

Now...I am wondering if the game is messed up because of a previous mission. On the mission where you make the choice to go with Shabaev or destroy her, I followed her and ended up at the AAN Rebels mission (one where you are in the mech) and then after that mission I ended up at ambush.

am I doing something wrong? If I go back to my save where you make the choice and destroy shabaev i end up at the AAN rebel mission and continue.

Both the mission order being broken after Fanning the Fire and the stall in Ambush's mission script are known issues. Unless someone else has a workaround your best bet is to use game.cheat bzwinner in console.

ahh, i looked around and didn't see anything about it.

It took me some time to figure out I needed the bz19 patch....took me till the ambush mission to realize I couldn't upgrade anything

try this:

https://dl.dropboxusercontent.com/u/98749582/scion02.7z

unzip so that scion02.dll and scion02.pdb are in addon\Missions

will do. thanks guys

Forgot how awesome this game was, I haven't played it in probably 5 or 6 years.....

I am glad it is still going strong and sad that there will never be games like this again.

bigbacon wrote:I put up the jammer and lure stuff in and ISDF just start sending unlimited units to my base. I've manually tried to get archers to destroy the base power but it never triggers anything.

Wow. This brings back memories. I first experienced this bug probably back in 2004 when I first played through BZ2. I remember the endless supply of enemy forces coming at me. I was new to BZ2, so I just played it for hours and hours, slaughtering the endless ISDF forces as they kept coming.

Eventually I realised that this was not letting me progress in the game, so I quit and started the mission again. It has worked properly since then and I've never experienced the bug again.

I thought it was a one-off issue and long gone, but apparently not.

#Nostalgia