palota

You can set g_engineerChargeTime

You increased the range of the MORTAR goal. But you have to increase the range of the AMMOCAB goal which is only 1250.
AMMOCAB_main_ammocabinet = { CreateOnLoad = 0, GoalType = "AMMOCAB", Position = Vec3(1512.000, 939.000, 516.000), Range = 1250, TeamAvailability = 6, },  

The chosen botToKill is never an engineer because botToKill has goal FLAG, but engineer has goal PLANT.

foreach(g in Util.GoalTable("FLAGRETURN.*")) { Util.MapDebugPrint("Position " + g.GetPosition()); }  

It does not count dead players because dead players cannot carry anything. But you can get distance to a dropped object from a FLAGRETURN goal.
foreach(g in Util.GoalTable("FLAGRETURN.*")) { d = DistanceBetween(g, Vec3(-1824, 2115, 4)); Util.MapDebugPrint("Distance " + d); }  

for ( i = 0; i < 64; i += 1 ) { if ( EntityIsValid(i) && GetEntFlags(i, ENTFLAG.CARRYINGGOAL) ){ d = DistanceBetween(i, Vector3(-1824, 2115, 4)); Util.MapDebugPrint("Distance " + d); } }  

Here's my solution:  voilegarde_b3.gm

I uploaded new omnibot mod binaries for Windows 32bit to my Google drive.

I will increase MAX_MENUS from 64 to 128 in the next Omnibot mod version.

I uploaded new omnibot mod binaries for Windows 32bit to my Google drive.

I will increase MAX_MENUS from 64 to 128 in the next Omnibot mod version.

I have just moved commands stuckstart, stucknext, saveplayerpos, saveusepoint, warpanybot, warptogoaloffset, cleargoalflags  from et to global_scripts so that they can be used both in ET and RTCW.

It's a bug in the legacy mod since version 2.76. It happens on all maps with multiple MG42s. The same problem is on goldrush map. I created an issue on  Github.

Hi
Those commands were not coded into RTCW mod. I added them to GitHub now. They will be included in the next Omni-bot version.
Will you make any waypoints for RTCW ?

I have just moved commands stuckstart, stucknext, saveplayerpos, saveusepoint, warpanybot, warptogoaloffset, cleargoalflags  from et to global_scripts so that they can be used both in ET and RTCW.

It's a bug in the legacy mod since version 2.76. It happens on all maps with multiple MG42s. The same problem is on goldrush map. I created an issue on  Github.

I have just moved commands stuckstart, stucknext, saveplayerpos, saveusepoint, warpanybot, warptogoaloffset, cleargoalflags  from et to global_scripts so that they can be used both in ET and RTCW.

If you need to suspend mortar shooting for a specific goal, you can try to change Map.DontShootMortar to this.MapGoal.DontShootMortar.

I committed modified goal_mobilemortar.gm to SVN, so it's available to all.

The command dontshoot is used to disable attacking enemies. It does not work for scripted goals (mortar, grenade, airstrike).
You can modify line 72 in file goal_mobilemortar.gm:
if (!Map.DontShootMortar) { this.Bot.FireWeapon(); } Then set Map.DontShootMortar in planted/defused/destroyed triggers.

Hello Beer, thank you for giving me access to your Github project. I fixed the mg42 so that bots can use them and repair them.

Hello Beer, thank you for giving me access to your Github project. I fixed the mg42 so that bots can use them and repair them.

Only Beer knows why this is happening. He is the only one who can fix it. I can't do anything because I don't have Pub mod or cU engine. He refused to give them to me. I don't understand why he wants to keep his mods private.
s4ndmod is free and open source. Everybody can download it. It works with Omni-bot 0.90, if you update the version number and recompile it from source code.

I'll start with the bots not getting the flag
Without goals the bots will just wander around the map, the issue here is that the CHECKPOINT goal (the flag) is not been detected, this is why the bots were not going for the flag.

To see what the bots goals are type
/bot sag into the console, on this map there are only EXPLODE & PLANT goals, this showed that there was not a goal for either flag.
I'm not that familiar with RTCW so I'm not sure if this a omnibot or a map issue & manually creating it does not work. I've done a work around by creating 2 ATTACK goals at the flags.
At this stage the bots just run around to the 2 flags.
(I've PM'ed you the new code)
The dynamite problem
 
The main issue I see is that you have only put BLOCKWALL onto 2 waypoints but you have many more connections that go through the gate(s), the bots are trying to plant but can't get past the gate, every waypoint that has a connection going through a gate or a blowable wall must have the BLOCKWALL flag. Start with that & see how it goes.
 

 

I added MP34.
Other weapons don't need to be handled in et_weapontables.gm because they have the same ID as original weapons.