ET Finding stuckage

Waypointing

Finding stuckage

Intro

In 0.81 a new feature for logging stuckage was added. This means that the burden of finding stuckages has been transferred to the bots. Waypointers no longer need to test for hours or rely on feedback from the community for stuckage reports.

Instructions

Locate the goal_checkstuck.gm file

    ~/omni-bot/et/scripts/goals/goal_checkstuck.gm 

If logging is switched off (false), you need to turn logging on by editing line 6 to say true.

    this.LogStuckage = true;

If you are running a public server you should set this to false as it may cause tiny bits of lag & can create large log files.

Collecting data

All that is needed is for you to run the map with bots when a bot becomes stuck for more then the default 5 seconds it will selfkill & will log its location.

Run with bots for as short or as long as you want, the longer is better as the bots will find more stuckage.

Setup

Once you are happy that you have run your map for long enough you need to go to your ~/omni-bot/et/user/ folder. In this folder you will find a new file called <mapname>_stuckages.gm (<mapname> will be the name of your map i.e. oasis_stuckages.gm).

Now just copy your new file to ~/omni-bot/et/scripts

Commands

For this to work you need to enable cheats using /devmap mapname or enable via the cheats section in the DMS

Turn your waypoints on as normal & open the console

To go to the 1st stuckage point type this

    /bot stuckstart 

This executes the script which populates a table of stuckage vectors. and then warps you to the first one.

    /bot stucknext 

This will warp you to the next in the list, type this again to continue on through the list of stuckages.

Finish

Once you have fixed the stuckages delete the <mapname>_stuckages.gm file.

If you want to check for more stuckages just repeat the process.