palota

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.

This project has been inactive for 10 years. Are developers still alive ? The problem is that there are many bugs in silEnT mod. Nobody can fix the bugs if the source code is not available.

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.

This is not a goal. It's a paththrough navigation. It is executed when a bot goes through that waypoint. Bots visit that location because there is DEFEND goal. If you want to change priority or make it class specific, you can set it on the DEFEND goal.

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.

Good morning,

Which map is it ? Does the target entity have health information which could be used to calculate exact amount of grenades needed to destroy it ?

We can't ignore EVENT.ENT_ENTER_RADIUS if distance is greater than AvoidRadius. If a bots is moving towards a grenade or a grenade is moving towards a bot, then the event is triggered once at distance 400.

If you want bots to go to ammo cabinets, you can change priority:

global OnBotJoin = function( bot )
{
	wpn = bot.GetWeapon(WEAPON.ALLY_GRENADE);
	if(wpn)
	{
		wpn.PrimaryFire.LowAmmoPriority = 0.82;
	}
};

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

That wiki page was written 20 years ago. Maybe DrEvil did it.

Why don't you use the PrintScreen key or Snipping tool to make screenshots ?

There must not be "=" in server.cfg. You have to delete = after set omnibot_path.

It would be too slow to search waypoints network every second for every bot. You can set a role for the goal and then assign the role to bots in triggers.

0x1005a is number 90 converted to hexadecimal.

You can use command /entitylist which prints all entities and their script names and target names. GetEntityByName searches target names.

Where can we download pk3 file of this map ?

Where can we download pk3 file of this map ?

You should never use entity numbers because they depend on mods. You should use GetEntityByName instead of GetGameEntityFromId. If the entity does not have any name, then you can use TraceLine.

Functions GetEntityByName and GetGameEntityFromId return null if the entity is invalid. Correct condition is:

if(ent1)
{
	print("Entity is valid");
}

You must not use GetEntTeam in OnExit because it returns null if a player disconnected. Players can also change team when they are inside the region. See wiki how to count players in a region.

You cannot query the current stamina.

On 12/14/2024 at 5:06 PM, vargatom said:

When I follow a BOT in spectator mode and BOT sprints why doesn't show that his stamina is running out?

This is not related to bots. The same problem happens if you watch human players. There are a lot of bugs in the omnibot mod because it is based on the original game from year 2001. The spectator stamina is displayed correctly in newer mods (legacy, nitmod, noquarter, silent). It does not work in jaymod and etpub.

gm scripts are case-sensitive. There must be Goto, not GoTo.

Why didn't you copy the function from this page and paste it into your script (Ctrl+C, Ctrl+V) ?

The end of EvalFunc }, should be on line 79 after return, not on line 86.

Hi, welcome to the Omni-bot forum.

If you have scripted a lot, where are your scripts ? Could you please share a link to your scripts and waypoints ?

Util.EnableGoal and Util.DisableGoal can be used to activate ROUTE nodes. You can do this in a while loop in a thread.

	Navigation =
	{
		stop =
		{
			EvalFunc = function()
			{
				return !this.StopTime || GetTime()-this.StopTime > 2;
			},
			navigate = function()
			{
				this.Goto(this.Bot.GetPosition());
				sleep(3);
				this.StopTime = GetTime();
			},
		},
	},

Use Paththrough Navigation

Navigation =
{
	stop =
	{
		navigate = function()
		{
			this.Goto(this.Bot.GetPosition());
			sleep(3);
		},
	},
},

/bot waypoint_setproperty paththrough Navigation_PT:stop

After the wp_check command you can use commands /bot wt DUPE1; /bot wt DUPE2 etc.

You can use INFILTRATOR role for goals that are available only for disguised covertops.

You can use detonatespot property for a place to trigger the explosion.

It is intended. It's written on the wiki: Any goal that has a role defined will be ignored by bots that do not have the same role defined.

If you have goals with a role available for both teams, then you have to assign that role to both teams. Or you can duplicate the goals and have one goal for Axis and the second goal for Allies.