Feature #947

Increase amount of trigger_objective_info

Added by keMoN over 2 years ago. Updated 7 months ago.

Status:New% Done:


Priority:NormalSpent time:-
Category:Mod generic
Target version:2.78
OS: Arch:


Currently there is a limit of 18 trigger objective_info per map.
You need one for every objective, constructible, destructible,... Basically for anything that has a track ("You are near ... ") or that has an icon in the command map.
There is a reason why maps in ET are basically always the same, because it is incredibly easy to run into this limit. Is there a reason why this limit is in the code or is it just random?

For example at the bottom of this page is Fueldump with 14 *ToI*s in the standard version.
Then there is a version with spawns in both of the CP locations and for both teams, which is an additional 4 ToIs and we are already at the set limit.
Now imagine if a mapper wated to make a version where the river isn’t frozen, the tunnel grate is filled with water and there is a water pump in the tunnel bunnker that will drain the tunnel grate, we would need another one. The more a mapper wants to get creative (not necessarily good) the faster he runs into trouble and has to do the same old shit that has been done for more than a decade now.

Interesting read on the subject is the readme of Baserace beta3


#1 Updated by Spyhawk over 2 years ago

  • Category set to Mod generic
  • Target version set to 2.76

I don’t see any reason the MAX_OID_TRIGGERS value could not be increased, apart from the fact that the map would obviously be compatible with Legacy mod only.

#2 Updated by IR4T4 about 2 years ago

There are some good reasons beside loosing compatibility: The configstring, team info and some other related data will grow each objective!

#3 Updated by IR4T4 about 2 years ago

  • Target version changed from 2.76 to Behind 2.60b / protocol 84

#4 Updated by IR4T4 7 months ago

  • Target version changed from Behind 2.60b / protocol 84 to 2.78

Also available in: Atom PDF