palota

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.

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.

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.

SVN Assembla requires username and password, but it accepts anything (for example username: a, password: a).

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 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.

You can download Omni-bot 0.9 from GitHub. List of changes is in changelog.txt file inside the ZIP.