Good news, I managed to reproduce it and fixed the bug in 1.4.0. This will be updated sonly :)
WolverinDEV TeaSpeak Team Staff member Administrator Sep 5, 2019 #21 Good news, I managed to reproduce it and fixed the bug in 1.4.0. This will be updated sonly
Vafin TeaFanatic Sep 5, 2019 #22 WolverinDEV said: Good news, I managed to reproduce it and fixed the bug in 1.4.0. This will be updated sonly Click to expand... Can you release while release 1.3.6-3 with the fix since 1.4.0 is not ready yet?
WolverinDEV said: Good news, I managed to reproduce it and fixed the bug in 1.4.0. This will be updated sonly Click to expand... Can you release while release 1.3.6-3 with the fix since 1.4.0 is not ready yet?
WolverinDEV TeaSpeak Team Staff member Administrator Sep 5, 2019 #23 Its a good thing to think about, but its quite hard to switch back there. I'mm may give it later a try.
Its a good thing to think about, but its quite hard to switch back there. I'mm may give it later a try.
Vafin TeaFanatic Sep 6, 2019 #25 WolverinDEV said: Done there is a 1.3.6-4 Click to expand... Everything seems to work
WolverinDEV TeaSpeak Team Staff member Administrator Oct 14, 2019 #26 //Closed (Everything works now)