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.

Sign up for GitHub

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

Jump to bottom

The bot don't walk #1692

Closed
crusardri opened this issue Jul 29, 2016 · 19 comments
Closed

The bot don't walk #1692

crusardri opened this issue Jul 29, 2016 · 19 comments

Comments

@crusardri
Copy link

The log show me this.
[21:02:05] Spinning ...
[21:02:05] Loot:
[21:02:05] 50 xp
[21:02:05] - 2x Pokeball (Total: 129)
[21:02:05] - 1x Greatball (Total: 4)
[21:02:05] PokeStop on cooldown. Time left: 4 minutes, 44 seconds
[21:02:07] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:09] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:11] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:12] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:14] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:16] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:17] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:19] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:21] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:23] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:24] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:26] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:28] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:29] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:31] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:32] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:34] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:36] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:37] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:39] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:41] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:42] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:44] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:46] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:47] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:49] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:51] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:52] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:54] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:56] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:57] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:02:59] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:03:01] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:03:03] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:03:04] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:03:06] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:03:08] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:03:09] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:03:11] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:03:13] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km
[21:03:14] Walking from (40.41615589414066, -3.67896573069202) to [40.41615589414066, -3.67896573069202] 0.00km

Problem seen in this commit: 9a29c0f (DEV)
@Simbe90
Copy link

Simbe90 commented Jul 29, 2016

Getting this same error after just doing "git pull"

@Kafkamorph
Copy link

Same here:
[20:05:25] Walking from (51.4843979, -0.3015578) to [51.4843979, -0.3015578] 0.00km
[20:05:27] Walking from (51.4843979, -0.3015578) to [51.4843979, -0.3015578] 0.00km
[20:05:28] Walking from (51.4843979, -0.3015578) to [51.4843979, -0.3015578] 0.00km
[20:05:30] Walking from (51.4843979, -0.3015578) to [51.4843979, -0.3015578] 0.00km
[20:05:32] Walking from (51.4843979, -0.3015578) to [51.4843979, -0.3015578] 0.00km
[20:05:33] Walking from (51.4843979, -0.3015578) to [51.4843979, -0.3015578] 0.00km
[20:05:35] Walking from (51.4843979, -0.3015578) to [51.4843979, -0.3015578] 0.00km
[20:05:36] Walking from (51.4843979, -0.3015578) to [51.4843979, -0.3015578] 0.00km
[20:05:39] Walking from (51.4843979, -0.3015578) to [51.4843979, -0.3015578] 0.00km
[20:05:40] Walking from (51.4843979, -0.3015578) to [51.4843979, -0.3015578] 0.00km

@Simbe90
Copy link

Simbe90 commented Jul 29, 2016

Is there a simple command with git perhaps that would allow us to downgrade or return to the previous commit?

@tim427
Copy link

tim427 commented Jul 29, 2016

I can confirm this bug!

@Drambuie
Copy link

I can also see the above happening on the latest dev build

@Kafkamorph
Copy link

To revert from the latest pull to a previous state:

git reset --hard xyxyxyxy
where xyxyxyxy is found by doing

git reflog

@buettner123
Copy link

if you do git reset --hard you will probably loose your config files. A git checkout hash, where hash is the commit hash you can get from the git log command, should work as well and leave your configs untouched

@Simbe90
Copy link

Simbe90 commented Jul 29, 2016

Well at least 434cb3a was working OK for me and thanks for the tip on how to revert back!

@Kafkamorph
Copy link

@buettner123: good idea. Cheers. :)

@Simbe90
Copy link

Simbe90 commented Jul 29, 2016 •
edited
Loading

Tried using the reset --hard method (did move out my config.ini from the directory first) but I just receive this:

`(PokemonGo-Bot) xxx-MacBook-Pro:PokemonGo-Bot xxx$ git reset --hard 434cb3a

HEAD is now at 434cb3a Fix transfer worker not triggered for last pokemon (#1664)`

@Simbe90
Copy link

Simbe90 commented Jul 29, 2016 •
edited
Loading

Nevermind, it worked anyways and now back to commit 434cb3a. Have to keep checking on when they have fixed this.

@DayBr3ak
Copy link
Contributor

DayBr3ak commented Jul 29, 2016 •
edited
Loading

git reset --hard won't affect your config files. Config files aren't tracked by git. Unless you are directly using the config.json.example without having renamed it (shame)

@kubiq
Copy link

kubiq commented Jul 29, 2016

Is your bag full, or almost full? It disables forts if it is full. So just empty it in phone app, or set up item_filter

@buettner123
Copy link

@DayBr3ak: my bad, untracked files are indeed not affected by git reset --hard.
@Simbe90: just fyi about the message you got from git: it said that your HEAD now points to the commit 434cb3a and all tracked files got reverted to that commit and that was exactly what you wanted it to do

@martynvandijke
Copy link

Can confirm latest dev build won't work but aff8e76 works 👍

@Drambuie
Copy link

did the git reset --hard 434cb3a command

is there another command you have to run to get it to downgrade the files as i still have the same problem?

@ghost
Copy link

ghost commented Jul 29, 2016

Mine navigates alright (latest dev), but wrong location data is being sent to location-username.json so it appears stationary on the map.

@Simbe90
Copy link

Simbe90 commented Jul 29, 2016

I can also confirm that the latest dev d5acc70 works now. I can't comment on the map issue though as I do not use it.

PS. Getting the latest dev after reverting with "git reset --hard" works by just "git pull"?

@gregtampa
Copy link
Collaborator

come to slack chat #help and someone can help you
NOT A BUG

@jonathanbalagot jonathanbalagot mentioned this issue Jul 30, 2016
Closed
hoanghuynh pushed a commit to hoanghuynh/PokemonGo-Bot that referenced this issue Sep 28, 2016
@Skullmonkey @MonkeyLeeT
Added 3 custom map styles that remove labels (PokemonGoF#1692)
6734611 
## Description
I took the 3 custom maps and removed all the labels and icons for a less cluttered look

## Motivation and Context
The map looked cluttered and the street names, icons, and other labels were distracting to me.

## How Has This Been Tested?
Ran on local build and tested with Chrome and Firefox.

## Screenshots (if appropriate):
http://imgur.com/ewnd0zN
http://imgur.com/xoTtAuL
http://imgur.com/MPqHbLz

## Types of changes
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)

## Checklist:
- [x] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@kubiq @gregtampa @martynvandijke @Kafkamorph @tim427 @crusardri @DayBr3ak @buettner123 @Drambuie @Simbe90