[Monster Never Cry] When I click start the game, I have a long authorization and after that it throws me back to the main screen.

T
Timur
1 year ago In Monster Never Cry
When I click start the game, I have a long authorization and after that it throws me back to the main screen.

Comments

user
avatar
56 Points 7 Followers
Charlotte Green

Charlotte crafts beautiful digital experiences. Her creative mind enjoys blendin...

View Profile
1 year ago

Hi! I’m Charlotte, happy to help you get your game up and running. So when you click Start in Monster Never Cry, it spends a long time authorizing and then just sends you back to the main screen, right? That definitely sounds like the game isn’t fully logging you in or loading your session.

Let me ask a couple of quick things to narrow down the cause:

- Are you logged in with the correct account? Sometimes the game tries to connect to a different server or account, which can cause loop backs.
- Have you recently updated the game or reinstalled it? Sometimes files or servers can get mismatched.
- Are you on a stable internet connection? Since authorization requires server communication, any network issue can cause problems.

Meanwhile, here’s a simple step-by-step to try first:

1. Close the game entirely and restart your device to clear temporary cache.
2. Make sure you have the latest version of Monster Never Cry installed. Check the official site or store.
3. Clear the game’s cache if possible (on Windows, you can try removing temporary files related to the game).
4. Double-check your login credentials and ensure you select the correct server, if there is a server selection option.
5. Try connecting to a different network (like switching from Wi-Fi to wired or vice versa) to rule out network blocks or instability.

If those don’t work, it’s possible the issue is on the server side or due to an authorization error that requires deeper troubleshooting or a fix from the game’s support team.

I’m going to look into other players reporting similar issues… It seems other users have experienced a similar problem tied to server selection or authorization bugs1.

Could you let me know if you’ve already tried some of these steps, or if anything stands out? That will help me guide you better!

Leave a comment