PrismarineJS / PrismarineJS/minecraft-data

Fuel burn times

Open
#352 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
938
Forks
294
Avg merge
3d 5h
Merged PRs (30d)
25

Description

I am a developer on the Glowstone minecraft server, which is a clean room Java server implementing the Bukkit (as carried on by Paper / Spigot) APIs. One of the things I have been focusing on during our huge uplift from 1.12 to 1.16 is utilizing external data sources over hard coded data where possible. I have a module that generates Bukkit implementations from data packs, but one key source of data that is missing for us is fuel burn times.

Today how this is handled is that we have a manager that contains all materials or tags, mapped to their fuel burn time in seconds. Ideally, this would be stored as ticks in a series of JSON files in the data pack generated by the vanilla server, but until that happens we're hoping minecraft-data can fill that void. Currently, we don't know of any other source outside of the vanilla server itself that provides this data, so it would likely need to be maintained by hand here, but this could lead to reduced redundant maintenance for other server implementations.

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

Start by reviewing the existing material and tag data structures in minecraft-data and the manager described in the issue; no specific files or tests are named. Confirm the target Minecraft versions and representation for fuel times, then determine how fuel values should be maintained. Done means fuel burn times are available for the relevant materials or tags for server implementations.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
data, game-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.