Brutus5000 wrote:
Oh boy quite sensitive here young man. I did not intend play the blame game, but before you accuse us of spreading FUD let's recap your argument about the burden of never being allowed to break.
Calm down. This is not a balance forum, I'm not interested in laying blame or quipping at people.
I never asked to become the main Python client maintainer. This happened out of necessity after Duke was no longer involved - without me you'd be forced to make a transition to the Java client, which would probably be for the better.
Brutus5000 wrote:
In the backend we built a modern replacement for the broken server-side stuff (REST API) that the all clients are open to use. We have offered help and explanation for the required api queries multiple times now. Instead you chose to refactor the chat...
Refactoring chat was necessary - without it, it was impossible to reconnect to chat and players on the list were missing or out of position. Chat is a significant part of the client - imagine what would happen if every time the IRC server crashed as often as it did lately, you'd have to restart the client for it to work again, and all your existing chat history was gone. As for jsonapi for the Python client - I'm sure you're aware of the hurdles regarding library support and async, we discussed it on Slack multiple times. From a technical standpoint it's interesting stuff, if you want to see both bugfixes and this, I welcome you to contribute.
Brutus5000 wrote:
Edit:
By the way is classic client is not meant as devaluation. Coming from the Ultima Online world, the classic client is a fixed term there refering to the first released client, while the "modern client" introduced 3d graphics nobody wants to use.
I appreciate that - but at the same time I'm slightly annoyed that the Java client receives far more dev power (which I understand is any developer's choice), and at the same time there doesn't seem to be any intention of making it the primary client for the game.
In October I'll be resuming my studies while working part time, so I won't be able to contribute to the client what little I do right now. From that point the Python client will be essentially unmaintained, and I think it's a good idea to either have some people pick it up and continue work on it, or deprecate it for good in favour of the Java client.Statistics: Posted by Wesmania — 18 Jun 2018, 17:07
]]>