Wrapper needs new developer

[suresttexas00]

Hello all,

I have stopped being in the server business and I don't play Minecraft any longer. I have just gotten too busy with other parts of life. This was enjoyable and I learned a lot. However, I will not be able to keep up with or test the myriads of changes that are occurring with the game. Presently, this code base works reasonably well up to 1.12.1 or 1.12.2 (I forget) in Proxy mode. I am aware of no problems with non-proxy mode; however, I do expect that Mojang will create different server text output in new versions that will eventually break non-proxy mode too (well, not break.. but introduce bugs).

As Ben is also rather inactive, wrapper will need someone that can become familiar with the codebase and implement support for new protocol versions as they emerge.

If such a person steps forward and is serious, I am willing to remain available to answer questions about the present code. I will also periodically keep tabs on this issue board.

~ Surest Texas

[benbaptist]

I have a bit more free time lately thanks to some career changes, and a bit of COVID-19, so I'm going to maybe try to start being a little more active again. I actually started work on a completely new branch called 'lite'. Essentially, I just want to get back to the barebones basics of Wrapper.py, and I wanted to just re-write everything from scratch. Doing so allows me to some major changes without any worry of backwards compatibility. It'll be super lightweight compared to the relatively bulky main branch, and will follow the more traditional setup.py approach to installation instead of the weird zip-bundling thing I did originally.

[benbaptist]

I've decided to fork off Wrapper Lite into its own thing entirely, so I created a new repository for it. If anybody's interested:

https://github.com/benbaptist/wrapper.py

This is entirely incompatible with the original Wrapper, so I figured keeping them separate would be the best.