-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
issue with CampFort #5301
Comments
have u wait 1800 ? |
No I didn't wait 1800, why would it wait if no lured forts? |
i think that with |
If The bot will not more away imediately if lures disappear because a player might put back a lure right away. However, I am adding a feature that will apply a malus to the time when we see there is no lure. So the bot will leave earlier. |
I set the bot to a big city with huge amount of forts. (41.8756,-87.6291) |
Can you check that it is working with the config you have mentioned in your first post ? It is not 4 or 3 there, it is 2. |
it's working with 2. |
You may not have any 3+ fort camp in your area. |
what's the meaning of 3+ fort camp? 3 forts in a range of xxx meters? |
|
I see, it's quite rare but I did see a place with min_forts_count 3. [2016-09-09 09:46:19] [ CampFort] [INFO] Arrived at destination: 3 forts, 1 lured. |
Keep it at 2 if you want to make the CampFort your main decision point for moving. |
Question answered ? |
I'm trying to use CampFort and notice 2 problems.
Your FULL config.json (remove your username, password, gmapkey and any other private info)
Output when issue occurred
[2016-09-08 12:16:54] [ CampFort] [INFO] New destination at 328 meters: 2 forts, 2 lured.
[2016-09-08 12:24:34] [ CampFort] [INFO] Arrived at destination: 2 forts, 0 lured.
...
staying there
Branch:
master
Git Commit:
11123a8
The text was updated successfully, but these errors were encountered: