Leaderboard

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.

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:

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.

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

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.

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.

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.

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 set g_engineerChargeTime

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

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.

Need to find time to play ET with my buddies first and then BF5 / Warzone

Welcome to MyGamingTalk. Please feel free to browse around and get to know the others. If you have any questions please don't hesitate to ask.

Hi I'm just looking at the map mp_ruiner (RTCW) & a lot of the automatically detected goals have a '!' at the end. This causes the following parse error in the goals file. error (232) parse error, expecting `'}'' or `','' Could not parse file nav/mp_ruiner_goals.gm Line 232 FLAG_Ruiners_head! = { CreateOnLoad = 0, GoalType = "Flag", Position = Vec3(1088.000, 4200.000, 208.000), TagName = "Ruiners head!", TeamAvailability = 4, }, I can fix the parse error by deleting the ! but it still shows as the original goalname in game & if I save the goals, it just creates a new goal with the original name. Same issue if I rename the goal in game as well --------------ALLIES-------------- ALLIES: FLAG_Ruiners_head! - 0.8 Just wondering if there is a way to fix this? It also causes a parse error in the script file made by "makemapgm" but that is easy fixable by removing the '!'

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

Hi I'm trying to create a version of the DMS for RTCW but I can't work out how to add a text box for naming the goals waypoints & groups The ET version uses setGoalName setGroupName setWaypointName I don't even know if the above commands are coded into omnibot RTCW system life they are in ET, cs helped me with this section in the ET version so I'm not sure if this was already in the code or added. I have a working beta version of the menu so the rest I can do, it's the text box that I can't do. Is this something that can be done?

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.

Welcome to MyGamingTalk. Please feel free to browse around and get to know the others. If you have any questions please don't hesitate to ask.

I'm just helping someone out at the minute, trying to teach a few things without taking over. Getting the DMS to a workable state is my 1st task before getting into the waypointing. I have been doing a bit. I noticed that stuckstart / stucknext are missing from the Commands in RTCW, appears to work fine when I added the code from et_commands.gm into rtcw_commands.gm, I only have assembla/et access, so I can't update any RTCW files. A few corrections to do due to the ET/RTCW differences, but the menu is working & taking shape.

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 ?

For the Axis I would use a Switch goal just to shut the gate & set the paththough waypoints to allies only as an option. This can be looked at another time. If you update the waypoints / script I can have a look & see what is wrong. I learnt by asking questions (a lot of questions) so if there is something you need to know & I (or someone else) has the time I/we can try & answer. Some of your questions on MapScripts might be answered here

Managed to do a fix on mp_base faster than I expected, it's set for all bots just to open the gate if it's closed. I don't know the map well enough to know if the axis would want to shut the gate but that would work better with a switch goal activated by the gate opening trigger rather than paththrough.

Ignore the bit about looking at mp_base, I wrongly assumed that there was a paththrough on the map (will see about fixing it) Look at the 110_factory script I know this uses Paththrough UseSwitch as I did it. Note that there is no blockwall flag as this would stop the bots using this path.

If you look at the ET map "mp_base" this has the same gate & looks to be based on this map (with an Alien instead???). Ignore / remove "LimitClass = (1<<CLASS.COVERTOPS)," in the script, as that's an ET thing This will give you the base to study If you just want the allies to open & the axis to close you could just use 2 switch goals but you might find the bots fighting over the opening & shutting the gate all map, or just the allies opening the gate may work better? These this would need to be enabled/disabled in the script to stop them just opening/shutting the gate. You need to disable some of the goals you have created for Teams, Normally I disable all the goals 1st Util.DisableGoal( ".*", true ); Then enable the goals you want the Teams to use SetAvailableMapGoals( TEAM.AXIS, true, "DEFEND_.*" ); SetAvailableMapGoals( TEAM.AXIS, true, "FLAG_Blue_Flag"); SetAvailableMapGoals( TEAM.AXIS, true, "CAPPOINT_Blue_Flag"); SetAvailableMapGoals( TEAM.ALLIES, true, "ATTACK_.*" ); SetAvailableMapGoals( TEAM.ALLIES, true, "FLAG_Red_Flag"); SetAvailableMapGoals( TEAM.ALLIES, true, "CAPPOINT_Red_Flag"); You will need to create the 2 CAPPOINT goals where the flags are to be taken. The ROUTE goal is just used to define more than 1 route as a goal from a location i.e. the spawn to flag_goal rather than taking the shortest path (Routing)

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

For Android app development, the cost of a final product depends on various app elements and the type of app that matches your business requirements. On an average, cost of Android app ranges between $15,000 to $40,000 with an hourly rate of $15-$25.

Updated. server_api.zip

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