Track experimental non-Java server support (Pumpkin) via loader abstraction

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, typescript
Domain
backend, devops

Research direction

Start by locating the instance templates and the code paths that hardcode itzg/minecraft-server, then map how they handle image, environment, ports, status, console, mods, RCON, and log heartbeat. First check whether Pumpkin has reached 1.0 and supports world saving; the issue makes those prerequisites for starting this work. Done means the loader abstraction supports the required runtime behaviors and an experimental Pumpkin option works with the mod UI disabled, with console, logs, and status verified.

Written by the indexing model from the issue text.

Description

enhancement
Summary

Pumpkin is a Rust Minecraft server with very low resource use (reportedly tens of MB RAM). It is not a jar, is not supported by the itzg image (no TYPE for it), and has no mod/plugin compatibility with Bukkit/Fabric. As of now it lacks world saving, world borders and lighting, and has no 1.0 release.

Why not now

Isopod hardcodes itzg/minecraft-server in the instance templates. Supporting Pumpkin means a separate image, start command, config path, and disabling mod/RCON/log-heartbeat assumptions.

Requirements (when Pumpkin reaches 1.0 / has world saving)
  • Introduce a loader/runtime abstraction (image, env, ports, status detection, console method) instead of itzg-only code paths.
  • Add Pumpkin (experimental) using that abstraction, with the mod UI disabled.
  • Verify console/log and status behaviour; consider Pumpkin Hub as a plugin source.
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
13h 12m
Merged PRs (30d)
57

Getting set up

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.

More from Isopod-Project/Isopod

All issues in Isopod-Project/Isopod

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.