Refactor repeat_start needed

[bwookieeeee]

When a robot fails to enter a ready state, it should not say the boot message. That is to say, when a robot fails to authenticate, it should not continue saying "OK" until it's killed.

This appears to be somewhat addressed in networking.py, however I've failed to observe the termination actually terminating; although it may be an overzealous repeat_start starting the script after it's terminated, I'm not quite sure.

[Nocturnal42]

This is in part because the boot message is in the internetStatus function, and not actually linked to the bot authenticating to the site. I was surprised when you added a customized boot message that you did not move it somewhere more appropriate.

The other reason is repeat_start. The internet status function runs by default at 120 second intervals, so unless it's been dropped to something unreasonably low, the controller is being terminated and restarted and thus repeating the message.

[bwookieeeee]

I haven’t yet looked through the code to see the absolute best spot for it. I’ll do that when I get home, but am also open to suggestions. Currently sitting in the lobby of a Red Robin waiting for somebodies food, trying to ignore the Vengaboys on the speakers.

[bwookieeeee]

Looks like it's actually an issue with repeat_start. Not sure what to do about that...