Helicopter Attack botz v2.0 - v2.0

ROFL !!!, DO NOT try to run these bot files with the Original version of the map. ROFL !!! if you do, DO NOT EXPECT THESE BOTS TO PLAY THAT MAP !!!!! Maps having the same .bsp name does NOT mean compliance or that they will work with any map with the same .bsp name. Some map makers change the bsp file name for their map for each version of the map they create & others do NOT, they use the same .bsp name through all versions of their map including the final version.

Small problem with the map or the bots files (heli_attack_ets_custom_2) Once the Allies capture the flag, it remains inactive and the Axis stay in their base, going around in circles up top.

Did you see the script Credits banner when the map starts and then see the bot script Credits banner 15 seconds later? When the flag is held by the allies for 18 seconds the axis should fight until they die. Then, When axis die after the flag has disapeared they should spawn up top at the new battlefield area - top bunker. Not down in Helicopter area. Allies MUST build the contructable ladder. it is a trigger that kills all bots below at helicopter level. Allies will spawn at the constructable ladder or inside Axis top bunker. While the Allies are building the constructable ladder the axis bots will plant tripmines, call artillery and mount a planted MG42 at the axis top bunker in preparation of the allied attack on the bunker. When the constructable ladder is built, the axis will then also start to defend the door control box the allies must dynamite , Etc. The map has a kill trigger built into the map when the truck exits building with the gold. it Kills all bots inside. They all spawn outside on the new battle area. ( Long Road with 3 Truck Barriers ) & then Escort truck more and Escape.

20 bots trying to ride 1 elevator at exactly the same time is not good. They commit suicide \kill. These bots do not ride the helicopters. They would have to be restricted to 1 bot at the same time or they crush each other and die or jump out. Its a Alpha map and for playabilaty purposes, the Axis needed to be up top and ready to defend when Allies got the constructable ladder built and attacked the door control box. Which could only be accomplished by editing the maps script & adding a kill trigger below so Allies dont waste precious time trying to use the lift.

Technically the constructible ladder can be destroyed by an axis covertops satchel charge. Allies would then spawn down by helicopters. But axis can not get back up there to destroy the ladder unless a human Allied player destroys the bars on the doorway protecting the allied spawn area. The allied bots intentionally do not destroy it.

Yes, indeed, I noticed that once the flag is captured by the Allies, the bots are around the flag and remain inactive, even after several minutes, and the Axis bots are in their bunker above and are just going in circles.

Good, the bots are working correctly.

This is a incomplete & incorrect ALPHA map. The bot files were Made to work with a incorrect & incomplete map that would have remained unused because it is incomplete & not correct. I can look for the bot files where the axis stay down with helicopters & most bots are /killing until the allied engineer builds the constructible ladder and spawns change - ladder is a MAP trigger that changes the spawns. Humans & bots. I simply have axis change spawns early before allies build the ladder instead of waiting until after it is built when the allies change spawns.

The bot files do need time consuming tweaking - work. But if the map is not acceptable for public use, it's not worth the time. So I stopped working on them. Multiple pieces from this map were used to make the 3 heli_m series maps.

I could not change the allied spawn location like i did axis because allies spawn has a lock on it. Ladder is actually considered a commandpost in script & linked to command post inside bunker & other triggers & spawns. Axis spawn change was easy. Changing Allies, broke the map! When gold was secured & the truck exited the map crashed. It is the next spawn change. So the allied spawn was not altered.

Debug = 1, uses excessive resources to stream a bunch of information about completed objectives that have the Util.MapDebugPrint("Completed Objective"); in the script for their triggers. Debug should Never make the bot files work or Not work. It simply streams information. But from your description of the bots behavior and locations and the screenshots I know the bots are working perfectly correctly and as intended on the map. The bot files were made without ever setting debug to 1. Debug = 0, is how the bot files were created from beginning to end of creation. I didn't care about what debug would say, I was using Map trigger strings or I was Adding them to the MapScript then using them. /bot debugtriggers gives a tremendous amount of useful information for creating bot files. Debug = 1, not much help for creation. Good for troubleshooting if there is a problem. If the credit banners for the map script and bot script are displayed the bot files should be working/running correctly. But if they do not display then there is a problem.

Omnibot version 0.93