selected_maps_bits: 4223639358
selected_maps_bits: 1797519182
selected_maps_bits: 0
(all played* 3 games from upward)
so it appears it might be tracking loaded areas* or something akin to that at the end of a map/game? Our bud who provided the file left the 3rd game midway (casual servers, not community).
selected_maps_bits: 318767360
selected_maps_bits: 167777024
selected_maps_bits: 0
(one game on harvest)
selected_maps_bits: 2151948288
selected_maps_bits: 2690566289
selected_maps_bits: 29360128
(Abandoned game of degroot keep)
selected_maps_bits: 1208027196
selected_maps_bits: 16900100
selected_maps_bits: 0
(abandoned koth_king)
No fucking clue what this is for now. Maybe its recording the previous/last game then taking that into effect on top of your elo?
Selected_maps_bits: 0 (the last line) seems to be the exact thing thats causing a crash. the github link from OP only shows repeated fixed32 selected_maps_bits = 3; that under tf_gcmessages which seems to do something
random thoughts: Its an elo/rank modifier or cleaning up how it presents values? having replaced this stuff, no clue as to the insanely high value though.
everything is irrelevant.
My casual_criteria.vdf was empty until I checked off maps I wanted to play in casual mm. Didn't even play a game, just checked them off, started/ended a search.
Oh well, fix is on the way regardless
Squidamatron provided the tidbit.