(Last Updated On: August 3, 2016)

PogoLocationFeeder

This is exactly the enhancement you need to gather rare and high IV pokemon alike during long botting sessions. The bot is constantly pulling from popular discords and json feeds which aggregate the latter.


Download the latest build:

v0.1.10

General info:

We had to reconfigure our to only allow rare pokemon to be uploaded, too much pidgeys & weedles are killing our server. See what pokemon are supported by our server at the bottom (in managed mode)

Fixes

Fix pokesnipe setting Fix performance issues on the server Add KimCordashian/coord_input as a channel (We don't use the output channel because they are based on our feed, stop asking 🙂 ) Fixed verified pokemon without a moveset. (Some bots haven't extended the CapturePokemonEvent like new necrobot did. If you are a bot developer, please implement this). Also trying to control the massive amounts of unnecessary uploads

New settings:

UseUploadedPokemon = true; //Allow uploads by bots and manual input (Note: Some bots might capture a pokemon before it's was spotted on another channel or site, then it still spotted by the bot) UnverifiedOnly = false; //Scanner setting: Don't use this unless you want to verify the feed before everyone else PokemonNotInFilterMinimumIV = 100; //Expiremental: Allow pokemon that aren't in the filter list above a certain IV (Note the server will only allow above 90% IV), Default 100, meaning no pokemon will be added.

Pokemon supported in managed mode by the Pokefeeder.live server (unless higher than 90IV)

[ "Venusaur", "Charizard", "Blastoise", "Golem", "Raichu", "Nidoqueen", "Nidoking", "Ninetales", "Vileplume", "Arcanine", "Poliwrath", "Alakazam", "Machamp", "Victreebel", "Tentacruel", "Slowbro", "Muk", "Gengar", "Exeggutor", "Electabuzz", "Gyarados", "Lapras", "Ditto", "Vaporeon", "Jolteon", "Flareon", "Snorlax", "Articuno", "Zapdos", "Moltres", "Dragonite", "Mewtwo", "Mew" ]

Note: source is not correct (GitHub noob)=> https://github.com/5andr0/PogoLocationFeeder/commit/478cbeb528725810df48f80c6eae2cf398f7664e was added to this release


About

This is a standalone server that will scrape messages containing Pokémon to snipe from a Discord channel. It will parse those messages and broadcast them to connected clients as JSON objects.

NOTE: Client integration with NecroBot supported as of 4.0 release.

PogoLocationFeeder (PogoLoco) is designed to interface with NecroBot (and recent forks thereof) to allow it to automatically snipe Pokémon posted to dedicated Discord sniper channels.

The wikis of both these respective projects have configurations guides that explain client-side sniping settings.


How to Configure

Building from source will always keep you up-to-date with the latest features and bugfixes. That said, the latest release may also be found on the releases page.


Server

After building the project and running the executable for the first time, follow the on-screen instructions and fill out the config.json file. Make sure you connect your discord account with NecroBot and PokemonGo Rare Hunting first.

Here’s a config example:

{
  "Port": 16969,
  "usePokeSnipers": true
}

Client

NecroBot’s config.json file contains the following relevant options:

  "SnipeAtPokestops": true,
  "MinPokeballsToSnipe": 0,
  "SnipeLocationServer": "<set this to the configured server>",
  "SnipeLocationServerPort": <integer port of the configured server>,
  "UseSnipeLocationServer": true,
  "UseTransferIVForSnipe": <true/false. Note that this will SKIP sniping Pokémon below your transfer IV setting>,
  "MinDelayBetweenSnipes": 5000,

  "PokemonToSnipe": {
    "Locations": [ 
      {  
         "Latitude": "<This feature checks additional locations...>",  
         "Longitude": "<...other than those used by this bot>"
      }
    ], 
    "Pokemon": [
      "<List of Pokémon the bot is allowed to snipe>",
      "Mewtwo"
    ]
  }

Additional Information

NOTE: Current GTX pathing in NecroBot does not give ample time to the sniper task. I will update this message when the logic is fixed.

A reasonable default list of NecroBot config.json sniper settings may be found at: Ilses’ PokeSnipe List V1.3


Contact

Discord: @Ilses#9123


NecroBot Setup Description

With this setup, NecroBot will rely on a separate location feeder service instead of the config. This service will run on the same machine as NecroBot to supply dynamic Pokemon locations from the Discord server channels for sniping.

  1. Open Necrobot’s Config.json
  2. Make sure your values are set like below:
    "SnipeAtPokestops": true,
    "SnipeIgnoreUnknownIv": false,
    "SnipeLocationServer": "localhost",
    "SnipeLocationServerPort": 16969,
    "UseSnipeLocationServer": true,
  3. Run Necrobot
  4. Pogofeeder should give you a new notification about a connection from 127.0.0.1
  5. If you start getting notifications about Pokemon in PogoFeeder, you set it up correctly. You should see Necrobot attempt to catch some of the Pokemon, but it will only catch them all depending on how quick Pogofeeder finds the coordinates.

 

Non-GPX

If UseGPXPathing is set to false, Sniping will execute every Pokestop.

GPX

If UseGPXPathing is set to true and GPXFile is found, Sniping will execute every second or based on the value in milliseconds for MinDelayBetweenSnipes (whichever is higher).

 All builds of PogoLocationFeeder available for download

v0.1.10

General info:

We had to reconfigure our to only allow rare pokemon to be uploaded, too much pidgeys & weedles are killing our server. See what pokemon are supported by our server at the bottom (in managed mode)

Fixes

Fix pokesnipe setting Fix performance issues on the server Add KimCordashian/coord_input as a channel (We don't use the output channel because they are based on our feed, stop asking 🙂 ) Fixed verified pokemon without a moveset. (Some bots haven't extended the CapturePokemonEvent like new necrobot did. If you are a bot developer, please implement this). Also trying to control the massive amounts of unnecessary uploads

New settings:

UseUploadedPokemon = true; //Allow uploads by bots and manual input (Note: Some bots might capture a pokemon before it's was spotted on another channel or site, then it still spotted by the bot) UnverifiedOnly = false; //Scanner setting: Don't use this unless you want to verify the feed before everyone else PokemonNotInFilterMinimumIV = 100; //Expiremental: Allow pokemon that aren't in the filter list above a certain IV (Note the server will only allow above 90% IV), Default 100, meaning no pokemon will be added.

Pokemon supported in managed mode by the Pokefeeder.live server (unless higher than 90IV)

[ "Venusaur", "Charizard", "Blastoise", "Golem", "Raichu", "Nidoqueen", "Nidoking", "Ninetales", "Vileplume", "Arcanine", "Poliwrath", "Alakazam", "Machamp", "Victreebel", "Tentacruel", "Slowbro", "Muk", "Gengar", "Exeggutor", "Electabuzz", "Gyarados", "Lapras", "Ditto", "Vaporeon", "Jolteon", "Flareon", "Snorlax", "Articuno", "Zapdos", "Moltres", "Dragonite", "Mewtwo", "Mew" ]

Note: source is not correct (GitHub noob)=> https://github.com/5andr0/PogoLocationFeeder/commit/478cbeb528725810df48f80c6eae2cf398f7664e was added to this release

PogoLocationFeeder-Release-V0.1.9

This is a prerelease to show of the new features and to test how many people can connect to our server. When your having trouble to connect to the server, please turn of managed mode and try again later.

New settings:

