ZZZ ASIA | MMC LV57+ YIXUAN+SIGN +FUFU+SIGN +MIYABI+SIGN +EVE+SIGN +TRIGGER+SIGN +YUZUHA +VIVIAN +BURNICE +2'WE'S +6'BANGBOO'S

Login to Hoyoverse (Gmail is set, username is not set) - MC Wise - Birthday not set - Pity banner and Bangboo rank S as shown in the screenshot (event character rate banner ON, weapon rate OFF) - Other details are as shown in the provided screenshots Screenshots of character build and mindscape: https://drive.google.com/drive/folders/1vSY4XRxLzmpjf8NuqMmLsp0ruFmlxxeS?usp=sharing The account will be automatically delivered within approximately 1 minute after payment. You can check it in the order menu (Home > Account > Shopping > Already delivered). How to log in: 1. Log in to the Gmail account that has been sent to you (website "mail.google.com" or the Gmail app on your phone. If phone verification is required, just enter your phone number). 2. Enter the game and input the email address and password as I sent. Then press "Log in". 3. Complete the captcha briefly and press "Get a verification" to have the verification code sent to the Gmail inbox from step 1. 4. Go to that Gmail, check the "inbox" or "all emails" to get the verification code, copy the code, and paste it into the game. 5. In the game, press "Next" and you will automatically enter the in-game account. Done. *To secure the password and Gmail, you can do so through the User Center in the game. In-game, open the HP menu (press ESC for PC, or the top-left icon on the mobile screen > Options > Account > User Center). Note: - If when changing the email, a notification appears saying "Too many requests/terlalu banyak permintaan", it means there is still a cooldown period for changing the email. You need to wait 1 to 3 weeks for the cooldown to expire. So, you can use the Gmail I provided and secure both the Gmail and Hoyoverse passwords. - If you request a code to change the email or password, but the code hasn’t arrived in the email inbox, wait for about 4-5 minutes. Do not immediately spam the resend button, as it may trigger an error/bug with the "Too many requests" notification.