Forums

files fixed, waiting for feedback..

https://www.dropbox.com/scl/fi/o7e740lc5qr5ursxv5tdv/drempuzzo_xmas_final.zip?rlkey=glrt6et94qdzqzrkhxgno8458&dl=0 There is this one but for Xmas...  I found this on Fearless assassins (capuzzo.zip) Capuzzo Waypoints 1.0.0 By BlackWolf Find their other files   About This File Fixed waypoints for Capuzzo.   Fixed issue with bots not building CP. Fixed issue with bots not completing final obj. Fixed issue with Axis bots not stopping transmission of message.   These are NOT final waypoints, but will work OK. capuzzo.zip

Ok i try another bot file. Need to search for bot file which is for _final. Those arent. Did change file names but seems not work then

from claude.ai:   The definitive test is to check whether the bots move on other maps on the same server. If they remain stationary everywhere, the issue lies with the Omni-bot installation within Nitmod. Either the Omni-bot version is incompatible with your Nitmod version, or Omni-bot isn't loading at all; the startup console log will show this. If they are stationary only on Capuzzo, Nitmod isn't the cause. The most likely explanation is that your files aren't in the correct `nav` folder. On a server with multiple Omni-bot installations (for example, the one included with ET:Legacy in the `legacy` folder versus a separate one), the files must be located in the `nav` folder of the specific installation Nitmod is actually loading. This path is specified by the `omnibot_path` cvar. To check both scenarios, type `omnibot_path` into the server console. Then, observe what the log displays when Capuzzo loads: either "2238 Waypoints Loaded from file..." or "Waypoint capuzzo.way not found." If you send me those lines, I can draw a conclusion.

According to claude.ai: Bugs in capuzzo.gm... These bugs don't explain why the bots are stationary, but they do need fixing: Line 1499: `MapRoutes.ATTACK_Barrier_1_1 = MapRoutes.PLANT_Tank_Barrier_2;` overwrites the route defined on line 1492. It should likely be `ATTACK_Barrier_2_1` instead. Lines 179–180, 211–212, 316–317, and 641–643: "ESCORT_tank" and "MOUNT_tank" are written in lowercase, whereas the goals are named `ESCORT_Tank` and `MOUNT_Tank_Allied` / `MOUNT_Tank_Axis`. If the lookup is case-sensitive, these user limits have no effect. I haven't verified this in the code. In the `ESCORT_Tank` and `PLANT_Tank_Barrier_1` routes: the key `ROUTE_F15_1` is defined twice in the same table, so the second one replaces the first. Probable causes to check on the server BSP name. Omni-bot officially provides waypoints for `capuzzo_b1`, whereas the final version, "Capuzzo Airport," uses the BSP name `capuzzo`. Your .pk3 file must contain the exact path `maps/capuzzo.bsp`. If it is `capuzzo_b1` or another variant, your files will not load. (i verified: capuzzo.bsp correct) File names and location. Linux is case-sensitive: the files must be named exactly `capuzzo.way`, `capuzzo.gm`, and `capuzzo_goals.gm` and located in the `omni-bot/et/nav` folder. The files must be placed directly in that folder or at the root of a .zip archive, not inside a subfolder. Map version. Your waypoints were created in 2018 for a specific version of Capuzzo. If your server is running a different version with different terrain, the bots will be unable to find a path and will remain stuck. How to determine the cause Check the console log when the map loads. If the .way file cannot be found, Omni-bot logs a message like `Waypoint capuzzo.way not found in file or archives`. If it is found, the log will indicate `2238 Waypoints Loaded from file…`. Enable script debugging. Add `Debug = true` to the global `Map = {` table at the top of `capuzzo.gm`. The line `Omni-bot map script for capuzzo executed.` should then appear. If the waypoints load but this line is missing, the script is crashing during the loading process.