OutdatedNecroBot v0.9.3

I can't config the GoogleAPIKey.
I already have a Key and put them here: "GoogleAPIKey": "PUT THEM HERE" but doesn't work.

Hi guys. this is my first post. I've pretty much downloaded and got necro 9.3 running last night on a new ptc acc. firstly it's great as it stands. I'm wondering what sort of things I can change in the config to increase xp/ph, as I'm a bit of a noob I've looked and began to play but a push in the right direction would be a big help.I obviously dont want to change a setting that will increase softbans or unrealistic movement speeds. anyways thanks and hello again

EDIT** turns out I had 9.2 downloaded and running. Have upgraded to 9.3 but as Dicamo says above I also put the API key in and it's not being recognised when I start Necro. in 9.2 the api was in the auth file so I tried adding the line but it is automatically deleted so that's definitely not it. Will just stick to 9.2 until can solve this dilemma I think.

anyone tell me whu do we have to put the google apikey ??

the key is part of the googlewalk in the config file now. but it doesnt seem to be picked up when you run it. give it a go and let me know how you go. I kept scrolling straight past it so if you want to find it maybe ctrl+f lol

That basically mean that your character won't go from one pokestop to another in a straight line. It will use information from google map in walk mode to determine how a normal person would get there and use that route to avoid suspicion (like walking over a lake or a building).

this one has slow xp .. is there anyway to bring the xp up?
i tried modifing config

- - - Updated - - -

for google API you actually have to click that web
and creat one.
google - creat google API key.
you will be logging into your google account then it asks you some questions.
that web will give you API key and you copy past on your Auth

Hi all
when i closed a bot i want a bot record last status
example
amount of poke
item limit
for continue data when we are running bot again


decrease banned

looks like creating another new api worked... although i had the old 1 in at time of starting with new key added i have data on dashboard so it must be getting used