Search the Community

Hi guys. I’m looking at some tracker issues in the hope of providing some useful patches to grayman and greebo. For this one I could do with advice from mappers who've used objectives in plenty of ways I've never thought of! Should a target_setobjective_amount give the mapper any control other than the new "amount" requirement? The other objective-affecting targets (addobjectives, setobjective_state, setobjective_visibility, setobjective_component_state) don't have extra spawnargs to let the mapper control whether there's a HUD message or anything else. The one exception is setobjective_state which lets you add an "unlatch_irreversible_objectives" spawnarg so you can choose whether to undo irreversible objectives. Would a target_setobjective_amount need any? I guess "unlatch_irreversible_objectives" is relevant to this one too, as the default behaviour should probably be: undo a completed objective if the required amount gets raised above what the player has achieved, except if it's an irreversible objective. The lazy way to go about this kind of thing is to add a dozen spawnargs/options so every mapper has to look them up and answer the questions for themselves, but it'd be better to take the cue from the existing targets and implement just the most useful behaviour instead. Any thoughts on how it should work?