Open mellowagain opened 7 years ago
Commit d055083 reverted the change in that commit, it will be re-done.
is 1.4.0 still working? I do not got an error but I think the guy did not went into OW.
Commit dbd64a5 contains bugs that prevent reporting.
Commit d055083 reverted the change in that commit, it will be re-done.
what to do? change ' Titan/Managers/AccountManager.cs'? I will clone the full package and copy accountmanager.cs into my old Titan-folder?
sry for my stupidity & big thanks for help
from ger,too
This has to do with the latest source code release, this issue is currently the "waiting" issue for the suggestion to implement
Version 1.4.0 and prior are working. Latest release built from source code is working.
Please keep in mind that you can only report players with bot accounts that haven't reported anybody in the last 12 hours. If that was the case, the victim got surely into Overwatch but wasn't convicted.
Thanks for this fast awnser!
I had some problem with steamGuardMail, maybe the 2 guarded accs did not reported. Email-code worked but it did not send a report. Maybe I was too stupid and had to create a folder in the sentry-folder for accounts with steam-guard enabled?
I swapped steam-guard to off and all 11reports were commited.
great work btw :)
This issue is known and is being tracked in #8, as for now I suggest generating the sentries
on Linux (where it works for some reason) and moving them to Windows if you are required to use SteamGuard.
I am fine with guard->off :)
12 hours cooldown not 8?
I got no error for reporting. Is there an output-msg if the cooldown is up? I know i can check last report-date in log-folder^^
You will not receive a message if the cooldown isn't over yet except a warning in the console that its botting with a cooldowned index.
Valve will also send confirmation ID's (like Ingame, you can report another person right after one but it won't count towards Overwatch), which is in my opinion misleading.
Hi,
Are you having any problems with sending reports right now? I sent reports 24 hours ago without any problem, but I can't get any confirmation ids at this moment. Is there something wrong with Steam or am I on a long cooldown lol?
OS: Windows 10 Version: Latest commit
@Weeeishy You can check the SteamStatus website to see if CS:GO Game Coordinator and Steam Community are online. Does it work now (after these 7 hours)
Huh that's odd, seems like it's working now after 36 hours. PS: I checked SteamStat.us before commenting and the CSGO game coordinator was fully functional.
Thanks!
EDIT: Seems like not all of the indexes sending reports confirmation ID, 2 out of 3 showed that its trying to send the report but it times out. I'll try again in the morning.
It looks like its more of a problem with Steam than with Titan. Always check SteamStatus before commenting on a issue or opening one.
@123top I'll be tracking your suggestion in this issue.
@raspbianlike Updates / ETA on this?
i disagree, i worked on some api shit but no eta yet
Description
Commit dbd64a5 contains bugs that prevent reporting.
System Information
Operating System: Linux, Windows Titan version: 1.4.0-DEV
EDIT: Reporting is now possible again.