You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our usual netcat captures are not going to work, will presumably require going back to tcpdump (which does UDP, yes, despite the name).
This is probably a very different protocol! Many doc updates likely!
I think the intention is that if we want to integrate "other stuff" With Artemis Cosmos, we can now do so using the built-in Python runtime, not reverse-engineer the network protocols and write unofficial clients, however there are several good use-cases where unofficial clients may still have value, EG some of the known Artemis 2 use-cases:
automation / bots to control the server itself (this may be better done with Python now?)
recording and archiving games for future archaeology
driving giant LED display boards with extra ship status screens
special-purpose unofficial clients like the Android Artemis Messenger
unofficial servers
proxies
Let the discussion commence! 😀
NN
The text was updated successfully, but these errors were encountered:
The UDP port 3100 traffic is the same server discovery protocol from 2.7
The UDP port 2010 has the real traffic,
I've done some initial tests, (up to but not including console choice) found some patterns. https://github.com/aiden-w-135752345/Cosmos-protocol
I'm going to continue identifying packet types in the order they appear.
Artemis Cosmos 3.0.6.2 Pre-Release Pre-Alpha is available! 😍
Initial discoveries:
netcat
captures are not going to work, will presumably require going back totcpdump
(which does UDP, yes, despite the name).Let the discussion commence! 😀
NN
The text was updated successfully, but these errors were encountered: