Goth Zagog-Thou wrote:Thanks for the vote of confidence Rman. The whole reason NEXUS did what he did was because NASDA had eighty-sixed Project NEXUS. They surely had an alternative in place that was better, and now we're seeing it. That's how I've treated the story with regards to NODE, although the Pumpkins never got into the details.
We greatly expand the story in Campaign 5, and that's where NEXUS is rebooted. I'm not ready to provide any more information than that, yet -- I'm still writing, but suffice it to say that Dr. Reed does survive the encounter in Nevada after all -- though it's not by the hand of The Project or NODE. That's how we'll segue into the reboot. Campaign 5, my intention anyway, is to tell a story more than Cam 4 has. Might even warrant a Warzone FMV that could bridge the events of Campaign 4 to Campaign 5, and we'll use what I've written for THAT, instead. Lots we can do here, and I'm definitely open to any and all suggestions and ideas.
oh btw idea for you, nexus finds a way to enter your system but you imediatley find out and eradicate him form your system but by doing so you corrupt some of the system thus causing you to loose a bit of tech or some buildings turn and attack everything =D
Hiya CDO. We don't have a testing version yet -- at least one that I can get running. Milo is working on the scripts still.
For Campaign 5, all I have so far is written dialogue for the initial FMV sequence and Mission 1. I haven't done anything else, and it's a draft at this point.
We've done just about all we can with NEXUS in it's current form. This is the Campaign where we "reboot" NEXUS. HOW that reboot occurs is up to us, I'd really like to make a story out of it rather than just change it up. Think of a NEXUS 2.0 -- what would be different? Is it still Dr. Reed behind the madness? Is this new NEXUS more dangerous than before?
Not yet. Missions are still being scripted. Remember also that nobody is being paid for this work -- we're doing it in our spare time. We all have other things going on along with this.
The problem was that I renamed a file and forgot to update the wrf. Both versions were affected. Somehow I let that change into the wild without testing Everything else was tested though.
I did a little more scripting on mission 3, it's almost finished now. Before it can be loaded there are a few things that need to be changed in the wrf Mostly ids and such. It does need to be supplied with a template, so that will need to be added.
My net access has more or less dried up and blown away so I'm back to the old "lucky if I get on once a week" thing That and other projects are using up my time I'm not going to stop working on the scripts but I won't have much time to work on them.
You do not have the required permissions to view the files attached to this post.
In general, if you see glowing, pulsating things in the game, you should click on them.
- Demigod Game Ganual
2) You'll see 3 folders - Base, 3.0 and 2.3. Whatever version of the game you use (I'm using 2.3.8 ) you take the contents of that particular folder, copy, paste them into Base.
3) While still inside the Base folder, select everything, make a new .zip archive, name it cam4.wz
4) Place this new .wz file into /Warzone 2100/mods/global
5) Change your shortcut you use to launch Warzone (typically on your desktop) and add --mod=cam4.wz at the end, past the quotes. You'll know immediately if it's working or not, because Warzone will tell you if it's loaded. Select 'Campaign' and you'll be able to play Campaign 4.
Be aware also that Cam4 is notoriously buggy still. Mission 3 will probably refuse to load. If you get errors followed by a crash to desktop, post the contents of your log here. That way Milo can fix it.
I"m still having issues trying to get M4 to load. You've probably already got this problem figured out, Milo. I'll wait for your next update, I have a business venture I'm starting with a friend of mine, so I'll be pretty busy for the next several days or weeks getting it all set up.