Mateos

The bot does not stand exactly at the center of the goal. The distance from the goal to the wall is less than 64, but the distance from the bot to the wall is greater than 64.
I fixed the problem now and commited it to the SVN.

Priorities of ROUTE goals were ignored. It will be fixed in the next Omni-bot version, or you can build it now from GitHub.
The 1944_nordwind map automatically changes spawns just after a player joins the game, so you have to add yield() before ChangeSpawnPoint.
 

TraceLine does not hit anything at the beginning of the game because the construction materials are not there until the path is destroyed.
But you can set entity name instead of trace:
/bot goal_setproperty entityname axispath1_toi  

You have to use paththrough navigation. Then in the navigate function you can stop the bot:
this.Goto(this.Bot.GetPosition());  

Engineers don't fire garand grenades when they are going to PLANT goals. Do you need to disable it for BUILD goals too ? Maybe I could add a new optional property to the BUILD goal which would be used for objectives that need a lot of charge.
If you want to disable grenades in some narrow corridors, you can create a region trigger and use function ETUtil.DisableRifleNade.
Function WeaponTable.SetWeaponAvailability can be used to set weapons for team/class, but it's not possible to set a weapon for a role.
If you want to change weapons manually in triggers, you should set Map.DontSelectWeapons=true. That will solve the problem of spawn self killing, but it completely disables weapon selection globally for all bots.

The trigger distance is not from the target goal, but from a grenade. If somebody is standing just beside a bot, then his thrown grenade immediately enters the radius. It would be necessary to calculate trajectory of a grenade and predict coordinates of explosion. Maybe I could use some code from the mortar goal.
I agree with your other suggestions and I added them to my to-do list.

I updated goal_rolemanager.gm now so that you can use AllBots=true to assign all other bots to that role:
Roles = { ALLIES = { AllBots = true, DEFENDER1 = { numbots = 2, }, DEFENDER2 = { numbots = 2, AllBots = true, }, }, },  

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, },  

Here's my solution:  voilegarde_b3.gm

voilegarde_b3.gm

That's my solution. Not the cleanest solution but from my testing it works. For checking if the doors are opening and eventually opened I use "rightlabdoor_button_Moving". 
Check Right_Lab_Door_Moving2 to see what I did there.
 
 

1st test with new binaries looking good thanks
Just need to get the rest of the DMS working



 

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.

It's about 93% done

1% tweaks / code clean up
1% cheat menu minor fix's (getting sv_cheats within the game was a challenge, but got working)

5% is the goal/target/waypoint etc naming.

This last 5% is where I can't go any further.
I can see the new coding in cg_main.c, I just don't have the understanding of c++ to compile this for testing.

I have managed to get a text box to work but I have no idea if what I've done will work for naming the goals etc.
I know there is a issue with the text not clearing after pressing ok, i'm unsure why this is.


This last bit is where I'm stuck
 
Is it possible for someone could check my coding to see if this would work & if possible compile the code to test this.
The code is over 10,000 lines so it's not possible to post in the forum, I could upload into the ET repo on Assembla if thats ok or is there another option (never used github).
If someone could let me know on here or via PM please

Here's a few pictures of the DMS for you to see:

You can remove these in OnMapLoad and manually recreate them in-game through the console, using /bot goal_setproperty for all custom required properties

Some "may" know / remember me as BubbaG1 - would have used that as my display name but assumed I would add that later.  Silly me!
I was with the **DRC** (Das Rebellion Clan) for Enemy Territory and helped with waypointing / scripting for a hot minute.  A few of us are playing ETL so figured I would help again, where I can.  Will have to get back up-to-speed on what is possible.
Great to see this crew is still around and enjoying the games.
I am an old phart that primarily does web development / IT now for a company based in Stuttgart, Germany though I am located in Central USA.

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.

If you don't script any restriction, it's the same for all bots

First problem: https://mygamingtalk.com/wiki/Paththrough_UseSwitch
Other problem: You'll probably have 2 CAPPOINT goals, just have 1 enabled for Axis and 1 for Allies

Waypoint Commands - MyGamingTalk

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.