Sundered. I would love to see the equivalent of Rogue Legacy 2 for that game, where the sequel completely supplants the original while expanding upon the storytelling and lore.
Hashing is more about obscuring the password if the database gets compromised. I guess they could send 2256 or 2512 passwords guesses, but at that point you probably have bigger issues.
It doesn't matter the input size, it hashes down to the same length. It does increase the CPU time, but not the storage space. If the hashing is done on the client side (pre-transmission), then the server has no extra cost.
For example, the hash of a Linux ISO isn't 10 pages long. If you SHA-256 something, it always results in 256 bits of output.
On the other hand, base 64-ing something does get longer as the input grows.
To follow on to this, the "best" build may not be the best for you and how you play. Try out various things to see what feels right to you. Sword and board, magic, gish, dual wield, big two hander, bigger two hander, etc. All of them are viable to beat the game, so find the one you like the most/is easiest for you.
Perhaps the solution is to figure out how to update without restarting. It is a hard problem, but a forced restart is the same as a crash from a user perspective.
Sundered. I would love to see the equivalent of Rogue Legacy 2 for that game, where the sequel completely supplants the original while expanding upon the storytelling and lore.