Core Craft v1.2.4 Bedrock: 26.40 Setup, Progression and First-Day Guide

Evidence boundary: MineBrush statically inspected the current creator file named core-craft_v1.2.4.mcaddon (CurseForge file ID 8698525) and replayed an original two-pack manifest fixture. We did not launch Minecraft, enter a world, test a device, join a Realm, measure performance, or verify gameplay. The creator archive is All Rights Reserved and is not included or mirrored here.

Core Craft is not a small single-feature pack. The creator describes it as a Bedrock survival expansion with quests, structures, new creatures, farming, cooking, furniture, and other systems. The current catalog file is version 1.2.4 for Bedrock 26.40 and several earlier 2026 builds. That breadth is exactly why the safest first session is controlled: keep the behavior and resource packs together, use a copied or disposable world, and learn one system before adding more variables.

Core Craft 1.2.4 at a glance

The file page is the authority for the downloadable release. The official Core Craft wiki is the better place to check individual systems. On the source day, the wiki exposed sections for quests, farming, cooking, weapons, furniture, utility, biomes, and other features. Treat this article as a start route, not a substitute for that living reference.

Install without mixing releases

1. Open the creator-owned CurseForge project and confirm the project owner, filename, file ID, upload date, and supported-build labels.
2. Back up the world you care about. For the first import, prefer a new disposable world rather than the only copy of a long-running save.
3. Open the .mcaddon file through Bedrock's normal import flow. Do not rename another archive and assume it is equivalent.
4. In the disposable world's settings, inspect Behavior Packs and Resource Packs separately. The current archive contains both.
5. Activate the matching 1.2.4 pair from this one release. Do not combine a 1.2.4 behavior pack with an older resource pack that merely has a similar display name.
6. Start with no unrelated add-ons or visual packs. Save that clean baseline before experimenting with a larger stack.

Bedrock manifests identify packs by UUID and version. Microsoft's manifest reference says a declared dependency must match the other pack's header identity and version. MineBrush's private static inspection found a two-way 1.2.4 link between the behavior and resource roots in file 8698525. That is a file-structure result, not proof that the pack imports or runs on your device.

If you want a deeper explanation of the two layers, read Behavior Pack vs Resource Pack in Minecraft Bedrock. The practical rule here is simple: never “repair” a creator release by inventing UUIDs, lowering versions, or editing the manifest until you have ruled out an old, incomplete, or mismatched download.

A spoiler-light first-day route

This route is MineBrush editorial guidance, not a claimed optimal strategy and not a gameplay test. It deliberately avoids exact loot, spawn-rate, damage, or boss advice that would require a reproducible world run.

1. Prove the vanilla baseline first

Spawn, collect ordinary wood and food, place a small shelter, and sleep when you safely can. The goal is not speed. It is to confirm that movement, saving, basic crafting, and reopening the world behave normally before you chase a custom system. If the world fails before you touch Core Craft content, that distinction matters when you troubleshoot.

2. Find the guide path before spending rare materials

The creator page says Core Craft includes a built-in guidebook, and the official wiki documents a craftable Quest Book that stores quests. Use those first-party references as your glossary. If a recipe or system is not clear, check the current wiki instead of relying on an old video or an item list copied from another release.

3. Choose one early lane

The wiki says the Quest Master appears in a special Quest Tower, accepts completed quests, rewards Rubies, and connects those Rubies to Market items. It also describes the Quest Book as the place that contains your quests. Those are creator-published facts. MineBrush did not verify tower generation, reward amounts, persistence, or multiplayer synchronization.

4. Save, exit, and reopen before expanding

After a short session, record the Bedrock build, Core Craft filename, active BP/RP names, device, world name, and any other packs. Save, exit, fully close the game, reopen the same disposable world, and check the small area you changed. This is a proposed test plan. Until someone records the result with a linked Capture Lab tuple, the article must not call it tested or verified.

What the static inspection proves

The downloaded file had SHA-256 a34e3f288e63b5a08490f1e2704c4dfc9a7c286c087602784e2318cb4ef08128, measured 33,659,044 bytes, and passed ZIP integrity testing. It contained exactly two top-level roots: a behavior pack and a resource pack. Both manifests declared version 1.2.4 and pack_scope world. The behavior pack declared data and script modules; the resource pack declared a resources module. Their UUID/version dependencies matched in both directions.

The archive also contained world-generation-related directories, scripts, structures, recipes, and PNG, OGG, and TGA files. Directory presence only proves that the file contains those classes of data. It cannot prove where content generates, how often it appears, whether a script runs, how a mechanic feels, or whether a particular device stays stable.

MineBrush's original fixture models a generic behavior/resource pair with invented UUIDs and no Core Craft bytes. Its validator accepts the complete pair and rejects eight controlled faults, including a missing companion, wrong UUID, wrong version, absent script entry, incomplete script dependencies, wrong scope, missing product type, and invalid minimum-engine shape. This validates the checklist logic only.

Troubleshooting by symptom

For a broader symptom tree, use MineBrush's Bedrock add-on troubleshooting checklist. Before importing a newer release into a valuable world, use the rollback-first Bedrock add-on update workflow. Mobile players can pair this entity guide with the Android, iPhone, and iPad import guide.

Update notes for 1.2.4

The creator's current file page presents 1.2.4 as an August maintenance release for the larger 1.2 End Update. The visible notes include fixes and adjustments for the Advanced Bed, certain piston drops, multi-placement item consumption, metal-weapon smelting recipes, bonemealable foliage, ritual-zombie variants, and Forgotten Pickaxe rarity. Read the live file page before updating; release text can change, and this summary does not replace it.

Because the two manifests carry the same 1.2.4 version and depend on one another, treat them as one release unit. Keep your old download and a pre-update world copy until the new pair has passed your own save/reopen check. Catalog version labels and a clean ZIP do not guarantee compatibility with another add-on, a Realm, or every device.

Bottom line

Use the creator-owned file, keep the 1.2.4 behavior and resource packs together, start in a disposable world, and make the first session small enough to diagnose. The best first-day route is not a sprint through every feature: establish a safe vanilla base, use the current guide and quest references, choose one custom lane, then save and reopen before expanding. That gives you a useful record without pretending a static archive inspection is gameplay evidence.

Primary sources: Core Craft creator project, Core Craft 1.2.4 file page, official Core Craft wiki, Quest Master reference, Quest Book reference, and Microsoft's Bedrock manifest reference. Sources were checked on August 26, 2026.