lihop / lihop/systemnauts

Assign player a directory

Open
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
GDScript
Stars
6
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Consider assigning a directory to the player (in addition to their shell process).

This directory would move (mv) when the player changes directory (cd). The players inventory would be stored in this directory.

Some things to consider:

  • This would allow us to set limits on the player can carry in their inventory using directory quotas. We could also have a sub-directory called buffer that the player uses to move files.
  • We would probably have to use a copy-on-write (COW) file system to avoid delays when the player moves between directories.
  • We would probably have to use a UUID for the directory name so they player can freely move about without causing a file name conflict.
  • When the player dies (i.e. their shell process is killed) we could leave their directory in place and create a new directory for them before they re-spawn in their home directory. This would work kind of like Minecraft where players can return to the place where they died to get their items back.
  • BTRFS appears to support COW and quotas, so it could be a good candidate for this. It also supports snapshots which could be a useful way of implementing game saves. However, I have had issues with btrfs corruption in the past, especially after power loss events, so be cautious!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified. Start by mapping how the Godot project represents players, shell processes, directory changes, inventory, and respawning; then evaluate whether filesystem moves, quotas, copy-on-write, UUIDs, and BTRFS snapshots can support the proposed behavior. Done would require an agreed design and implementation plan before coding.

Written by the indexing model from the issue text.

Assessment

Tech stack
godot, linux
Domain
game-dev, operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.