https://mygamingtalk.com/wiki/index.php?action=history&feed=atom&title=ET_Finding_stuckageET Finding stuckage - Revision history2026-04-09T21:16:42ZRevision history for this page on the wikiMediaWiki 1.41.1https://mygamingtalk.com/wiki/index.php?title=ET_Finding_stuckage&diff=1403&oldid=prevPalota: 1 revision imported2023-02-13T07:02:31Z<p>1 revision imported</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<tr class="diff-title" lang="en">
<td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 07:02, 13 February 2023</td>
</tr><tr><td colspan="2" class="diff-notice" lang="en"><div class="mw-diff-empty">(No difference)</div>
</td></tr></table>Palotahttps://mygamingtalk.com/wiki/index.php?title=ET_Finding_stuckage&diff=1402&oldid=prevPalota: 1 revision imported2021-07-13T19:05:46Z<p>1 revision imported</p>
<p><b>New page</b></p><div>{{process header<br />
| title = Finding stuckage<br />
| section =<br />
| previous = [[Template:Basewaypointing | Waypointing]]<br />
| next = <br />
| shortcut =<br />
| notes =<br />
}}<br />
{{TOCright}}<br />
<br />
== Intro ==<br />
<br />
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.<br />
<br />
<br />
== Instructions ==<br />
<br />
Locate the goal_checkstuck.gm file<br />
<br />
<br />
~/omni-bot/et/scripts/goals/goal_checkstuck.gm <br />
<br />
<br />
If logging is switched off (false), you need to turn logging on by editing line 6 to say true.<br />
<br />
<br />
this.LogStuckage = true;<br />
<br />
<br />
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.<br />
<br />
== Collecting data ==<br />
<br />
<br />
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.<br />
<br />
<br />
Run with bots for as short or as long as you want, the longer is better as the bots will find more stuckage.<br />
<br />
<br />
== Setup ==<br />
<br />
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'').<br />
<br />
<br />
Now just copy your new file to ''~/omni-bot/et/scripts''<br />
<br />
<br />
== Commands ==<br />
<br />
<br />
For this to work you need to enable cheats using /devmap mapname or enable via the cheats section in the [[DMS | DMS]]<br />
<br />
<br />
Turn your waypoints on as normal & open the console<br />
<br />
<br />
To go to the 1st stuckage point type this<br />
<br />
/bot stuckstart <br />
<br />
This executes the script which populates a table of stuckage vectors. and then warps you to the first one.<br />
<br />
/bot stucknext <br />
<br />
This will warp you to the next in the list, type this again to continue on through the list of stuckages.<br />
<br />
== Finish ==<br />
<br />
<br />
Once you have fixed the stuckages delete the ''<mapname>_stuckages.gm'' file.<br />
<br />
<br />
If you want to check for more stuckages just repeat the process.</div>Palota