.:: Bots United ::. - View Single Post

the bindlestiff · **Re: Route System -** 10-08-2007

Tiger:

I spotted a few things right away:

1. The target for your route is a CAMP. In RtCW, the only actions that can be routed to are dynamite, steal, and deliver actions (as I reminded you in my previous posting).

2. The team for your route is ALLIED, but the target is AXIS. This won't work, either.

3. The route is not placed in an optimum area for the bots to recognize it. Routes must be located in areas where the bots are selecting new goals for themselves, usually at SPAWN POINTS or at a STEAL location.

Remember, if you route to a dynamite action, only engineer bots will follow the route since a dynamite action only applies to engineers. OTH, if you route to a steal action, all the bots will follow it. And if you place a route at the steal point leading to a deliver point, only the bot who takes the item will observe the route.

Another point to be aware of: I assume that your working nav and aiscript files are located in the appropriate folders under the /fritzbot folder. You are re-doing an existing set of waypoints and those waypoints are stored in Fritz2.pk3 along with all the other map waypoints. BE AWARE that files encased in a pk3 supersede files in the external folders. IF you leave the Fritz2.pk3 in the /fritzbot folder while you're working on your new waypoints, every time you do a map_restart, it'll bring up the pk3 waypoints, NOT those you want to work on!

The reason I think that this may be the case is because you haven't mentioned the big gate that can only be opened by a wall lever. Bots cannot operate levers, so the gate was removed in a modification to the map script. If the gate hasn't appeared during your waypointing, then it's clear that the modified script (also located in the pk3 along with the nav and aiscript files) is in effect.

When you temporarily remove Fritz2.pk3 from the /fritzbot folder, you'll need to open it up, locate mp_base.script in the /Maps folder and copy it to the external /fritzbot/Maps folder in order to have the gate removed. I hope that this is clear.

I hope this solves your problem!

	(#7)
the bindlestiff Member Status: Offline Posts: 280 Join Date: Nov 2005 Location: Washington state	Re: Route System - 10-08-2007 Tiger: I spotted a few things right away: 1. The target for your route is a CAMP. In RtCW, the only actions that can be routed to are dynamite, steal, and deliver actions (as I reminded you in my previous posting). 2. The team for your route is ALLIED, but the target is AXIS. This won't work, either. 3. The route is not placed in an optimum area for the bots to recognize it. Routes must be located in areas where the bots are selecting new goals for themselves, usually at SPAWN POINTS or at a STEAL location. Remember, if you route to a dynamite action, only engineer bots will follow the route since a dynamite action only applies to engineers. OTH, if you route to a steal action, all the bots will follow it. And if you place a route at the steal point leading to a deliver point, only the bot who takes the item will observe the route. Another point to be aware of: I assume that your working nav and aiscript files are located in the appropriate folders under the /fritzbot folder. You are re-doing an existing set of waypoints and those waypoints are stored in Fritz2.pk3 along with all the other map waypoints. BE AWARE that files encased in a pk3 supersede files in the external folders. IF you leave the Fritz2.pk3 in the /fritzbot folder while you're working on your new waypoints, every time you do a map_restart, it'll bring up the pk3 waypoints, NOT those you want to work on! The reason I think that this may be the case is because you haven't mentioned the big gate that can only be opened by a wall lever. Bots cannot operate levers, so the gate was removed in a modification to the map script. If the gate hasn't appeared during your waypointing, then it's clear that the modified script (also located in the pk3 along with the nav and aiscript files) is in effect. When you temporarily remove Fritz2.pk3 from the /fritzbot folder, you'll need to open it up, locate mp_base.script in the /Maps folder and copy it to the external /fritzbot/Maps folder in order to have the gate removed. I hope that this is clear. I hope this solves your problem!