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

issue with CampFort #5301

Closed
liejuntao001 opened this issue Sep 8, 2016 · 13 comments
Closed

issue with CampFort #5301

liejuntao001 opened this issue Sep 8, 2016 · 13 comments
Assignees
Labels

Comments

@liejuntao001
Copy link

I'm trying to use CampFort and notice 2 problems.

  1. If I increase "min_forts_count" to 4, I don't see CampFort kicking in
  2. If a cluster was detected and after moved to the place, if the lure has gone, bot is not leaving

Your FULL config.json (remove your username, password, gmapkey and any other private info)

  {
    "type": "CampFort",
    "config": {
    "enabled": true,
    "max_distance": 2000,
    "min_forts_count": 2,
    "min_lured_forts_count": 1,
    "camping_time": 1800,
    "moving_time": 600
    }
  },
  {
    "type": "MoveToFort",
    "config": {
    "enabled": true,
    "lure_attraction": true,
    "lure_max_distance": 300,
    "walker": "PolylineWalker",
    "log_interval": 5
    }
  }

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

@MZorzy
Copy link

MZorzy commented Sep 8, 2016

have u wait 1800 ?

@liejuntao001
Copy link
Author

No I didn't wait 1800, why would it wait if no lured forts?

@MZorzy
Copy link

MZorzy commented Sep 8, 2016

i think that with
camping_time": 1800,
bot will not move until 1800 time expire.

@julienlavergne
Copy link
Contributor

If min_forts_count is 4, you will only go to clusters of 4 forts. Do you have such thing in your area ? If not, the task will not so anything.

The bot will not more away imediately if lures disappear because a player might put back a lure right away.
The next cluster could be far so it will be a waste of time to decide to go 1000 meters away to realize lures are back in our previous location.

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.

@liejuntao001
Copy link
Author

I set the bot to a big city with huge amount of forts. (41.8756,-87.6291)
I tried to set min_forts_count to 3 and saw no log about CampFort

@julienlavergne
Copy link
Contributor

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.

@liejuntao001
Copy link
Author

it's working with 2.

@julienlavergne
Copy link
Contributor

You may not have any 3+ fort camp in your area.

@liejuntao001
Copy link
Author

what's the meaning of 3+ fort camp? 3 forts in a range of xxx meters?
basically the area is full of forts, if you search the coordinate.

@davidakachaos
Copy link
Contributor

min_forts_count is the amount of forts you can reach while standing in 1 spot.
Of those a count of min_lured_forts_count must be lured for the task to select is as a camp site.

@liejuntao001
Copy link
Author

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.

@julienlavergne
Copy link
Contributor

Keep it at 2 if you want to make the CampFort your main decision point for moving.
Put it to 3 with a minimum number of lures, if you know you have several spot with 3 forts reachable and only want to go there when it is really worth it.

@julienlavergne
Copy link
Contributor

Question answered ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants