An automated bot for Pokemon Go that catches Pokemon, farms items, and manages inventory using configurable rules.
Poketrainer is an open-source automation bot for Pokemon Go that simulates player actions like catching Pokemon, spinning Pokestops, and managing inventory. It solves the problem of manual grinding by automating repetitive tasks with configurable rules for capture, navigation, and resource management.
Pokemon Go players and developers interested in automating gameplay, experimenting with bot behavior, or running multiple accounts with customized automation rules.
Developers choose Poketrainer for its extensive configurability, support for multi-account botting, and active community-driven development, offering a flexible alternative to manual gameplay or less configurable bots.
The original Pokemon Go bot
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The bot allows granular control over capture logic, inventory management, and navigation, with configurable rules for ball usage and Pokemon release methods, as detailed in the CAPTURE and POKEMON_CLEANUP sections.
Users can run multiple bot instances with separate configurations for different accounts, enabling efficient automation across several Pokemon Go profiles simultaneously.
The project has a Slack channel for support and encourages contributions, with ongoing updates like Python 3.5 support and experimental features, indicating community-driven maintenance.
Includes a local web UI to monitor bot status and player information, providing real-time insights without needing to check console logs constantly.
Requires building an external encrypt library (libencrypt.so or encrypt.dll) and managing Python version compatibility, which adds significant overhead compared to pre-packaged solutions.
As an automation bot violating Niantic's terms of service, usage can lead to softbans or permanent suspensions, with the README explicitly warning users to 'use at your own risk.'
Features like NEEDY_ITEM_FARMING are marked as experimental and may not work reliably, potentially causing unintended behavior or resource mismanagement during automation.
The README has disclaimers, relies on external links for item IDs, and mentions parts 'to be updated soon,' making it difficult for newcomers to navigate setup and configuration.