search

Razviar / mtgap

Support tool for MTG Arena online game
https://mtgarena.pro/
219 stars 50 forks source link

Question: The tracker fails to detect the MTGA connected user #301

Open MAC-GH opened 2 years ago

MAC-GH commented 2 years ago

Hello,

Still don't understand why you closed the issue #290 which was covering 2 problems: a connected user detection problem and a manual parsing problem (which I believe is at least in part a consequence of the user detection problem).

Most of the time I start the tracker before the MTGA but when the tracker started to fail to detect the connected user I've sometimes started it after MTGA (or not started at all during the gameplay) and this kind of use case may be present in the submitted log file.

Given that the MTGA creates a log file per user and that the log clearly indicates when a user connects/disconnects confuses me and makes it hard to understand why the tracker fails detect the user which ultimately defeats the purpose of the tracker.

Could you please give some more details about the user detection ?

Thanks and regards

MAC-GH commented 2 years ago

Also, it would be nice to be able to label some issues as questions instead of the default bug or enhancement.

Razviar commented 2 years ago

Hello! Like I explained in the previous answer, we use injection which modifies log output. We don't rely on the line "[Accounts - Login] Logged in successfully. Display Name: Pufuletz#40518", we search for our own output in the log, which is marked with "[MTGA.Pro logger]" mark. Why don't we use the game's standard output? Well, there's several reasons. First of all - WOTC messed it up several times. And they keep messing it up over and over again, so I decided to let it go and rely only on the output we 100% control. Second - there's no User ID in that output, only screen name. And we need ID, so we use injection to get both screen name and user ID in one line. So when the game session was played without our tracker running, you can't parse the old log, since there will be no injection marker.

Multiple accounts support has been a weak spot for our tracker since the first versions. We made numerous attempts to fix it, but it's harder than it looks. No matter how we fix it, data from different accounts is still getting mixed up and messed up. I can't provide any ETAs and guarantees that multiple account support will be fixed.