Open nskylink opened 7 months ago
I am aware of this issue-- unfortunately, it appears that crytek has made some changes with the latest patch such that hunter data is no longer stored locally...which effectively means that my app will not work. Doesn't seem to be any way around it.
I'll update the repository's Readme shortly, as it seems like my app is pretty much going to be defunct now.
Don't be upset. I think this is some kind of temporary problem/bug. I noticed that if you delete this file and play 1 raid, it will be created again, but with the statistics of the last match before the doomsday update on February 14 :)
I am aware of this issue-- unfortunately, it appears that crytek has made some changes with the latest patch such that hunter data is no longer stored locally...which effectively means that my app will not work. Doesn't seem to be any way around it.
I'll update the repository's Readme shortly, as it seems like my app is pretty much going to be defunct now.
I want to express my sincere gratitude to you for this application. I myself had a desire to make it in Python (I’m a Linux administrator), but something simpler like the script of the same name. And you got a whole application. WELL DONE! I am proud of you)
Thank you! I appreciate it. I don't believe it's a bug, I feel like this may be intentional by crytek...but we'll see!
Thank you very much for the good work. I hope they'll change that again. I really liked your tool
@majikat768 I'll just take this chance to say thanks! Almost 1000 hunts tracked with your tool, I had a blast! The chart was really the killer feature for me. I hope it's just temporary, but if not, still great job, and such cool recent UI improvements ✌️
See reddit dicussion for reference.
I still have the extended logging parameters enabled, from when crytek called on the community to help solve some issues (+log_writetofileverbosity 4). It seems to generate a log file in
Sidenote: these logs are getting big (~100mb/hour) and I just deleted 44gb of old logs.
I assume the problem is in the source attributes.xml file itself. the information there does not change, but the file metadata changes. Please conduct an Invistigate to see if the problem persists for you.
The problem was noticed after the global maintenance on February 14th (event end date)