Accounts clustering and ignoring most spawnpoints

Noctem / Monocle

PoGo mapper and notifier

MIT License

122 stars 151 forks source link

Accounts clustering and ignoring most spawnpoints #294

Open sciguma opened 7 years ago

sciguma commented 7 years ago

I tried my best but I don't get it. Something is very off here. I try to scan a bigger area and the accounts seem to ignore most of the map and stick to certain points.

Initial scan was made with a lot a accounts and then switches to 30 lv30 accounts. Should be sufficient normally for this area. I tried lot's of settings but I don't get my guys to move around. Any advice or is this a known problem?

M3G4THEKING commented 7 years ago

@sciguma add more workers ,you have alot of spawnpoint

sciguma commented 7 years ago

They still cluster. The spawn points shown are by far not all and those were scanned with 100 accounts. Thing is I wanted to tune the accounts to fly with 140 km/h which worked quite nice with RM until their login process screwed up. I don't get why they also don't move away from their clusters. I know these spawns and they are by far not bound that hard to the places. Like those 2 workers close to the middle next to the Seal and the Karps. I can clear/catch this area by foot in 15min. and then move on. Hmm..

MiguelGall commented 7 years ago

Can you show us the config.py settings? terminal screenshot and scan.log also would help

ghost commented 7 years ago

They will prioritise the known (blue) spawnpoints over the unknown (red) spawn points so it is expected they would cluster around paths of blue spawn points. You need to let your mass swarm of low level workers turn those spawn points blue by learning the tths then drop in your 30's also as previously suggested up your worker count just looking at that I can see you don't have nearly enough workers remember they are limited by speed & time and will prioritise blue over red.