Mateos

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.

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

We can't use ent->s.number because Omni-bot runs it its own DLL and does not have access to internal data structures of the game.
You can use TraceLine function to get entity ID.
 

If there is at least one bot, then OnMapLoad is called immediately before OnBotJoin. If there are no bots, then OnMapLoad is called from BotUpdate. It depends on mod when it sends GAME_CLIENTCONNECTED event and when it calls BotUpdate function. Your gm map script should not depend on specific time when OnMapLoad is called. It can be one time frame earlier in silEnT.
The door lever is always moved at the beginning of the game. Your trigger function will be called only if it is registered by OnTrigger. The trigger is missed if OnTrigger is called after the lever has moved.
You can fix it by moving line OnTrigger( "rocdoor_lever1_Moving", Map.rocdoor_Moving ) to the end of OnMapLoad and insert sleep(1) before it.

Good evening,
I've just refreshed old waypoints I was asked for years ago for Missing in Action v1: Wolffiles.de - your filebase
The main objective is to pick up 3 MIAs being held in bamboo cages
It requires precise positioning and aiming (stance, as crouch, helps a lot, but isn't required)
When Allied bots have Axis enemies in sight, they'll do combat movement (but seem to keep the highly prioritized aiming, thus not engaging shooting, so that's fine to my mind), breaking that precision scripted in related path through navigation tables
Is it possible to disable CM like for ATTACK/CAMP/DEFEND spots through script?
Can it be re-enabled automatically upon exiting, or will it require an instruction in OnExit table?
Thanks in advance
Regards,
Mateos

I modified goal_mobilemortar.gm and commited it to SVN.
Position in front of the tank is GetEntityWorldSpace( GetGoal("MOVER_tank").GetEntity(), Vec3(0,250,0) )
 

Yes, you can disable combat movement in navigate and re-enable it in OnExit.
But I think it would be better to create RegionTrigger.DisableCombatMovement.

I decided to not rename the 0.8 folder because it would break everything for everybody. There are links to that 0.8 folder everywhere (on the wiki, forum or GitHub). We can't rename it now because it would cause a lot of trouble.

It's easy. Just add two use points. Bots will find the shortest path and automatically choose the best use point for them.
Console command saveusepoint (or sup) can be used to add use points. It creates a TXT file in omni-bot/et/user folder. Then you have to copy and paste it into OnMapLoad.
 

I did try & do RTCW version but I had a issue getting it to show up, I've just done a new test (just editing text) which did work.
For RTCW you need to edit mp_pak1.pk3\ui_mp\wm_quickmessageAlt & create a new pk3 in the same directories, its a little bit more hard work as 1 line in the ET menu you have to scroll down 50+ lines in the RTCW version. It looks like it can be done but its a lot of work
The DMS program was never designed to waypoint from it was rather to add waypoint flags without me having to remember exact command or which key bind it related to, it then progressed to adding goals without the need to open the console to manually type 3 or 4 commands for each one. After that I just added more bit that I found useful.
 
If you need there are some ET binds in here that should work fine in RTCW, I used the binds in combination with the DMS
http://svn.assembla.com/svn/omnibot/Enemy-Territory/0.8/tools/waypointing_configs/

Thank you very much!

I modified C++ code so that GetEntTeam works for spawns. It's in the mod. On Windows you need to compile qagame_mp_x86.dll from project GameInterfaces\ET\src\game\game_2013.vcxproj.
GetEntTeam is used in many map scripts, but it should not break anything because it is used only in region triggers which are triggered for CLASS.ANYPLAYER.

I will add possibility to set multiple navigation flags in the next Omni-bot version.

You've converted the waypoints successfully. Now you should create some goals.
Add a CAPPOINT goal at the ship so that Allies know where to take the documents Add three GRENADE goals to destroy barriers on the beach Enable MOUNTMG42 goals for Axis team Change priorities. CHECKPOINT_beach_flag should have the same priority as FLAG_War_Documents. Create routes.

Did you read the wiki ? The cappoint must be created by these commands when you are standing at the exit:
/bot goal_create cappoint transmitter /bot goal_save I attached gm script which disables PLANT_2transmitter7 goal so that engineers do not drop dynamite near the transmitter.
basor2light.gm