I just checked, HereAuth is supposed to be able to read SimpleAuth accounts. You should be able to cut and paste all of the account files.
Also note that PiggyAuth has added support for importing data from SimpleAuth or ServerAuth. As the original author of HereAuth [citation needed], I don't recommend using HereAuth anymore. PiggyAuth covers most features offered by HereAuth.
I could have sworn that PeMapModder made it... If you say you did, this is reinforcing the theory that you are @PEMapModder #Conspiracy
"Importing other hashes" works by storing both the external algorithm and the external hash, validate it the first time the player joins, and if it is correct, delete the old hash and store the new hash normally. For instance: Spoiler SimpleAuth uses sha512^whirlpool (abbreviated as "sw" below) PiggyAuth uses blowfish (password_hash()) Say, normal PiggyAuth passwords are stored as "$(blowfish-hash $password)" When the data of Steve is imported from SimpleAuth into PiggyAuth, the password is stored as, say, "SimpleAuth: $(sw-hash $password)" When Steve logs in (only PiggyAuth is installed right now), PiggyAuth finds that a record of "Steve" exists in the database. When Steve inputs the password, PiggyAuth checks the password of Steve and finds that it is a SimpleAuth hash. Therefore, PiggyAuth uses the sw algorithm to hash Steve's password. It ends up that $(sw-hash $inputted_password) matches the record in the database. Therefore, Steve is authenticated. Since a foreign hash algorithm is considered "bad" (we don't want to support too many hashes in the database, and we hope to migrate all hashes as soon as possible, and usually we self-proclaim to be a better hashing algorithm when we migrate someone's else), PiggyAuth now hashes the password using blowfish. "$(blowfish-hash $password)" is stored instead of "SimpleAUth: $(sw-hash $password)". When all old accounts have been migrated in this way, there is no longer the need to support sw, so the old data are considered "completely migrated". But even if not all old accounts are migrated yet, it's not really a big deal HereAuth uses a poor encryption algorithm, same as that used by SimpleAuth. That's why it is not recommended.
Inventory is being buggy in HereAuth! like its not sending inventory contents directly you have to relog for that, why's that? can anyone fix that? @Muqsit @SOFe @Primus ?
It is not lag. It is a feature called "inventory masking". Again, on behalf of the author of HereAuth I discourage you to use it nor SimpleAUth, though