Commit Graph
154 Commits
Author SHA1 Message Date
Manevolent d9ce7f21a3 JitPack is broken. Trying one more time to get this to go through. 2018-10-13 02:17:13 -04:00
Manevolent 2f7bf10322 Merge remote-tracking branch 'origin/master' 2018-10-13 01:35:14 -04:00
Manevolent ce77f91c6f I'm changing whisper and voice handlers. I think that the COMPRESSED flag is important, it may signal you to reset your decoder for each incoming packet. Not sure. 2018-10-13 01:35:09 -04:00
Manevolent a85904555e Synchronize the remote counter, and correct an issue with rest() concerning generation IDs 2018-10-02 08:58:29 -04:00
Manevolent 6bf85e3c6c Re-order handleError (handleComplete) 2018-09-20 02:13:05 -04:00
Manevolent 5ee74e6c45 Make step 127 public 2018-09-18 15:13:58 -04:00
Manevolent e4a1e69410 Packet flags for server, setters would apply to wrong object 2018-09-18 00:15:14 -04:00
Manevolent 8ba218f094 Timestamp was not sent right 2018-09-17 23:54:54 -04:00
Manevolent 66bc483490 Init1 changes to make it neater 2018-09-17 23:41:28 -04:00
Manevolent 127ae9bc8f Don't mind me... 2018-09-17 23:01:25 -04:00
Manevolent ec34b59ad3 DatagramPackets are synchronized. This could have caused problems, or would, cause problems. 2018-09-17 22:55:34 -04:00
Manevolent e683ad1bbb Added helper methods to connect()
Refactored packet handlers
2018-09-17 21:43:36 -04:00
Manevolent 4c539e44c7 Proper extension 2018-09-17 19:51:33 -04:00
Manevolent e48a5a0435 Handle notifypermissionlist, Init127 2018-09-17 15:24:30 -04:00
Manevolent 8d74195d42 Support clientinitivexpand and not just expand2 for all TS3 server support (incl. TeaSpeak) 2018-09-17 13:24:09 -04:00
Manevolent d271b7a358 Set transformation before connecting 2018-09-11 08:35:17 -04:00
Manevolent 956344f1c9 Better logging for decryption errors 2018-09-11 08:21:16 -04:00
Manevolent 8e87f8c2c1 Merge remote-tracking branch 'origin/master' 2018-09-06 11:53:55 -04:00
Manevolent 285d6ab9a4 Add setEventMultiThreading(boolean) instead of forcing multi-threading on 2018-09-06 11:53:44 -04:00
Manevolent 15f7485fa9 Moving command execution to a single thread executor. I leave it up to end-users now if they want event processing to be multi-threaded. 2018-09-06 11:49:51 -04:00
Manevolent 1dbca2543b Remove -> Deleted 2018-08-31 21:55:55 -04:00
Manevolent 882812ff40 Merge remote-tracking branch 'origin/master' 2018-08-31 21:54:19 -04:00
Manevolent f248faad72 Add support for more missing events 2018-08-31 21:54:15 -04:00
Manevolent b7282cc337 Reconnection issues 2018-08-29 11:44:14 -04:00
Manevolent 2207e65392 Silly imports. 2018-08-23 11:41:39 -04:00
Manevolent 4c235badd5 Server group add/del 2018-08-23 11:34:27 -04:00
Manevolent 61f35951e2 Weak TSDNS support (_udp SRV record type) 2018-08-23 09:18:24 -04:00
Manevolent 09c21b171e Pull up socket role 2018-08-23 08:48:58 -04:00
Manevolent da3495c297 Whisper support 2018-08-17 16:27:18 -04:00
Manevolent 0cd72622a2 latestPacketId exposure for the same reason as the last commit 2018-08-16 13:44:43 -04:00
Manevolent 3898f2658c Expose the remote counter's features for discerning buffer beginning and end. I need this because my bot will be decoding audio for speech recognition. 2018-08-16 10:12:05 -04:00
Manevolent 83e59ab6e9 Exposed voice packets to the client 2018-08-15 11:43:41 -04:00
Manevolent 99ed8dda77 Use packet ID instead of key. 2018-08-13 20:30:50 -04:00
Manevolent d0e2ad194f It's possible for a packet's responsible queue to be incorrectly tracked. 2018-08-13 20:30:05 -04:00
Manevolent e4e1b5b4fe Still getting random connection losses. I think it may have to do with the way I set up ACK, ACK_LOW, and PING commands. 2018-08-13 18:18:49 -04:00
Manevolent f041820020 Catch socket exception for code clarity even though I dont think it was causing any problems 2018-08-13 09:58:55 -04:00
Manevolent ca869089cf Reconnection works now 2018-08-13 09:48:30 -04:00
Manevolent 89c483d3b9 Fragments which wrap around 65536 and cause the packet ID to ascend more than once will crash the code 2018-08-13 09:20:27 -04:00
Manevolent aad790c146 Packet reassembly would fail if the server sent packets out of order. Now, it is resilient to this. 2018-08-13 01:03:44 -04:00
Manevolent 7d195439b8 Send a zero-length byte array when the audio thread is done sending audio, as Teamspeak does. this is to prevent interpolation 2018-08-12 15:39:55 -04:00
Manevolent fb7923b63b Change HighPrecisionRecurrentTask to 0.01 instead of 0.02 2018-08-12 15:13:21 -04:00
Manevolent 9d37b982d5 Packet fragmentation had a bug 2018-08-12 15:07:49 -04:00
Manevolent 69024381de It would help if I pasted it after a packet has its ID assigned wouldn't it? 2018-08-12 12:45:27 -04:00
Manevolent 555f6a56d6 Mic packet ID was wrongly generated, changed some tests and increased verbosity of the reassembly exceptions 2018-08-12 12:14:29 -04:00
Manevolent bc37491328 Created a new test for fragments. If a packet fragment is received which wraps around the generation, it is lost. Also, packet fragmentation outgoing would cause a desync in the packet IDs. 2018-08-11 18:44:44 -04:00
Manevolent 04299b5c77 More tests for packet generations. Compression test also exists now to test compression into the future. QuickLZ first checks the level on decompression, and also throws a diagnostic error with full Base64 byte array on issue. Disconnections will actually fully reset and free the client for valid re-use. There is now a Consumer for Throwables for the abstract client socket for error handling. 2018-08-11 15:50:22 -04:00
Manevolent 5a440c890f Round ping to nearest whole number 2018-08-11 12:36:37 -04:00
Manevolent 2666e940e8 Undo debugging stuff 2018-08-10 23:38:07 -04:00
Manevolent 7f6f6c79d2 Bitmasks were wrong 2018-08-10 23:37:45 -04:00
Manevolent 798f84689f get rid of JavaFX 2018-08-10 22:46:03 -04:00