Description

Add paper support for Minecraft

Steps to reproduce (optional)

Intention:

Title.

Why is it necessary:

Trivial.

• #30
• #29
• #28
• #27
• #26

Intention:

Rocket has problems with CORS policy which need to be explicitly addressed.

Look into if Axum needs to be set up to avoid such issue, if so fix it.

Why is it necessary:

CORS broke the Rocket app before.

Description

Currently the core downloads and invoke 7z to handle zipping and unzipping. This is not ideal for multiple reasons.

Rewrite the unzipping logic to use libraries.

https://rust-lang-nursery.github.io/rust-cookbook/compression/tar.html

https://github.com/google/ripunzip

https://github.com/muja/unrar.rs

Description

Add restart functionality to server instances

Steps to reproduce (optional)

Intention:

CI does not run any test right now. CI should run cargo test before running cargo run. CI should fail if cargo test fails.

Why is it necessary:

Tests should be part of the CI process for more rigorous verification.

Intention:

• Add a new global setting "hostname"
• Have it default to localhost for now? (maybe we can default to the user's public ip once we got that figured out)
• Add an endpoint for getting and setting this value

Why is it necessary:

Example of issue:
A user setup a new Lodestone Core and connects to it through localhost:16662, then creates a Minecraft server.
When they try to copy the server's IP to share with their friend, they get localhost:25565.

Example of issue:
A user sets up a custom domain myserver.com pointing to their server at 123.123.123.123 running Lodestone Core and Minecraft. But the dashboard keeps displaying 123.123.123.123

Description

store/users.json is sometimes randomly corrupted

Steps to reproduce (optional)

Investigating

Intention:

Implements all methods in the TMacro interface for a Minecraft server instance

Why is it necessary:

Trivial.

Intention:

Why is it necessary:

Intention:

Need a standardizde way to download files, even non UTF-8 ones.

Why is it necessary:

Intention:

Add cross-platform unzip functionalities that handle a wide range of archive formats (.tar.gz, zip, rar),

Why is it necessary:

Loadstone will need to deal with compressed archives a lot.

Description

Currently, when a user tries to login.
If the username is incorrect, the server replies with a 404 error.
If the password is incorrect, the server replies "Unauthorized", "Credential mismatch"

The server should not use 404 for "user not found" in this case, and reply with the exact same response in both cases

Description

If Lodestone is ran through SSH on a linux machine that has a DE running, Tauri window will pop up invisible to the SSH user, and ctrl-c the CLI will only shutdown Lodestone Core and not the Tauri window, leaving it in a invalid state

Steps to reproduce (optional)

1. Launch Lodestone through SSH
2. Ctrl C the CLI
3. Lodestone does not exit, only the core is shut down but the tauri window remains op on the DE

Description

Add Minecraft Bedrock server instance support.

https://help.minecraft.net/hc/en-us/articles/4408873961869-Minecraft-Dedicated-and-Featured-Servers-FAQ-#h_01GK57JW8ACHQ0187971GFNZSK

Shouldn't be hard, the only real issue I can see is the LD_LIBRARY_PATH env var on Linux.

System is only using around half the total memory

Intention:

Implement the function get_list_of_versions under implementations/minecraft/util.rs to return a list of valid versions for a particular flavour for Minecraft.

Why is it necessary:

Frontend needs to know what versions are available for each of the flavours.

Intention:

All Axum handlers return a json value which is dynamically typed. Change all the return type to be strongly typed.

Why is it necessary:

Dynamic typing produce less readable code and is more error prone.

Intention:

More rigorous CI

Why is it necessary:

When a linter writes better code than u

Description

For ex, get_vanilla_jar_url, get_fabric_jar_url etc all return options. Result would be preferable in this case since there are multiple points of potential failure in the function

Intention:

Add a route for frontend to query preliminary info about the client

Why is it necessary:

So frontend can check hardware specs, version numbers, etc

Intention:

Implements all methods in the TConfigurable interface for a Minecraft server instance

Why is it necessary:

Trivial.

• Display the current port
• Instruct the user to open https://lodestone.cc and enter info
• Instruct the user to open port
• Display its own ip address/hostname/public ip?
• Stop displaying the user's password on setup

Description

Add file watcher to server.properties and maybe .lodestone_config file to watch changes and update core's internal state.

Relevant crate: https://github.com/notify-rs/notify

Steps to reproduce (optional)

Intention:

Refactor all old handlers in src/handlers/system.rs and src/handlers/jar.rs to axum routes

Why is it necessary:

Part of the refactor to axum process

Intention:

Switch from Rocket to Axum during the refactoring.

Why is it necessary:

Not necessary as Rocket works fine.

Axum has native WS support while Rocket doesn't
Axum is more actively developed while Rocket often stalls
Axum is faster than rocket
Axum is a more minimal framework which may work in our favor
Axum potentially provides more features that could help with permission/auth

Intention

We should support https and wss so that those who want to set it up can.

Ideally we should also have wiki pages on this topic, and guide on how to set it up with certbot or something.
This would also serve as the basis for automating this process in the future.

Edit: Also ideally, we can have both https and http at the same time, since tauri currently defaults to http

Intention:

Implements all methods in the TPlayerManagement interface for a Minecraft server instance

Why is it necessary:

Trivial.

Intention:

Fix Clippy lints

Why is it necessary:

Better code quality

Intention:

Lodestone should not seg fault under any circumstances.

Why is it necessary:

Seg fault is bad and is indicative of memory access violation/corruption.

While I can't consistently reproduce this issue, the rough steps seem to be:

1. spawn multiple JS runtime within one macro executor, let $n$ be the number of js runtimes
2. cancel some runtime $a$ where $a < n - 1$, then cancel runtime $n-1$ and $n$
3. Seg faults occur in debug mode (not tested in release)

Intention:

Investigate the potential of switching from Rocket to Axum during the refactoring.

Why is it necessary:

Not necessary as Rocket works fine.

Axum has native WS support while Rocket doesn't
Axum is more actively developed while Rocket often stalls
Axum is faster than rocket
Axum potentially provides more feature that could help with permission/auth

Intention:

Implements all methods in the TResourceManagement interface for a Minecraft server instance

Why is it necessary:

Trivial.

Intention:

Eventually we will need to add support for installing Lodestone on Windows, an installer tailored to the windows experience is preferred.

Why is it necessary:

While the installer can be a script (python), a Windows installer provides the installation experience expected by a Windows user.

Description

Steps to reproduce (optional)

Intention:

Why is it necessary:

Intention:

Implements all methods in the TServer interface for a Minecraft server instance

Why is it necessary:

Trivial.

Intention:

Research into Axum to see how to do auth & user permissions.

Assume the user database is a kv store with the ability to get specific permissions of the user.

A small demo of the process would be nice.

Why is it necessary:

Lodestone needs auth and permissions.

Intention:

Update to Rust version 1.62.0

Why is it necessary:

1.62.0 provides major improvements on mutexes

Since Lodestone will support multiple platforms, we need a way to compress/decompress .tar.gz file commonly used on *NIX and .zip file commonly used on Windows.

Intention:

Testing on Lodestone right consists of limited unit testing. We should test on the HTTP level with real AppState and HTTP requests

Why is it necessary:

HTTP is the layer exposed to the end user, and may contain bugs not found by unit testing the sub-systems.