cargo build fails

[glass-ships]

$ cargo build
error: failed to load manifest for workspace member `/home/glass/dev/anotherland/tools/kismet-plotter`
referenced by workspace at `/home/glass/dev/anotherland/Cargo.toml`

Caused by:
  failed to load manifest for dependency `upk`

Caused by:
  failed to read `/home/glass/dev/anotherland/upk/Cargo.toml`

Caused by:
  No such file or directory (os error 2)

rustup 1.27.1 (54dd3d00f 2024-04-24) cargo 1.85.0-nightly (66221abde 2024-11-19)

[cseander]

I had the same problem but solved it by doing this:

Open D:\anotherland\tools\kismet-plotter\Cargo.toml.

Locate the line referencing the upk dependency: upk = { version = "0.1.0", path = "../../upk" }

Update it to: upk = { version = "0.1.0", path = "../../lib/upk" }

[glass-ships]

thanks @cseander that got the ball rolling! I've managed to build successfully after a few changes, but the documentation is... pretty bad. For example, anotherland isn't a command - is it an argument to another cargo command? cargo run returns:

error: `cargo run` could not determine which binary to run. Use the `--bin` option to specify a binary, or the `default-run` manifest key.
available binaries: cluster_router, core_service, dungeon_service, frontend_server, kismet-plotter, login_server, realm_manager_service, world_service

it's not clear what to ... do after building

[plehmkuhl]

Hey! Thank you for your interest in this project :) Currently I'm doing a major restructuring of the project, that's why it currently fails to build, is not really doing anything useful and the documentation is lagging behind.

If you are interested in running your server locally, you could use the docker image that is already compiled or checkout the tag https://github.com/AnotherlandServer/anotherland/tree/v0.1.1

Then, the documentation should match again.

Let me know if you have any issues :)

[glass-ships]

Ahh nice, ok! I'll give the Docker image a shot for now - quick question, will I need to mount any local volumes to the container? I'm assuming the commands like init-db and standalone-server will be run within the container

[plehmkuhl]

No, the container itself doesn't require a volume. But you need to provide a mongodb instance. You can then use the image to run init-db to seed the realm database.

What is also not mentioned in the docs currently is, that you need to create accounts using the exposed graphql api. GraphQL is somewhat selfdocumenting, so you can use graphiql exposed on port 3000 of the container to browse the api.

I'm also publicly hosting the server, which can be accesses as described in this reddit post: https://www.reddit.com/r/Otherland/comments/1cub7ot/anotherland_a_server_emulator_for_otherland/

Keep in mind, that this project is still very early. While the proof of concept is functional, a lot remains to be done :)

[glass-ships]

Would that be a local mongodb instance (i assume a port would need to be exposed to the container?), or could it be pointed to a cloud atlas instance of mongo?

Also, do you know if character progress is stored locally in the event your database gets reset or I switch over to self-hosting or some other event?

Apologies for all the questions, I appreciate your input and the effort you put into keeping this gem of a game alive!

[plehmkuhl]

As long as the mongo-uri is reachable from within the container it shouldn't matter. I've only tested locally running instances tho.

All progression is inherently tied to the servers database instance. But the only mode that is currently functional is the social mode, with not a lot of gameplay attached. You can visit the different maps via the main portal at lambda mall though.

Reimplementing the classes and quests is part of the ongoing research :)

[glass-ships]

Ahh ok ok. Awesome, thanks for the info! I'll mark this as closed, and eagerly awaiting further updates