Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unknown Message Types #58

Open
spheenik opened this issue Sep 13, 2015 · 169 comments
Open

Unknown Message Types #58

spheenik opened this issue Sep 13, 2015 · 169 comments

Comments

@spheenik
Copy link
Member

spheenik commented Sep 13, 2015

Thank you for reporting an unknown message type.

Please note: In case clarity detects an unknown message, it reports this with the warning, but will be able to skip over the message and successfully parse the replay. This means that if you have an exception, there is another problem, and I suggest you open a new issue.

@Decoud
Copy link

Decoud commented Sep 17, 2015

Match ID: 1782181262
Running clarity-examples tick package. Happens on many ticks:

tick 57378, synthetic true, had 0 messages
unknown embedded message of kind SOURCE2/47. Please report this in the correspon
ding issue: #58
unknown embedded message of kind SOURCE2/47. Please report this in the correspon
ding issue: #58

@Decoud
Copy link

Decoud commented Sep 18, 2015

Same replay, I don't have the ticks but can get them if you want:

unknown embedded message of kind SOURCE2/497. Please report this in the correspo
nding issue: #58
unknown embedded message of kind SOURCE2/128. Please report this in the correspo
nding issue: #58

@spheenik
Copy link
Member Author

uploaded a new snapshot, which has all those...

@Decoud
Copy link

Decoud commented Sep 21, 2015

unknown embedded message of kind SOURCE2/510. Please report this in the correspo
nding issue: #58

@spheenik
Copy link
Member Author

new snapshot uploaded

@Decoud
Copy link

Decoud commented Sep 22, 2015

What type of messages are these things?

unknown embedded message of kind SOURCE2/62. Please report this in the correspon
ding issue: #58

@howardchung
Copy link
Contributor

My guess is that @spheenik tried to remove as many of the messages from the generated Java classes as possible to reduce code size and speed up compile times.

@spheenik
Copy link
Member Author

@howardchung: correct.

@Decoud:
62 is svc_UserMessage...
In S1, UserMessages had their own container, in S2, they were, until now, encoded as Embedded Messages. The latest protobufs on SteamKit do not have the message definition (yet). Someone has to extract it from the client. I'll look into it tonight...

@manveru
Copy link

manveru commented Sep 23, 2015

@spheenik latest protobufs are always available at https://github.com/SteamDatabase/GameTracking/tree/master/Protobufs/dota

@howardchung
Copy link
Contributor

+1 for GameTracking :)

@spheenik
Copy link
Member Author

@manveru: thx!

So, their netmessages say that it's CSVCMsg_HLTVStatus. I'll release a new protobuf snapshot tonight...

@spheenik
Copy link
Member Author

new snapshot uploading as I type...

@Decoud
Copy link

Decoud commented Oct 11, 2015

SOURCE2/554

@howardchung
Copy link
Contributor

I think this is the new CombatLogDataHLTV. @spheenik added support for it last night, try updating your snapshot?

@Decoud
Copy link

Decoud commented Oct 12, 2015

Works fine, my bad. Should have checked for the update first. Will have to take a closer look at some of those combat log changes.

@spheenik
Copy link
Member Author

@Decoud: have a look at the comments in issue #61 for info on what changed.

@1zb
Copy link

1zb commented Oct 19, 2015

kind 534 or 544

file name: frankfurt_major\1856290165_1750727379.dem
unknown embedded message of kind SOURCE2/534. Please report this in the corresponding issue: #58
league id: 3671
total time taken: 0.158s

file name: frankfurt_major\1858282173_1016472045.dem
unknown embedded message of kind SOURCE2/534. Please report this in the corresponding issue: #58
unknown embedded message of kind SOURCE2/534. Please report this in the corresponding issue: #58
unknown embedded message of kind SOURCE2/534. Please report this in the corresponding issue: #58
unknown embedded message of kind SOURCE2/534. Please report this in the corresponding issue: #58
unknown embedded message of kind SOURCE2/534. Please report this in the corresponding issue: #58
league id: 3671
total time taken: 0.535s

file name: frankfurt_major\1859146913_1174254792.dem
unknown embedded message of kind SOURCE2/534. Please report this in the corresponding issue: #58
unknown embedded message of kind SOURCE2/534. Please report this in the corresponding issue: #58
league id: 3671
total time taken: 0.582s

