Repository navigation
Axes api rebase test - #34
Merged
Merged
Conversation
timber:api/add_axe {item, durability, label} adds an axe. The seven vanilla
axes are registered the same way, other datapacks use the function tag
timber:register_axes. Scoreboards, the settings button and the durability
are made from the registration. An unknown item (mod not installed) adds nothing.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…tched off Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
… table change) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…e Advanced Manual Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
timber:axes/init used to clear and rebuild the whole registry at every load, so an axe added by a plain chat command (not through the function tag timber:register_axes) was forgotten again on reload. Axes are now marked custom when they are registered outside of the load pass, and init keeps those instead of wiping them; only the vanilla axes and the ones of the function tag are rebuilt, since something registers them again anyway. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…est env with uninstall+init Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The old name was truncated to fit Minecraft's former 16-character objective name limit, dropping an 'e' and reading as a typo. Now that longer names are allowed, spell it correctly, and remove the old objective on the next init so upgrading worlds don't keep the stray one around. Fixes #7 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
When the settings menu was rebuilt as buttons, this option's label lost its "Destroy" verb (it used to read "Destroy Player-Placed Trees"), and the tooltip never picked up the slack: it opened with an F3-debug-screen aside instead of saying what enabling it does. Put the plain-language effect first, move the risk warning up, and keep the technical detail as a short aside at the end. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…survive it New opt-in setting, off by default like its sibling "Stop on Axe Break". Where "Stop on Axe Break" still chops whatever fits before the axe would run out, this option checks the whole tree's cost up front and, if the axe can't survive it, chops nothing at all (only the block that was already mined by vanilla is lost, no extra wear applied). It requires "Wear Out Tool More" and is mutually exclusive with "Stop on Axe Break", mirroring the existing wear_out/stop_chopping and slow_chop/drop_loot guard pattern. Fixes #9 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Documents MAJOR.MINOR.PATCH: MAJOR for breaking changes (including dropping an old MC version or breaking the datapack API), MINOR for new features and new MC version support (even a pack.mcmeta-only bump), PATCH for bug fixes. Points to the existing V0.0.1-V7.2.0 tags for pre-changelog history instead of backfilling them. Fixes #26 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Runs on every published GitHub Release, builds a zip from the tracked datapack files (data, 121, pack.mcmeta, pack.png, LICENSE, README.md) with git archive, and uploads it as a new version on the "timber-datapack" Modrinth project (id gy7p6YNM) via Kira-NT/mc-publish. pack.mcmeta only stores numeric format IDs, not Minecraft version strings, so the supported version range Modrinth needs is kept separately in .github/mc-version-range.txt (currently 26.1 to 26.3, matching the project's current listing) and must be updated in the same commit as any pack.mcmeta min_format/max_format change. Needs a MODRINTH_TOKEN repository secret (a Modrinth personal access token with "Create version" permission) before it can actually publish; PlanetMinecraft upload was dropped from scope per #20. Fixes #20 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
… help dialog Per-version change entries aren't duplicated here: GitHub's Releases page (with its "Generate release notes" button) already covers that and is what Modrinth publishing reads from. This file only holds what doesn't exist anywhere else: the version-number scheme and the release checklist tying together the pieces that now have to move together on every bump (pack.mcmeta, mc-version-range.txt, the version string in help.json, and the tag/release that triggers the Modrinth upload). Set the help dialog to v8.0.0: dropping support for versions before 26.1 (min_format raised to 101) is a breaking change under the MAJOR.MINOR.PATCH scheme, so the next release after V7.2.0 is a major bump. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.