Something unusual

[the bindlestiff]

While fooling around with "thelighthouse" just now, I discovered that, as an Axis Engineer, I could blow the two entrances to the wall surrounding the lighthouse. But neither one changed the Goal Tracker.

I never could blow up an opposite team's objectives in all other maps that I've tried something like this. The dyno would go off but no damage would be done.

Is this unique to this map or maybe I just haven't tried this out on enough maps?

[Maleficus]

Is the action pointing to the correct info_obj entity number?

Its also possible its a map problem. Correctly made maps have info_obj entities targeting dynamite targets. If it wasn't done properly (Denny has mentioned a few maps like this), it won't be seen as a valid goal.

Never played or seen the map, so dont know for sure.

[the bindlestiff]

The two gate actions have the correct "trigger_objective_info" entity numbers. They are Allied objectives and the Goal Tracker works properly when they are dynamited by an Allied player.

It's just when a deranged Axis nut blows them up that the Goal Tracker is dumfounded. This is not something a bot would do, just a human with too much dynamite in his pocket!

It's just that I have never been able to blow up an opposing team's stuff before.

[CrapShoot]

I'd assume it's a map bug because it happens even when fritzbot isn't loaded.

[the bindlestiff]

Originally Posted by CrapShoot

I'd assume it's a map bug because it happens even when fritzbot isn't loaded.

Ahh, I didn't think to test it that way. It's just an oddity, not a problem, 'cause I can't think why a human player would want to destroy his team's defense that way. It'd serve him right to screw up the whole game due to confusing the goal tracker.

I just like to blow things up to see what happens!!

[Denny]

Originally Posted by Maleficus

If it wasn't done properly (Denny has mentioned a few maps like this), it won't be seen as a valid goal.

Yeah, that Sewer Lid on mp_carentan was one of them, thank god we we're able to remove it using the barrier removal code because the bots weren't liking it too much.

Although i've seen maps with Bindle's current oddity though too.