file name: frankfurt_major\1860271085_922706473.dem
unknown embedded message of kind SOURCE2/534. Please report this in the corresponding issue: #58
league id: 3671
total time taken: 0.601s

file name: frankfurt_major\1861004655_314559210.dem
unknown embedded message of kind SOURCE2/534. Please report this in the corresponding issue: #58
league id: 3671
total time taken: 0.511s

file name: frankfurt_major\1861405896_2145933448.dem
unknown embedded message of kind SOURCE2/544. Please report this in the corresponding issue: #58
unknown embedded message of kind SOURCE2/544. Please report this in the corresponding issue: #58
league id: 3671
total time taken: 0.321s

file name: frankfurt_major\1861422181_1394172680.dem
unknown embedded message of kind SOURCE2/534. Please report this in the corresponding issue: #58
unknown embedded message of kind SOURCE2/534. Please report this in the corresponding issue: #58
league id: 3671
total time taken: 0.213s

@spheenik
Copy link
Member Author

Hi, thx for reporting!

Deployed a new snapshot of clarity protobuf that has 534,

The 544 is the new combatlog - I already included it a week ago. So it seems your snapshots are not up to date. mvn -U ... should do the trick.

@spheenik
Copy link
Member Author

Bullshit - 544 was new too - added.

@howardchung
Copy link
Contributor

unknown embedded message of kind SOURCE2/557. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58

According to proto definition appears to be some kind of match metadata. Type is bytes so it's probably binary encoded in some way.

@spheenik
Copy link
Member Author

I have a fix, but I cannot test it.
Can you provide a D/L link to a replay?

@howardchung
Copy link
Contributor

@spheenik
Copy link
Member Author

Thx, will push a fix tonight.

@spheenik
Copy link
Member Author

Fix is out.

@howardchung
Copy link
Contributor

unknown embedded message of kind SOURCE2/558. Please report this in the corresponding issue: #58

