This I hate: blow something up too soon and the game dead ends.

Otter · #1 January 3rd, 2004, 04:07 AM

In campaign 1 I blew up the Mongol starbase while I was exploring the universe. Later, when it was a mission objective, well, it's already destroyed. Don't penalize me for being efficient! Then, campaign 3 I get to Perdition for the "scan" mission and after destroying all the Sitrak ships I **** back and wail on the unfinished artificial warp point. Sure enough, the day'm game says "hey, that baby's a big problem, go kill it." Well I did already but, oh no, the game pretends like it's still there.

FRUSTRATION INCREASING QUICKLY...MUST...PULLLLL...PLUGGGGGGGGG....AAAAAAG GGGGGGGGHHHHHHHH.

Phoenix-D · #2 January 3rd, 2004, 04:21 AM

Fixed (sorta) in the next patch, by making mission objects invulerable until you're assigned to kill them. That's kind of a weak way out, though.

Can be fixed otherwise, I think, by sneaky use of the event system.

EDIT: Yep. I'll try to get an unoffical fix for this up in the next couple of days. The event "Status No Enemy Ships In System" lets check to see if the target has been killed (you have to assign its enemy class a spaceobjectID number first), and if it has you can trigger the next event in the sequence.

[ January 03, 2004, 03:56: Message edited by: Phoenix-D ]

Phoenix-D · #3 January 3rd, 2004, 05:57 AM

Also, as a fix right now you can open main_jobs.txt, find the mission you're on, then open events.txt and find the event that enables the mission AFTER that event.

Then use the cheat `triggerevent (full mission name)` to bypass it manually.

[ January 03, 2004, 04:23: Message edited by: Phoenix-D ]

Otter · #4 January 3rd, 2004, 10:27 PM

After opening both files, that makes no sense. The event seems to be EVENT COMMANDER BENSEN 7 FINISH C.

Phoenix-D · #5 January 4th, 2004, 01:23 AM

Right, so now you start Starfury, load your save game and type this in then:

`triggerevent EVENT COMMANDER BENSEN 7 FINISH C'

After that you go to the same place you would if you finished the mission normally. IIRC the mission will still be listed in your mission screen though.

Otter · #6 January 11th, 2004, 07:37 PM

O.K. that works!

I did notice that if I stay in the screen where the object is missing, I'll get a mission expired message and then, shortly afterwards, the game will crash.

Maybe you should have code that checks if the object is still present. If not, give the player credit for having already whacked it or just skip over the mission.

Phoenix-D · #7 January 11th, 2004, 10:34 PM

I'm working on it. EDIT: on the solution for the original problem, that is. I'm a modder, not a coder.

MM is the only one that can fix the error you got, and I don't know that he would since its generated by using a cheat, and the next patch fixes the problem that required the cheat anyway.

The problem is that some of the event types listed in events.txt don't work, and some of them crash the game when used. And guess what? Those happened to be the events I needed.

I can work around it probably but haven't had the will to bother.

[ January 11, 2004, 20:35: Message edited by: Phoenix-D ]