First off, I am posting this in the "Simulator Development" part of the forums rather than the PO Wiki part because also this bot is doing Wiki-exclusive tasks now, I am hoping to develop it even further so it can evolve into a bot alike Shanai to run on the server. This thread will function as somewhat of a change log, a reminder to myself and other developers on what to do, as well as a behind the scenes look for regular users. Like the title says, Val is semi-automated, relying on both user input for some tasks, and for others, no user input whatsoever. In addition to being semi-automated, Val is also modular, so modules can be willfully removed and added at any time, even while the bot is running (so there's no need for a restart). The bot is written solely in Python, and tested on Python 2.7.x, so I can't guarantee it will work with any versions lower than 2.7.x or any later versions as well. The framework is derived off of Pywikipedia. I will get around to publishing the framework soon, and the modules at a later time. Give me a few days (from the time of this post) to clean up the code so I can publicize it. For now, though, I am going to make a list of things done and things to do. Feel free to leave a comment with any feedback, may it be questions, comments, etc. Things that are done: Main framework built family/pokemon-online_child.py - this framework has support for multiple Wikis, not just one; in this case, pokemon-online is the child or Wiki name, the contents of the file contains the configuration exclusive to that child or Wiki login.py - initialization script that waits for the user to input the bot password and then returns the status of the log in accordingly (if successfully, the response will be much more verbose than it would be if it resulted in a failure) user-config.py - a simple text file that contains information such as the Wiki's language, the child that corresponds to that Wiki, the bot name, and the character encoding (by default, it's UTF-8) Things to do: Make the list of things to do When I eventually clean up the code enough for it to be published and I host it on the site of my choice, I will make a bug tracker and issue manager along with it where I can record the milestones, progress, etc. of the bot.