(lower priority, I don't think this crashes the parser)

@TodorovicF
Copy link

I also got the same error as @howardchung

unknown embedded message of kind SOURCE2/558. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58

It seemed to have ran alright, no errors, though it does seem like it took longer to complete.

@spheenik
Copy link
Member Author

spheenik commented Apr 2, 2016

added 558 (S2DotaGcCommon.CMsgDOTAMatch) which contains a lot of detailed information about the match.

@PatheticNeatness
Copy link

Can you help me with

18:36:10.003 [clarity-runner] WARN  s.c.p.reader.InputSourceProcessor - unknown usermessage message of kind SOURCE1/15. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58
18:36:10.003 [clarity-runner] WARN  s.c.p.reader.InputSourceProcessor - unknown usermessage message of kind SOURCE1/27. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58

@spheenik
Copy link
Member Author

added those 2 with this commit and pushed a new snapshot.

@TodorovicF
Copy link

I've been getting crashes lately with this code:

unknown top level message of kind SOURCE2/1171. Please report this in the corresponding issue: #58

Exception in thread "clarity-runner" java.lang.ClassCastException: java.io.IOException cannot be cast to java.lang.RuntimeException
    at skadistats.clarity.event.Event.raise(Event.java:25)
    at skadistats.clarity.processor.runner.AbstractRunner.runWith(AbstractRunner.java:78)
    at skadistats.clarity.processor.runner.ControllableRunner.access$1401(ControllableRunner.java:13)
    at skadistats.clarity.processor.runner.ControllableRunner$3.run(ControllableRunner.java:208)
    at java.lang.Thread.run(Unknown Source)

@darrensapalo
Copy link

darrensapalo commented Jan 11, 2023

Detailing the above details here: faq

I too am experiencing the above mentioned issue:

unknown embedded message of kind SOURCE2/154. 
Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58

Using git repo: clarity-examples @ commit
Clarity version: 2.7.5 commit

with replay ID: 6963982486.dem, but as @spheenik explained above, he still needs to (1) extract the new protobuf definitions and (2) tweak the definitions to enable backwards compatible replay parsing.

Let me know if I misunderstood anything 🙇

@Whoeza
Copy link
Contributor

Whoeza commented Jan 11, 2023

Detailing the above details here: faq

I too am experiencing the above mentioned issue:

unknown embedded message of kind SOURCE2/154. 
Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58

Using git repo: clarity-examples @ commit Clarity version: 2.7.5 commit

with replay ID: 6963982486.dem, but as @spheenik explained above, he still needs to (1) extract the new protobuf definitions and (2) tweak the definitions to enable backwards compatible replay parsing.

Let me know if I misunderstood anything 🙇

Thank you for starting the wiki! I did not know if we were allowed to do it.
About your understanding, that's what I got as well.

@spheenik
Copy link
Member Author

New protobufs have been released.

Added
SOURCE2/114 (CUserMessageRequestState)
SOURCE2/154 (CUserMessageServerFrameTime)
SOURCE2/496 (CDOTAUserMsg_SwapVerify)
SOURCE2/499 (CDOTAUserMsg_ItemAlert)
SOURCE2/531 (CDOTAUserMsg_PlayerMMR)
SOURCE2/562 (CDOTAUserMsg_KillcamDamageTaken)
SOURCE2/608 (CDOTAUserMsg_AghsStatusAlert)
SOURCE2/616 (CDOTAUserMsg_DuelOpponentKilled)
SOURCE2/617 (CDOTAUserMsg_DuelAccepted)

My testing capability was limited, since downloading replays through the client seems buggy atm. (Opendota also does not work).

Regarding the Wiki Thing:
Doing a FAQ there is probably really a good thing. @darrensapalo Mind if I change your entry to properly explain this?

@spheenik
Copy link
Member Author

Oh, and, the protobufs contain several extra combatlog properties. If you want to use them, I released clarity 2.7.6. Pushed both artifacts to central five minutes ago, so might be an hour or so before you see them.

@darrensapalo
Copy link

@spheenik Please do! I'll follow your lead on the docs. Thanks spheenik!

@p0d3x
Copy link

p0d3x commented Feb 8, 2024

unknown top level message of kind CSGO_S2/16

also no decoder for class CCSPlayerController at 19/11! since the update today

@lochetti
Copy link

Not sure how to be more helpful, but I got a
WARN clarity.runner - unknown top level message of kind CSGO_S2/16. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58

I was trying to parse the first map of this game https://www.hltv.org/matches/2370928/liquid-vs-faze-iem-chengdu-2024
Using the version 3.0.3

@BusyLivingDota
Copy link

unknown top level message of kind CSGO_S2/16. Please report this in the corresponding issue: #58
on tick 152 of the cs2 replay:
https://www.hltv.org/matches/2370727/faze-vs-natus-vincere-pgl-cs2-major-copenhagen-2024
map-3-Inferno

@spheenik
Copy link
Member Author

spheenik commented Apr 17, 2024

Thank you guys, CSGO_S2/16 noted, I'll put updating the protobufs to my not so small list of todos.

@spheenik
Copy link
Member Author

CSGO_S2/16 and CSGO_S2/17 fixed in protobuf release 5.2.

@thwonghin
Copy link

Got an error parsing furia-vs-ninjas-in-pyjamas-m1-ancient.dem from this match
https://www.hltv.org/matches/2372732/furia-vs-ninjas-in-pyjamas-yalla-compass-2024

unknown embedded message of kind CSGO_S2/76

@spheenik
Copy link
Member Author

Thanks for reporting, as long as the parsing process didn't crash, it's fine.
I'll come around to updating the protobufs some time.

@darrensapalo
Copy link

Thanks for reporting, as long as the parsing process didn't crash, it's fine. I'll come around to updating the protobufs some time.

Hey Martin @spheenik! When you do plan to do it- Would it be possible for you to record your process? I'd like to learn and document the process in the FAQ so others can potentially contribute in the protobuf parsing. You don't need to explain everything step by step- just dropping specific keywords will be enough for me to do my own research to be able to do it myself.

If this is inconvenient to do- no worries. I just want to express my gratitude for your work! Thank you!

@ndorigatti
Copy link

Got an error parsing furia-vs-ninjas-in-pyjamas-m1-ancient.dem from this match https://www.hltv.org/matches/2372732/furia-vs-ninjas-in-pyjamas-yalla-compass-2024

unknown embedded message of kind CSGO_S2/76

got the same error, but the parser crashes. I'm just trying to seek to "getLastTick" in order to get scoreboard

@spheenik
Copy link
Member Author

CSGO_S2/76, CSGO_S2/141 and CSGO_S2/154 have been added in clarity-protobuf 5.3.

@spheenik
Copy link
Member Author

@ndorigatti I just tested your replay, and it does not crash here in getLastTick() with clarity 3.1.0.

@ndorigatti
Copy link

@ndorigatti I just tested your replay, and it does not crash here in getLastTick() with clarity 3.1.0.

Yeah it was not in that furia replay, was one of mine... I will try again, but don't know how to share that 300mb replay

@spheenik
Copy link
Member Author

@ndorigatti I have a hunch that self recorded replays do not properly encode the last tick.
Anyway, if you manage to upload it somewhere, open a new issue for it, because this issue here is for unknown message types.
Cheers.

@thurd
Copy link

thurd commented Sep 23, 2024

Dota 2. Match ID: 7888568761

I get the following message:
unknown embedded message of kind DOTA_S2/624. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58

Clarity seems to be up to date: api("com.skadistats:clarity:3.1.1")

@spheenik
Copy link
Member Author

@thurd fixed in clarity-protobuf 5.4

@any626
Copy link

any626 commented Oct 18, 2024

2024-10-17T23:49:17.997-07:00 WARN 38708 --- [ clarity-runner] clarity.runner : unknown embedded message of kind DEADLOCK/353. Please report this in the corresponding issue: #58
2024-10-17T23:49:18.184-07:00 WARN 38708 --- [ clarity-runner] clarity.runner : unknown embedded message of kind DEADLOCK/348. Please report this in the corresponding issue: #58
2024-10-17T23:49:18.371-07:00 WARN 38708 --- [ clarity-runner] clarity.runner : unknown embedded message of kind DEADLOCK/351. Please report this in the corresponding issue: #58
2024-10-17T23:49:19.860-07:00 WARN 38708 --- [ clarity-runner] clarity.runner : unknown embedded message of kind DEADLOCK/349. Please report this in the corresponding issue: #58
2024-10-17T23:49:20.608-07:00 WARN 38708 --- [ clarity-runner] clarity.runner : unknown embedded message of kind DEADLOCK/352. Please report this in the corresponding issue: #58
2024-10-17T23:49:24.878-07:00 WARN 38708 --- [ clarity-runner] clarity.runner : unknown embedded message of kind DEADLOCK/350. Please report this in the corresponding issue: #58

@vsmykalov
Copy link

Dota 2. Match 8056728116

unknown embedded message of kind DOTA_S2/570. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58

@MaverickMSG
Copy link

MaverickMSG commented Dec 20, 2024

Deadlock match 30739042 downloaded from http://replay272.valve.net/1422450/30739042_2038137483.dem.bz2:

unknown embedded message of kind DEADLOCK/353. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58
unknown embedded message of kind DEADLOCK/348. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58
unknown embedded message of kind DEADLOCK/309. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58
unknown embedded message of kind DEADLOCK/351. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58
unknown embedded message of kind DEADLOCK/356. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58
unknown embedded message of kind DEADLOCK/357. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58
unknown embedded message of kind DEADLOCK/349. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58
unknown embedded message of kind DEADLOCK/352. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58
unknown embedded message of kind DEADLOCK/350. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58

@dellis23
Copy link

Deadlock match 25917978

unknown embedded message of kind DEADLOCK/353. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58
unknown embedded message of kind DEADLOCK/348. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58
unknown embedded message of kind DEADLOCK/351. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58
unknown embedded message of kind DEADLOCK/349. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58
unknown embedded message of kind DEADLOCK/352. Please report this in the corresponding issue: https://github.com/skadistats/clarity/issues/58

@dellis23
Copy link

@MaverickMSG Can I ask how you got that direct download link?

@Noxville
Copy link
Contributor

@dellis23 you can generally work (in Dota 2 as well) from the metadata from the GC (i.e. something CMsgClientToGCGetMatchMetaDataResponse).

In the example of http://replay272.valve.net/1422450/30739042_2038137483.dem.bz2:

  • 272 is the cluster
  • 30739042 is the match_id
  • 2038137483 is the replay salt

@dellis23
Copy link

@Noxville Thanks! I assume GC is some sort of API I have to hit first for a given match ID?

@Noxville
Copy link
Contributor

It's the game coordinator. It's how the game client talks to the server, using protobuf encoded messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests