Should sword light attacks break Unbreakable more consistently?

November 5, 2026 5 answers
Asked by lagcaper

Some players want sword light attacks to interact with Unbreakable more reliably, instead of only certain sword options feeling useful. Others also want that interaction to work while using Prismatic.

Answers

moxbyte

That ask makes sense. If a build is supposed to lean on a sword and Unbreakable together, the weapon choice should not feel picky for no clear reason. A lot of players just want the same basic cancel or interrupt behavior across sword light attacks so the build feels consistent instead of awkwardly tied to a narrow set of weapons.

The bigger win would be making the interaction predictable first, then tuning damage or energy gain after. If one sword works and another does not, that usually feels less like buildcraft and more like fighting the rules.

t1lted:

Yeah, consistency matters more than raw strength here. If it works, people can actually build around it.

Reply to this answer
RIFT_KOI

I can see both sides. Broader sword support would make the setup feel cleaner, but there is always the risk of turning a niche defensive tool into a near universal combo piece. If the goal is just to let sword light attacks cancel Unbreakable, that sounds like a reasonable quality-of-life change as long as it does not create some weird spam loop.

Prismatic compatibility seems like the part most likely to need extra balance checks. That kind of cross-setup interaction can get messy fast if it stacks too many defensive layers at once.

lagcaper:

Mostly just want it to feel less locked to specific sword picks.

Reply to this answer
coinflipz

This feels like one of those cases where the game is being overly strict about weapon states. If a sword light attack is meant to function as a quick action, then letting it cancel Unbreakable across the board would probably make the whole thing feel more natural.

I would also be fine if the fix came as a clear rule instead of a hidden exception. Players usually accept limits better when they understand them, and right now it sounds like the interaction is inconsistent enough to be frustrating.

sprocket!:

The inconsistency is the annoying part. A clean rule would be easier to work with than guessing which sword qualifies.

Reply to this answer
idlecraft

If this is about making swords feel like a real defensive tool, then yes, that support should probably be broader. A build that asks you to hold a shield posture and still use a sword should not punish you for picking the wrong blade shape or frame type.

That said, I would expect any change like this to come with a pass on animation timing and input buffering. Sometimes the issue is not the idea itself, it is that the cancel window is too tight or only lined up for a few weapon behaviors.

Reply to this answer
hexrunner

Short version, it sounds like a fair ask. Weapon identity is nice, but when one sword can work with a build and another cannot, the build stops being about player choice and starts being about hidden compatibility rules.

I would rather see the interaction standardized and then balanced around that. If it ends up too strong, adjust numbers. If it is too clunky, widen the timing. Those are easier fixes than leaving it half-supported.

pocket_lan:

Standardizing it first would already make the setup way easier to understand.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions