Today's check in status:

Repository version:

• Getting your cookie
• Usage
• Discord Webhook
• FAQ
  • Is this safe?
  • How to update my (fork) repository version?
  • Error not logged in
  • I have other issues

You have to check in manually first to get your cookie, follow these steps (click to open screenshot):

1. Open HoYoLAB and login if you haven't (obviously)

2. Open dev tool (Ctrl+Shift+I or right click > Inspect)

   
3. For Chromium users, click on the Application tab. If not found, click on the arrow.

   
   For Firefox/Gecko-based browsers, click on the Storage tab.

   
4. On the filter box, type v2. You might want to expand the dev tools to see clearly.

   
5. Find ltoken_v2 and ltuid_v2, click on them, and copy the value below.

   
6. Write ltuid_v2=PASTE_ltuid_v2; ltoken_v2=PASTE_ltoken_v2 like the screenshot.

   I write the line on the browser url to make it easier. Pay attention, use semicolon (;) and not colon (:)

   It should look like this: ltuid_v2=249806310; ltoken_v2=v2_CAISDG...

   

7. Copy that. That's your cookie, keep it save and do NOT share it with anyone!

1. Fork this repo

2. Open your fork repository

3. Go to Settings > Secrets and variables > Actions

   
4. Click on New repository secrets

   
5. Insert name with COOKIE and secret with your cookie, then click Add secret

   
6. Now for the games, go to Variables and click New repository variable

   
7. Insert name with GAMES and value with the game codes you want to check in, separated by space like the example screenshot.
   Supported values are: zzz, gi, hsr, hi3, tot

   
8. For the first day, you have to trigger this manually. Simply go HERE and click on Run workflow

   
9. Refresh the page, wait for 15-25 secs, and see if it ran successfully. You should now see the check in status on top of README.

   

10. You're set! Hop on your game the next day and see if you got the rewards

You may use Discord webhook to send notifications to your channel!

1. Go to channel settings

   
2. Go to Integrations and click Create Webhook

   
3. You can edit the name and picture freely, then Copy Webhook URL

   
4. Create a new repository variable named DISCORD_WEBHOOK with value of the webhook URL

   

5. You may trigger the check in manually and see if the messages got sent

There should be no issues, automated check-in exists for years and there hasn't been any reports about hoyo doing anything against it

Go to your repository and click Sync fork

This is a common issue even if you seem to get the cookies right. Here's another method to get your cookies:

https://gist.github.com/torikushiii/59eff33fc8ea89dbc0b2e7652db9d3fd

Just copy everything and paste to the COOKIE secret

To the Issues page