[cod2]jm_kuwehr (is finished!)

[Drofder2004]

The only current limitation is that this would only work with "area" based waypoints. Which although is fine, some maps would work well with "object" (trigger_use) waypoints, but I think for a 'addon' to maps, this will be sufficient.

For now, it will be in archive, if Treyarch ever do allow for custom maps and a fairly good amount of custom modding, I will consider it for CJ Mod. At the moment, I am in no mood to start adding this on.

But a list of potential features:
- Custom waypoints [as above]
- Waypoint indicators [Kuwehr]
- Personal arrow guide [mp_waypoint]

[Rezil]

The only current limitation is that this would only work with "area" based waypoints. Which although is fine, some maps would work well with "object" (trigger_use) waypoints, but I think for a 'addon' to maps, this will be sufficient.

Hm, which maps in particular would work better using a trigger_use? It's entirely possible to insert(or at the very least, simulate) a trigger_use_touch into a map or any trigger for that matter.

[Drofder2004]

The only current limitation is that this would only work with "area" based waypoints. Which although is fine, some maps would work well with "object" (trigger_use) waypoints, but I think for a 'addon' to maps, this will be sufficient.

Hm, which maps in particular would work better using a trigger_use? It's entirely possible to insert(or at the very least, simulate) a trigger_use_touch into a map or any trigger for that matter.

Any with objectives or collectables, such as your own and a few of Nightmares mainly. Granted sometimes, you don't want the object to be marked on a map, but its a possibility. Also, it opens the door and gives a little push for those creating maps to be more creative.

I do not mean, insert a trigger, I mean detect. This can be achieved by adding structured information to a waypoint. Such as

waypoint[5] = SpawnStruct();
waypoint[5].type = "use";

And then parsing the extra info, instead of "reaching" a waypoint, a specific entity is triggered.
Through a little bit of notify/waittill behaviour, or a modification in the script, it is most definitly possible.

The idea can be further expanded for maps with two modes, or more challenging routes.
allowing for a different route to be taken, without breaking the order of waypoints.
Such as:
waypoint[5].hard = "<origin>";
waypoint[5].easy = "<origin>";

[XeloX]

if ONLY this was for cod4, looks friggin amazing.