...The hell?!?

Okay, so, I have a gövt (188):

Class: 130, -1, -1, -1
Ally: 190, 130, -1, -1
Enemies: -1, -1, -1, -1

I have a mission that says "Go to Ally of Govt": 188

So why does it select a planet of gövt 154 with:

Class: 1, 55, -1, -1
Ally: 0, 1, 6, 55
Enemy: 2, 3, -1, -1

...as its destination?

Are you getting any "can't find non-transient spöb" errors in your debuglog.txt file?

At one time I tried to convert all of the Nova delivery missions to use allies and classmates instead of random spöbs. All I ever got was weird BS like you've just encountered or else I would get the non-transient error. I submitted this as a bug via the BugFest topic (you'll have to search to find it, I don't have the URL handy). As a matter of fact, I queried you about this some time back over on the EV-Nova.net forum. Basically it boils down to the fact that if ANY s˙st in the ally or classmate category (and probably enemies as well) has a Visibility changeover, then the game-engine just refuses to give you any sensible TravelStel or ReturnStel. This is another case of a documented feature not being used in the default Nova scenario, so it wasn't ever verified to have worked in the first place. I've given up trying to use ally and classmate destinations.

This post has been edited by Arturo : 09 September 2005 - 10:01 PM

Suck.

Actually, I think we tried to use it, it fell over, and we ran out of time to fix it... so we avoided it by not using it. Now that Nova doesn't use it any more, it's not on the priority horizon to fix.

I'll raise it with Matt again.

Dave @ ATMOS

That's be greatly appreciated.

Does this only affect missions that use the class property? I'm doing Retribution work right now, and I'm not sure whether the reinforcements jammer outfit type was used in the stock scenario (I know the Aurorans had a Fed and Moash IFF jammer). The reinforcements jammer also makes use of the class field, so I wanted to see if anyone could confirm the functionality/nonfunctionality of this type of outfit.

As promised, I've passed this on to Matt. He'll be looking at the problem (no guarantee of a fix) after the weekend.

Thanks, Pipe.