Community Forums > Voobly Support and Game Complaints Support > Client and Website related Problems and Questions > recorded game section seems to be "bugged"
[1]
Displaying 1 - 2 out of 2 posts
1 User(s) are reading this topic (in the past 30 minutes)
0 members, 1 guests
0 members, 1 guests
What's popular right now:
Word Association (78 users)
Photos of Voobly Players (40 users)
CBA PathBlood 1.8.0 (38 users)
Torneo 1v1 HUMAITA / HUMAITA 1... (32 users)
New Voobly Client 2.7 (32 users)
TIW 2020 Map votes (28 users)
AoKTS updates (26 users)
Most active threads in past week:
Torneo 1v1 HUMAITA / HUMAITA 1... (34 posts)
🌟 Let's Restart Custom Scenar... (24 posts)
If there is chance to advertise ... (8 posts)
AOM Error "Unsupported Grap... (5 posts)
Which AI can play DE Islands cus... (4 posts)
Voobly Rouge Spear on Mac (4 posts)
Hero Tourney Match Schedules (3 posts)
i have a concern that most probably matches ALL voobly players.
it is regarding the "recorded games" of everybody.
I have had that issue now in 2 games of 3, where i played myself a game and after that, wanted to see the record of that game (through downloading it by voobly).
BUT it was the wrong record.
let me explain:
at both of that games which stand in the voobly recordings-list as existing, you will find another recorded game. and that "another" recorded game is in both cases a game which was broken up minutes before (right in the beginning) because of too much lagg or fast proxys. so instead of finding the game which is listed in the voobly recorded games section, you find the game which was just broken up (the one game earlier).
For example to understand that matter better (take my site (aox) -> "matches"):
look at the game i played on 26 October on 11:24 pm
that was a 3vs3!
then open the match (to see concrete data´s and download ability) and you will see then that there is listed a completely wrong game (the one we played before and broke up), a 4vs4.
i think thats a generell voobly problem. a bug or an error.
are you aware of that?
greetz!
Thanks for the information - we are aware of the issue and it is currently on our 'to do' list.