Edds' VeinCapitator 3.0.0: Bedrock Setup and Test

What the add-on actually does

When the trigger and tool match, the pack searches beyond the first broken block and processes connected blocks in the same job. For mining, that means a vein-miner workflow; for trees, it means a tree-capitator workflow. The creator advertises an upper limit of 1,000 blocks. Treat that number as a cap, not as a promise that every shape, mixed cluster, custom ore, or giant tree will resolve exactly 1,000 blocks.

Version 3.0.0 changed matching toward tag and identifier checks so more custom trees and ores can be recognized. The project description also says most custom tools work based on their identifier. That is useful compatibility intent, but it is not a universal guarantee: a custom pack can use unusual tags, block states, loot logic, durability systems, or scripts. Test each third-party ore, log, and tool separately before combining packs in a real world.

Current release snapshot

• Creator: AlienEdds
• Release: VeinCapitator 3.0.0
• Exact file: VeinCapitator 3.0.0.mcaddon
• CurseForge IDs: project 1137926, file 7849194
• Current file label: Bedrock 26.10; the file page also lists earlier Bedrock versions
• Dependencies: CurseForge lists zero project dependencies
• License: All Rights Reserved

The exact delivery endpoint reported 177,923 bytes during a header-only check. MineBrush did not download or open the archive, so its internal behavior/resource components, UUIDs, manifest versions, script declarations, and activation order remain unknown.

Pack settings: pick the job you want

The creator documents pack settings that let you keep vein mining, tree capitating, or both. Use that choice to reduce surprise. If your goal is faster ore collection but you want vanilla tree chopping, disable the tree feature instead of relying on memory to avoid crouching. On a shared world, write the selected mode into the server or Realm notes so another player does not discover the rule by accidentally dropping an entire tree.

The creator also states that the pack uses no experimental options. Record that as a release-specific creator claim, not a forever-compatibility guarantee. Minecraft updates can still change tags, components, scripting behavior, or import rules even when the Experiments screen is clear.

Five-minute survival test

1. Create a new disposable world or duplicate the save you plan to use. Activate only this add-on.
2. Use an ordinary pickaxe on one small vanilla ore vein. Break one block while standing normally, then repeat on a separate vein while crouching.
3. Count blocks, drops, tool durability, and any XP. Repeat once with Fortune or Silk Touch if that enchantment matters to your world.
4. Use an ordinary axe on a small, isolated vanilla tree. Check logs, drops, tool wear, and leaf behavior after the crouch-triggered break.
5. Save, fully close Minecraft, reopen the world, and repeat one ore and one tree check.

The project says Fortune, Unbreaking, and Silk Touch are supported. Verify the result rather than assuming the enchantment name alone proves correct loot or durability behavior. One clean comparison is better than testing a huge cave cluster while several tool and loot add-ons are active.

Custom tools, ores, and trees

After the vanilla baseline passes, add one custom content pack at a time. Test the third-party tool against vanilla material first, then a vanilla tool against the third-party block, and finally the custom tool and block together. That three-part route tells you whether the failure is tied to the tool identifier, the block tag, or their interaction.

The creator explicitly mentions support for All in One Tools and Core Craft, but no exact companion version matrix is published on the checked page. Do not turn those mentions into blanket support for every current or future build. Record the exact companion release used in your own test.

Conflicts worth checking

The highest-risk overlaps are other vein miners, tree fellers, area-mining tools, custom durability systems, custom loot tables, protected-region systems, and packs that replace ore or log identifiers. If two packs respond to the same block-break event, you can get duplicate work, unexpected drops, extra tool wear, or a job that spreads farther than expected.

Start with one pack, one tool, and one small cluster. If the single-pack baseline works, add the second pack and repeat at the same location type. Do not diagnose a conflict by testing a 1,000-block job first; that makes the result harder to inspect and raises the cost of a mistake.

Multiplayer, Realms, and performance

The checked creator pages do not provide a measured Realm, dedicated-server, joining-client, permission, persistence, or device matrix for file 7849194. A local host result does not prove that a second player receives the same behavior or that protected claims are respected. Test with a second account and a deliberately small vein before a community rollout.

MineBrush has no FPS, tick-time, memory, heat, battery, or long-session benchmark for this release. The 1,000-block cap is not a performance rating. Large connected structures and heavily scripted worlds can cost more than a small vanilla vein, so increase the test size gradually while watching drops, tool state, server tick behavior, and save stability.

Update and rollback plan

Keep the original world copy and the last known-good add-on release until the replacement survives import, one ore test, one tree test, a full restart, and a second-player check if the world is shared. The checked source does not document downgrade, removal, or queued-job recovery behavior. If you need to remove the pack, do it first in a copy and inspect recently processed terrain, inventories, tools, drops, and logs after reopening.

Get the current creator release

CurseForge marks this project All Rights Reserved, so MineBrush does not mirror the creator's file. Open the exact VeinCapitator 3.0.0 file record, confirm file ID 7849194 and the Bedrock labels, then import the .mcaddon through Minecraft. For general import behavior, use Microsoft's Bedrock add-on installation guide.

What is still unknown

• The archive's hashes, internal pack count, manifests, UUIDs, scripts, and component order.
• The exact included ore/log lists and the behavior of every custom identifier.
• Realm, dedicated-server, permissions, protected-region, reconnect, and multi-player timing behavior.
• Upgrade, downgrade, removal, rollback, crash recovery, and persistence outcomes.
• Performance on any specific phone, tablet, console, PC, server, or large modded world.

Compare other utility packs in the Minecraft Bedrock add-ons hub.