Problem with Objectives Satisfied at Start

[grayman]

I assume that any visible objectives marked "Satisfied at start" would show up as checked on the objectives screen when starting a map.

 

Is this not the case? I'm not seeing checkmarks.

 

Thanks.

Edited August 19, 2010 by grayman

[Fidcal]

I don't know. I can't find anything on this. It seems to be the same as 'Complete' except that is for the whole objective while 'satisfied at start' is for just one component (ie, could be more than one component in the object.) But I don't think it is that because I see it used on 'don't kill' objectives. But they have 'ongoing' to prevent those completing immediately. I'd need to test a 'don't kill' without it to see what happens.

 

I think I might have known this at one time but it does not seem to be documented.

[grayman]

I thought about it a bit more, and--though it's misleading--I think it only applies to NEGATIVE objectives. Don't kill, don't alert, etc. At the start, you haven't killed anybody, and you haven't alerted anybody, so those kinds of objectives should be marked "Satisfied at start". The more general interpretation--an objective is satisfied (which is how I read it)--is ignored for POSITIVE objectives.

 

I was trying to use this for forcing satisfied objectives near the end of a map w/o having to start at the beginning each test run. What I decided to do instead was to create a temporary entity (I forget what it's called) to mark objectives "satisfied", and trigger it at the start of the test run. Remove it for the final release.

Edited August 20, 2010 by grayman

[Fidcal]

Yes, I see that but as I said, negative objectives also have 'ongoing' which seems to do the same thing.

 

If you are trying to complete objectives by trigger then just use a set state entity; look in targets, I forget the exact name.