Client rendering crash involving the Everbook when joining HexKeys Mindscape

[Twisted-Code]

When trying to enter hexkeys:mindscape from The Nether, a player on the server encountered a recurring client crash for which the stacktrace implicated Hexal's FileEncrypterDecrypter in the everbook api. Specifically, the stacktrace seemed to imply that the user's everbook file could not be decrypted because the padding didn't make sense for the given key. I suggested that the player should rename the Everbook folder (it had no important data anyway, in this case at least) and that seemed to fix the problem, somehow. Currently my most prominent question is "how did this come about from simply changing dimensions? We change dimensions all the time, but this specific case breaks the everbook?". Is there something HexKeys might be doing to its dimension that changes how the Everbook decryption key is computed? :concern: Crash report: crash-2024-07-23_02.48.41-client.txt "Broken" everbook data: everbookbugged.zip

[ChloeTax]

is this a networking issue? where the client didn't send their whole everbook contents to the server? this is pretty weird, but i've had my everbook stop working in the past from dying/ maybe changing dims? (i'm sure dying could cause it) until i relogged, so i've been using the grimore instead, so i wouldn't've noticed if this was an issue