There is no need to install 2 versions. So far, no cases of ban are from ps alone so far. The client data is stored in the registry anyways, it doesn’t matter how much installs of the game you have, it will sync across unlesss you are installing CN version client. Just turn off proxy and remove version.dll and you are safe for official
#Two installations for official and GC?
distant tinsel
distant tinsel
version.dll is just patching to get you past error 4214 on private servers. Same for the opposite, you need to remove version.dll for official because otherwise you will get error 4214. It is stored in the root folder of the game. I am not sure if cultivation removes the file, but it does add it.
still wren
Cultivation removes the file, yes
Anything Cultivation would do to your game/files/computer, would also be reversed upon exiting the game
(apart from the "Wipe Login Cache" option)
cedar coral
There is literally 0 risk, the option is for paranoid people
Official simply sees the login as having a caching error and has you relogin
Also just to be sure, no passwords are saved on private. You can put anything at all in the password field every time and you will login. As long as there is a single character in the box, it succeeds
It would be much the same as putting in a wrong password
Basically your cached login is validated against the main server's info and if it doesn't match it sees that as being a login cache error - simply called "Cache error" iirc. Even in normal circumstances such an issue could be for any amount of normal reasons and there's no reason to believe it would trigger any problems, much like putting in a wrong password once doesn't throw any flags
Your cached login data is account username/password combo basically, there shouldn't be any uid associated with it in info sent to the main servers
When you're actually playing on private there is no data being sent to official, of course, and even in the case of cache issues mhy definitely doesn't care about investigating account login issues
I wouldn't waste the effort
Passwords aren't saved, validated, confirmed, anything of the sort. As long as the box has something in it then the login succeeds. A single character like "b" is enough
Yeah if you keep that true, all logins will fail and any accounts made with it will be unusable
It worked back when it was made, but due to changes in how logins are validated it doesn't work anymore for normal Grasscutter. There are alternate options that may still work, but it's not really worth setting up imo
Unstable was doing something with it, not sure what exactly. Grasscutter is open source of course, if you're particularly concerned about having validated logins - though there's not much reason for it - you can always look into implementing your own method or fixing experimentalRealPass.
https://github.com/Grasscutters/Grasscutter/tree/development/src/main/java/emu/grasscutter/auth
Though you may want to look at what unstable branch is doing with it first
No problem, and best of luck. Glad to be of help