December Update

It's been a while since we've made an update, so I'll post one right now.

First, I'd just like to say that the server has the capability  to connect players to the server (without the world, unfortunately). Before you get excited, the player does spawn, however, they fall into the void without taking damage, until being disconnected by a peculiar JSON error we are still investigating (issue TRD-9). On the other hand, we are still investigating the format of the MapChunkBulk packet, as well as the conpression (which appears to work correctly on some packets, and not others, it particularly does not like non player entities or inventory packets being sent). We also have a few issues with the players's keep alive not being sent, which prevents players from disconnecting because of connection time outs. It was changed in order to keep it correctly concurrent.

Second, we still are working on the API and implementation concurrency. We've stopped pretty much everything else, excluding packet analysis (lead by Mythbusterma, big thanks to him for spending time on Wireshark decoding Minecraft packets) for player joining, to work on improving and smoothing out the API. Our planned changes are currently being discussed, which includes more documentation and code comments to explain the implementation, updates to concurrency (including the server config which I have found to be impossible to modify safely, and an improved task executor which I've tested personally to be 2-4 times faster than the Java executor), single instantiation listener/command registration to eliminate state gotcha's, more tests using JCStress and benchmarks, the ability to obtain the registered instance of commands and listeners, refactors and tweaking of naming consistency in the API (removing the "get" from getXXX, toXXX to asXXX, etc), and technical design documents.

Third, we'd like some new developers. Our current team consists of 4 people, me, Mazen, Vilsol, and Mythbusterma. If you have experience with the Minecraft protocol, consider helping us out to release the server faster. If you deal with concurrency, I'd like help myself reviewing the design of Trident and analyzing/testing for thread safety. If you're just a general developer, we'd love feedback and suggestions for the API, and if you could submit a PR on our GitHub, that would be awesome too. If you want to work with us and have expertise in the protocol or concurrency, please tweet to @TridentSDK, submit an issue on JIRA, or post on the forums. As said, if you just want to help, a PR would do great.

Fourth, expect inactivity or slowed progress the following weeks. Myth (documentation) is getting back with his family, Mazen needs to finish a new computer because his last one broke, and I have to do 2 tests when I get back from break and start training for next year's season. Vilsol has been inactive for a bit, he's don testing on TridentSDK and develops this wonderful site. He is most likely studying at his University, but I don't know for sure.

in my opinion, our release should be in February, but it is difficult to tell for sure. Stay tuned.

 

xTrollxDudex, Developer of Concurrency/Testing 

Copyright © 2019 TridentSDK
Made by Vilsol