GeoLocalocationFilter: The allows you to only receive pokemon that are in that area. "UseGeoLocationBoundsFilter": false, "GeoLocationBounds": { "SouthWest": { "Latitude": 40.744627259246641, "Longitude": -74.006222741943361 }, "NorthEast": { "Latitude": 40.816119123701981, "Longitude": -73.903569238525392 } }, IsServer: Set this to true if you want to host your own server and let your friends connect to it. "IsServer": false, Managed: Managed is when you connect to a server to retrieve your pokemon. All filters will still work. If you turn this off, you have the same functionalities as before, but no verified data "IsManaged": true, Serverhost: Which server to connect to "ServerHost": "pokefeeder.live", ServerPort: Which serverport to connect to "ServerPort": 49000, OutgoingServerPort: When IsServer is true, you need to specify a port to host on. "OutgoingServerPort": 49000, ShareBotCaptures: Allow your bots to send back the information about captured pokemon to PogoLocationFeeder "ShareBotCaptures": true, BotWebSocketPorts: Configure the port to read from the bot(s), this is the websocket which necrobot for example uses. "BotWebSocketPorts": [ 14251 ], VerifiedOnly: Only receive pokemon that were verified by bots. "VerifiedOnly": true, MinimumIV: The minimumIV a pokemon should have to receive it. Setting this value higher than 0, implies all pokemon must be verified. "MinimumIV": 0.0

Deprecated

It is advised not to use the verify by skipplagged anymore.

PogoLocationFeeder-Release-V0.1.8

  • Various repo fixes. Skiplagged checks now use a randomized user-agent.
  • Added option to manually remove pokemon entries (e.g., after successfully sniping them)
  • Added toggle to enable/disable pokemon filter
  • Users can now switch between two themes: dark and light

We have acquired enough donations to move the Discord feed to a dedicated server. This will allow us to actually fix the feed if it goes down in the future; the switch should be happening shortly.

We will also be working on the validated feed -- an announcement will be posted as soon as this is available.

Finally, we will be moving discussion of the feeder from our fledgling discord server to the 100IVCLUB server. Going forward, release candidates will be instead be posted in in the lounge and sniping_lounge channels.

(Edit: First post of the .zip didn't include version update for update checking, and so would claim you didn't have the latest version -- this is fixed now)

PogoLocationFeeder-Release-V0.1.7 Skiplagged verification integrated, bugfixes

PogoLocationFeeder-Release-V0.1.6 Filter integrated, bugfixes

PogoLocationFeeder-Release-V0.1.5 PokeZZ & pokewatchers

Added PokeZZ and PokeWatchers. Also discord is working fine again =)

Edit: Some users have reported that win7 is not working properly with this release! This issue should be resolved soon, but for now please wait for v0.1.6 if you are using Windows 7.

PogoLocationFeeder-Release-V0.1.4

Settings are now fully editable through the GUI! Furthermore, we have implemented a new thread management system which should more robustly handle disconnects.

Additionally includes bugfixes for PokeSniper2 integration, and the ability to select the executable path if it is not detected automatically.

And finally, you can now ignore channels by removing them from your discord_channels.conf!

PogoLocationFeeder-Release-V0.1.3 PokeSnipers2 integration

PokeSniper2 integration is now available! If we detect a PokeSniper2 installation, a button will be available to automatically snipe pokemon via the new v1.9 protocol. You need install the pokesniper2 protocol for this to work; please follow the guidelines in the ownedcore topic.

This release also includes general bugfixes, GUI updates (max pokemon to display, copy coordinates button, debug window, and other fixes) and automatic version checking. The ability to ignore channels will be available in our next release!

PogoLocationFeeder-Release-V0.1.2 new GUI

Added a gui template. Minor bugfixes. Should be much quicker than 0.1.1, and adds better logging to boot!

PogoLocationFeeder-Release-V0.1.1 Hotfix

Server config file moved to exe directory

PogoLocationFeeder-Release-v0.1.0

Huge update to Discord integration aimed at addressing server load issues.

PogoLocationFeeder v0.0.2.1

Add welcome message linking to github repo so we can receive issue reports.

PogoLocationFeeder v0.0.2

  • Adds error handling for auth failures
  • Improved parsing
  • Ignore duplicate coords across servers/channels
  • Pokesnipers integration
  • Various bugfixes

v0.0.1

2 COMMENTS

  1. v1.10 is really bad, the pokemon list is less monster, and even the software “debug” show received monster, but the GUI list never refresh, sometime the list just went blank with zero pokemon. But if you close it and re-open, new list refresh immediately, please change back to v1.8. v1.10 only show IV, it really doesn’t mean anything if the list always blank.

LEAVE A REPLY

Please enter your comment!
Please enter your name here