I'm not opposed to dumping my code into a public repository of some kind, but its a bit premature for me. Unlike your project, say, which is designed as an end user product, mine is more of an exploratory one, trying to push the limits of Paragon Chat and exploring the Paragon Chat protocol in ways normal users can't with the game client. In the process, I've helped spot some subtle bugs in Paragon Chat itself, but the project is really about learning the protocol and what it can ultimately do. My code gets refactored practically weekly and there's no helpful user interface or manual. To the extent I'm discussing my work, the target is more other programmers that are interested in similar projects, such as slick and dyne.
At some point, and that point may be far off depending on Paragon Chat's development trajectory, I may start to make ArcanaBot more end-user friendly, but that's not likely to happen for some time. As an educational tool, its still in its infancy. Even I don't know if everything I do the way I do it is a good idea, because new things keep popping up. For example, I've done keyboard control three different ways already. I'm also using a lot of shortcuts I don't advocate as being good programming technique, because I needed the speed to bootstrap the learning process.
Also, mine is written in Python 2. Because trying to keep unicode conversions straight on top of learning a library that's based entirely on string manipulation was a bridge too far for me.
