Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some hunts are not logged after latest patch #63

Open
Forien opened this issue Jun 28, 2023 · 5 comments
Open

Some hunts are not logged after latest patch #63

Forien opened this issue Jun 28, 2023 · 5 comments

Comments

@Forien
Copy link

Forien commented Jun 28, 2023

Played two hunts since the patch.

Both were Rotjaw Wildcard ones.

  1. First one we killed the Scrapbeak and 5 players, as well as took someone's Rotjaw Bounty, we also used the altars etc. Logger correctly showed HD, XP, EP, kills and estimated MMR change
  2. Second hunt we found Rotjaw, didn't kill anyone and left the contract with Bounty. Logger didn't notice the new hunt and shows "33 minutes since the last hunt". My guess is, it found something unexpected while parsing and broke

Logs:

1687981354	launching app
1687981355	clean_data
1687981355	'blood_line_name'
1687981355	building json error, trying again
1687981355	'game_id'
@majikat768
Copy link
Owner

That's happened before, a lot of the time after a big patch, they change some properties that I'll need to add in. I'll take a look at it later today.
Thanks!

@Forien
Copy link
Author

Forien commented Jun 28, 2023

@majikat768 I am pretty sure it's only happening when you or your team personally kill Rotjaw. I could send you the attributes file if you want them

@majikat768
Copy link
Owner

So I played for a while and got that same error message a couple of times, but it appears that all of my hunts were logged...I'll keep looking though. I have seen that error before, but it seems more frequent now.

@majikat768
Copy link
Owner

I've had a few now that haven't been logged as well...it doesn't seem to have to do with the new patch specifically, though. I'll have to do a bit of investigating

@majikat768
Copy link
Owner

I may have found the issue,
sometimes in the attributes file, the value for 'blood_line_name' is an empty string, which seems to break it. I've added a step to replace an empty string with a generic value and it seems to be working better....I'll do some more testing to see.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants