sudoinit6 Posted April 11, 2017 Share Posted April 11, 2017 I am writing a tut island script and I am almost done, while testing sometimes it just stalls out and when I turn the config debugger on, 281 is just missing. Happens at several different places but not consistently, sometimes the script works flawlessly all the way through, right now it is stopped by the Survival Trainer and the configs listed are: 1999:0 1998:0 1997:0 etc... Is there something I am missing? Quote Link to comment Share on other sites More sharing options...
Juggles Posted April 11, 2017 Share Posted April 11, 2017 15 minutes ago, sudoinit6 said: I am writing a tut island script and I am almost done, while testing sometimes it just stalls out and when I turn the config debugger on, 281 is just missing. Happens at several different places but not consistently, sometimes the script works flawlessly all the way through, right now it is stopped by the Survival Trainer and the configs listed are: 1999:0 1998:0 1997:0 etc... Is there something I am missing? Nothing wrong with the configs for me make sure u have configs on before u do the task or it wont show up Quote Link to comment Share on other sites More sharing options...
sudoinit6 Posted April 11, 2017 Author Share Posted April 11, 2017 5 minutes ago, Juggles said: make sure u have configs on before u do the task or it wont show up Thanks for the reply, not sure what you mean by this though, the config debugger? Quote Link to comment Share on other sites More sharing options...
lizzzerd Posted April 11, 2017 Share Posted April 11, 2017 21 minutes ago, sudoinit6 said: Thanks for the reply, not sure what you mean by this though, the config debugger? yeah just make sure the configs numbers are on screen before you do the action that triggers the change in a config, or else you wont see it. ie. you cant open up the config debug after you do things to see the past changes in the configs Quote Link to comment Share on other sites More sharing options...
sudoinit6 Posted April 11, 2017 Author Share Posted April 11, 2017 Thanks both of you. The issue wasn't related to the bot, in all cases it came down to PEBKAC. Thanks for your support, this script is so annoying to write! Quote Link to comment Share on other sites More sharing options...