Jump to content

palota

Moderators
  • Posts

    115
  • Joined

  • Last visited

  • Days Won

    71

Everything posted by palota

  1. Do you have the last version of both Omni-bot library (omnibot_et.dll) and the mod (cgame_mp_x86.dll) ? \gamedate "gamedate" is: "Jun 14 2024" \bot version Omni-Bot : Jun 26 2024 17:00:59 Version : 0.91 Interface # : 17
  2. Look into the console. Are there any error messages ?
  3. 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, },
  4. The chosen botToKill is never an engineer because botToKill has goal FLAG, but engineer has goal PLANT.
  5. GetReinforceTime() is needed to kill a bot just before respawn, so that the bot is actually not dead. I've already done it and committed it to SVN repository.
  6. First of all bots should wait for respawn. You can use function bot.GetReinforceTime() and sleep until 1 second before respawn. Then you should check if the book is at its original location and nobody is carrying it. Then you kill bots that have bot.GetMapGoalName()=="FLAG_book".
  7. Which map is it ? Why do you want to kill bots ?
  8. foreach(g in Util.GoalTable("FLAGRETURN.*")) { Util.MapDebugPrint("Position " + g.GetPosition()); }
  9. 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); }
  10. 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); } }
  11. There is not delay between map trigger and OB script trigger. There's delay between map triggers "rightlabdoor_button_Moving" and "rightlabdoor_goto".
  12. I uploaded new omnibot mod binaries for Windows 32bit to my Google drive.
  13. I will increase MAX_MENUS from 64 to 128 in the next Omnibot mod version.
  14. The problem is that the file is very long and there are too many menus. Only 35 menus work. Others are ignored. Which version of RTCW do you have ? I use iortcw-1.51c.
  15. I tried it, but I can't open menus after Goal Options.
  16. It's ok to upload it to the Assembla. Can you create a new RTCW folder in the repository root ?
  17. 32bit version is only required for mods (SilEnT, n!tmod, Jaymod, NoQuarter, ...). But if you want to make waypoints, it is much easier to install 64bit ET:Legacy, because it does not depend on any packages or libraries. The 64bit ET:Legacy works on many 64bit Linux distros. I tested it on Ubuntu and Debian. Your et_powescape waypoints are for old Omni-bot 0.8. You should update Omni-bot to version 0.9.
  18. 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.
  19. 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.
  20. 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 ?
  21. If you need to suspend mortar shooting for a specific goal, you can try to change Map.DontShootMortar to this.MapGoal.DontShootMortar.
  22. I committed modified goal_mobilemortar.gm to SVN, so it's available to all.
  23. 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.
×
×
  • Create New...