Feature Request: Machine-readable list of which WE version is meant for which other software versions (Minecraft, Fabric etc.)

Open
#2,306 2 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
Stale
Tech stack
java

Research direction

Start by reviewing the CHANGELOG and release tags, especially 7.2.14 and commit 094b734, to understand the compatibility information already recorded. Then inspect COMPILING.md. Done means an agreed machine-readable compatibility file covers the targeted software versions and COMPILING.md explains how to use it.

Written by the indexing model from the issue text.

Description

status:pending type:feature-request
The Problem

I'm trying to get machine-readable compatibility information. Most importantly, which WorldEdit version is meant for which Minecraft version, and which commit to use for building it. (I can probably use the tags for the latter part.)

I investigated tag 7.2.14 = commit 094b734 and found that the CHANGELOG gives good clues, but I'm not sure how reliable that would be, because it's meant to be read by humans, not machines. For example, while a search for "1.19.2" yields a single line and thus is at least unambiguous in that aspect, the line is prefixed with [Bukkit] so it probably means something other than the - Update to lines. However, using only - Update to lines would give no result for which WE is compatible with MC 1.19.2.

A Solution

Would you mind keeping a CSV file (or maybe JSON) with, for each WE version, the versions of all targeted software? (Minecraft, Bukkit, Fabric, not sure what else)
Once we have that, add a hint to COMPILING.md about how users can determine which version of WE they need to compile.

Alternatives
  • Circumvent CurseForge's anti bot defenses to scrape the info from there. (Nope. There needs to be a FOSS way.)
Anything Else?

No response

Dominant language
Java
Stars
3.5k
Forks
981
Avg merge
2d 15h
Merged PRs (30d)
11

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 EngineHub/WorldEdit

All issues in EngineHub/WorldEdit

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.