Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MULE 1 #341

Closed
Earthdivine opened this issue Feb 18, 2015 · 1 comment · Fixed by #331
Closed

MULE 1 #341

Earthdivine opened this issue Feb 18, 2015 · 1 comment · Fixed by #331
Labels
Bug This is a bug in our game code

Comments

@Earthdivine
Copy link
Contributor

MULE 1 seems to have broken pathing, which is odd considering MULE 2 worked fine. Everytime I tried to get MULE 1 to move it would slam into the wall it starts at and stop moving.

Oddly enough as well, opening the MULE 2 menu turns on MULE 1 at the same time. Need to see if it happens every time or just once.

@mvanalphen mvanalphen added the Bug This is a bug in our game code label Feb 18, 2015
@mvanalphen
Copy link
Contributor

This is most likely an issue with our frequency code. Basically, the bot only has a destination if it's been pinged by a signal from a PDA or beacon, and this doesn't work half the time (hence the longstanding Beepsky issue we had, and Ofitser refusing to continue patrolling). Is probably difficult to fix, although I'll make a few minor adjustments.

Kiyahitayika pushed a commit to Kiyahitayika/Paradise that referenced this issue Apr 12, 2021
…p-in-not-without-my-anus

Don't forget the SQL update script
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug This is a bug in our game code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants