Hoyolab Auto Daily Check In

Today's check in status:

Repository version:

Table of Contents

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

Getting your cookie

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

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.

   Writing the line in the browser URL bar makes it easier. Pay attention: use a semicolon (;), not a 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!

Usage

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

Multiple Accounts

To add other accounts, you can add another cookie and games in a new line like below.

Language

Check in requests are made in English (en-us) by default. The language decides how HoYoLAB localizes the check in, so the reward messages you see in game and in the check in history follow it.

To change it, create a new repository variable (Settings > Secrets and variables > Actions > Variables) named HOYOLAB_LANG with one of the values HoYoLAB supports:

zh-cn, zh-tw, de-de, en-us, es-es, fr-fr, id-id, it-it, ja-jp, ko-kr, pt-pt, ru-ru, th-th, tr-tr, vi-vn

Leaving the variable unset keeps the current en-us behaviour.

Discord Webhook

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. (Optional) If you want to be tagged on check in, add `DISCORD_USER` variable with your Discord ID.

   

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

Telegram

You may use a Telegram bot to send notifications to yourself or a group.

1. Open @BotFather in Telegram, send /newbot, and follow the prompts. It gives you a bot token like 123456789:AAE...
2. Start a chat with your new bot and send it any message (the bot can't message you first).
3. Get your chat ID: open https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates in your browser (replace <YOUR_TOKEN>) and copy the number in "chat":{"id":...}. For a group, add the bot to the group first, then read the group's negative chat ID from the same URL.
4. Add two repository secrets (Settings > Secrets and variables > Actions):
   • TELEGRAM_TOKEN with the bot token
   • TELEGRAM_CHAT_ID with the chat ID
5. Trigger the check in manually and see if the message arrives.

Discord and Telegram are independent — set up either, both, or neither.

FAQ

Is this safe?

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

How to update my (fork) repository version?

Go to your repository and click Sync fork

Error not logged in

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

I have other issues

To the Issues page