Open dkstiler opened 3 years ago
destiny as a whole is being reviewed and updated/fixed as needed (by a real physicist, no less!!) this will require some time
Removing this from 0.8.5 milestone as it is part of the overall destiny_rework initiative and therefore will both take time and will require additional resources.
Describe the bug When you initiate a custom warp or predefined kms to gates and stations and you always end up on the double distance of the km range you selected. For example if you select 100 Km to a station you will end up on 200 Km. Thats on client side. If we use .update commands we would end up in the correct location. Need to check the actual client server sync issue
To Reproduce Steps to reproduce the behavior:
Expected behavior You should arrive at the exact km you specified when you selected the warp range.
System Details (please complete the following information):
Additional context This does not affect the warp to zero obviously. The log server capture log was: