using trinity 2.13 and r-rift profile
[8b73abdf-362f-48b0-96cc-ac8726e27e2f] Now beginning to receive data.
[Trinity] Bot is Stuck! Attempt #1 to fix it
using trinity 3.0.6.24 and adventurer
[8edf1d86-bb9c-43bf-b994-c235a9946a63] Now beginning to receive data.
[402e7f80-dd33-4455-8988-1df9a434338a] Now beginning to receive data.
[Trinity] Stuck! Trying to Unstick!
[Trinity] Stuck! Trying to Unstick!
[d08e7673-13ea-4c51-85f8-5b1a48121e03] Now beginning to receive data.
i sniffed some packets to find out the navigation server and i cant understand where is the problem because the server response well
Ping statistics for 51.254.37.24:
Packets: Sent = 93, Received = 93, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 32ms, Average = 31ms
[8b73abdf-362f-48b0-96cc-ac8726e27e2f] Now beginning to receive data.
[Trinity] Bot is Stuck! Attempt #1 to fix it
using trinity 3.0.6.24 and adventurer
[8edf1d86-bb9c-43bf-b994-c235a9946a63] Now beginning to receive data.
[402e7f80-dd33-4455-8988-1df9a434338a] Now beginning to receive data.
[Trinity] Stuck! Trying to Unstick!
[Trinity] Stuck! Trying to Unstick!
[d08e7673-13ea-4c51-85f8-5b1a48121e03] Now beginning to receive data.
i sniffed some packets to find out the navigation server and i cant understand where is the problem because the server response well
Ping statistics for 51.254.37.24:
Packets: Sent = 93, Received = 93, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 32ms, Average = 31ms
Last edited: