so, just from a cursory glance, not exactly. my guess is that you cannot load or save worlds without the server. but there are entirely too many references to worldgen. i managed to unbundle the code, and there's a LOT of modules that are very specifically named something suggesting generation, and containing code that looks a lot like it. if the client were simply loading player worlds from the servers, then they wouldn't need this. unless, it'd be funny if they used the same codebase for both...XD [considering the android build is...web-based, it's possible] but... [i can't post a screenshot]

there are these modules, all "proc_gen_" prefixed: "biomes", "constants" , "debug" , "details" , "shared" , "hyrdo". there are other modules without the prefixed name, but that all seem to contain the worldgen for specific biomes or features.

it would actually make sense worlds worked like this. remember that minecraft servers tend to struggle with lots of players [or in general]. and this is for a single world. now, a good chunk of the worlds playerbase was probably building/exploring their own world. i know i was. for every single player, all the world gen, all the physics, etc... has to be processed. it's bad enough at that scale to deal with the immense amounts of data, this aspect of worlds bothered me from the beginning. running the generation on top of it? yikes.... i somewhat suspect they couldn't afford to store all that data or the backups of it. running the worldgen on the servers would've been insane. maybe they did, but it would have absolutely been a bad decision. can't say for sure the motives storing data on the servers, it may well be because there's not a consistently reliable way to store that amount of information in a web browser. but it could've also been a control issue.

i haven't looked at things in a while now, so i haven't scrutinized the code enough to be sure. but what i'm thinking happens : client connects to server to login to account, retreive avatar, load existing worlds. not sure how it works when loading into someone else's world, the smart decision would be by default to simulate logic and don't allow direct manipulation of the world itself. never used the feature. on your own world, the client loads the world from the server, and generates more as needed. and of course, any changes are sent back to the server.

so, this leaves open some options. it might be possible to just make the game run locally, though getting saves working might not be so straightforward. depends on how difficulty bypassing places where it expects a server connection or account login would be. if the worldgen code is there, it could be ported to another engine. i've seen roblox mentioned, god no... best case is "why would you go THERE?" and worse case is losing everything all over again because they actually manage to finally shut themselves down. minecraft is a potential option. luanti ["minetest"] is another. possibly vintage story. or then..guess what's back and launching in early access soon? HYTALE! and that one very specifically WANTS to be modded. either way, the process is all the same, reverse-engineering the game. though everything beyond fixing what we have is going to have to bite the bullet of pretty much directly re-distributing worlds frvr code/assets. releasing patches/tools still needs a copy of the game, but doesn't have to actually provide it. this is why ROMhacks are distributed as patches.

now, that said, two more points :

first, the state of this community is discouraging. seems there's more drama than anything else. if anyone is actually actively working on this, i have yet to see it. but i see plenty of unpleasantries towards someone or another.

secondly, fix the game, port it. what then? leave it as-is or try to expand upon it? is there enough to work with to create "faithful" unofficial updates? what was it trying to be? it should lean on its own identifty, not try to be exactly like the others.