Ultimate Elemental Swords 1.13.3: Bedrock Setup Guide

Minecraft Bedrock · Elemental weapon add-on

Ultimate Elemental Swords 1.13.3 is built around weapons that change the fight, not merely the damage number. Iced_Fox_Studios describes fire, blue-fire, water, air, earth, plant, ice, lightning, and void blades with different crowd-control or area effects. Before committing a survival world, match the resource and behavior components, confirm your Bedrock build, and prove one weapon at a time in a disposable arena.

The current release changed on August 23

Older notes that name v1.13.2 are already stale. The exact resource-pack record lists a wider set of labels from 26.30 down through several 1.21.x releases, but those labels are creator metadata rather than MineBrush test results. They do not prove that controls, scripts, particles, multiplayer, and persistence behave identically on every device.

The v1.13.3 changelog is localization-focused: it completes Russian, Korean, and Simplified Chinese text for the Metal, Poison, and Frost swords and says the fixes were applied to both behavior- and resource-pack localization files. That makes matching versions important even if you play in English.

Do not treat the main file as the whole add-on

CurseForge identifies file 8710726 as the resource pack. A resource pack can supply textures, particles, sounds, and language strings; gameplay behavior normally lives in a behavior pack or another companion component. The checked page refers to both pack types, but MineBrush did not confirm the exact current behavior-pack filename, file ID, size, or activation order.

Use the creator's current project page to identify the matching v1.13.3 pair. Do not combine a v1.13.3 resource pack with a v1.13.2 behavior pack simply because both import. A mixed pair can look correct in menus while leaving recipes, abilities, or language keys out of sync.

If Bedrock presents both packs after import, create a blank world, attach the matching components, and follow any order shown by the creator. If no order is stated, record what you selected instead of inventing a universal rule. The MineBrush guide to installing Bedrock add-ons on mobile covers the general import route, while the Bedrock file-format guide explains why an .mcpack is not automatically a complete add-on.

What the swords are meant to do

The creator groups the arsenal by battlefield role. These are source descriptions, not measured damage or cooldown results:

• Fire ignites an area, while Blue Fire is presented as a stronger blue-flame variant.
• Water applies slowing pressure and a water-themed effect.
• Air lifts or launches mobs with wind and tornado particles.
• Earth produces an earthquake-style blast that disrupts nearby enemies.
• Plant uses a poisonous cloud and vegetation-themed particles.
• Ice encloses targets in a frozen cage.
• Lightning calls bolts around the fight.
• Void creates a black-hole effect ahead of the player, pulls nearby entities, applies negative effects, and ends by throwing targets outward.

The Void description is unusually specific: the creator says the rift appears eight blocks ahead, pulls within 15 blocks, lasts 30 seconds, and finishes with an explosion-like launch. Those numbers provide a useful acceptance test. They do not tell us whether protected mobs, players, bosses, pets, dropped items, or terrain follow the same rules.

Recipes and controls need the creator's current build

The project page contains crafting images and videos, but the checked text does not expose a dependable recipe table for every v1.13.3 sword. It also does not give one complete control map for keyboard, controller, and touch. Rewriting visual recipes from memory would be more dangerous than leaving them unknown.

Open the creator's current craft reference after the matching packs are selected. Confirm the item name in your language, exact ingredients, crafting station, output count, and whether the weapon appears in Survival. For controls, test normal use, attack, sneak-use, hold-use, and any on-screen ability button without assuming that a PC instruction maps cleanly to mobile.

Keep a plain vanilla sword on the hotbar. If the custom item appears but never triggers an effect, first suspect a missing or mismatched behavior component, not a bad recipe or weak weapon.

Build a useful ability test lane

1. Create a new Creative world with no other add-ons or texture packs.
2. Mark a flat lane in one-block intervals and place targets at five, eight, 15, and 20 blocks.
3. Use one sword against one ordinary mob. Record the input, visible effect, range, delay, duration, damage, and item durability.
4. Repeat with two nearby mobs to expose area targeting, then test a wall, water, fire-sensitive blocks, and a named passive mob.
5. Save, close Minecraft completely, reopen the world, and repeat the same action.
6. Only after the solo result is stable, invite one player and repeat with friendly fire both enabled and disabled.

This lane separates three different failures: the item did not load, the input did not trigger, or the effect began but targeted the wrong thing. A short clip and a note of the selected pack versions are more useful than “the sword is broken.”

Combat cost matters more than spectacle

Particles can hide the practical tradeoffs. Measure how long an ability controls a target, whether it consumes durability, whether the user can move during activation, how quickly it can be repeated, and whether the effect damages the player or allies. For Void, also check whether the 30-second field stacks with a second cast and whether pulled entities can cross walls.

Do not publish exact damage, cooldown, or durability numbers until they are visible in current creator documentation or reproduced against the exact file pair. The project description sells the fantasy; a player guide should show how to verify the cost.

Multiplayer has an authority problem to test

Area weapons may be calculated by the host, the user, or a script that behaves differently when a joining client activates it. Run a two-player test with both people taking turns as the attacker. Compare effect origin, target selection, knockback, status duration, particles, and inventory durability.

For a Realm or server, use a copy and test only after a local host session passes. The checked sources provide no Realm, dedicated-server, console, or cross-play matrix. A correct animation on one client is not proof that damage and movement were synchronized.

Conflicts to isolate

Weapon overhauls, combat scripts, custom enchantments, animation controllers, player-action handlers, damage systems, mob AI packs, particle replacements, language packs, and other custom-item projects can touch the same layers. Restore them one at a time after the clean-world baseline.

If the effect works but the sword is invisible, inspect the resource side. If the sword looks right but behaves like a vanilla item, inspect the behavior side. If both fail only after another pack is added, record the first conflicting pair and their order rather than cycling through every add-on at once.

Updating and removing the pack

Export the world before replacing either component. Update the resource and behavior sides as a matched release, then load a copy and check old swords in inventories, containers, item frames, and equipped slots. Craft one new copy and compare it with an existing item.

For removal, clear active fields, projectiles, fires, summoned entities, and custom items in a test copy before disabling the packs. Reopen the world and visit the combat lane. Exact cleanup behavior is unknown because MineBrush did not inspect the package internals.

Fast troubleshooting

Rights and evidence boundary

CurseForge displays All Rights Reserved. MineBrush therefore points to the creator project and exact resource-file record instead of mirroring downloads or copying gallery media. The existing article cover is editorial artwork; it is not an original gameplay capture and must not be filed as one.

No package bytes, screenshots, runtime results, device tests, Realm sessions, or performance measurements were available locally. The private DLE attachment allowlist is empty.

Primary sources

• Ultimate Elemental Swords creator project
• Exact v1.13.3 resource-pack record

Source metadata was checked August 25, 2026. Recheck the project immediately before editing DLE because this project changed releases one day before the package was prepared.

Browse more weapon projects in the Minecraft Bedrock add-ons hub.