My Brute

Devlog: the weapon trail behind every strike

We rebuilt the weapon trail as a per-category ribbon, then removed it from the staff and the halberd. A devlog on My Brute Legacy's strike animations.

Since the devlog on the castle arena, all the work has focused on one thing: what you see when a brute strikes. Two projects, one of which ended by removing what we had just built.

The old trail couldn't be seen

A motion trail is the glowing streak left behind a blade during a strike. Ours already existed. It was bad, for three reasons we had never taken seriously:

  • It was a polyline sampled at the origin of the weapon group, that is, a point at the level of the grip. So it traced the path of the hand, not of the blade.
  • Its width was fixed, and at our camera's distance it was less than a pixel wide. Practically invisible.
  • It was identical for every weapon. A knife and a flamberge left exactly the same streak.

A real ribbon, stretched between two points of the blade

The new version no longer samples one point but two, taken in world space every frame, and stretches a ribbon between them. The result is the one we had been after from the start: the ribbon's width is the weapon. A flamberge paints a wide arc because its blade is wide. A mace paints a short, thick streak. Nobody tuned those widths by hand: they come out of the geometry.

Two drawing modes share the categories:

  • Blade mode stretches the ribbon between two points on the weapon. That is the right approach for a sweep, where the blade moves sideways and covers a real area. It covers the sword and the blunt weapon.
  • Trail mode hooks the ribbon to the tip and widens it perpendicular to the motion and the camera. Essential for a thrust: a weapon moving along its own axis sweeps no area at all, and a ribbon stretched along the blade would be completely invisible. It covers the dagger and the bare fist.

Both modes are sized from the same measurement, the blade's bounding box, taken at strike time on the weapon model alone. That "alone" cost us an evening: the forge aura projects shells well beyond the real silhouette, and the right hand, which is attached to the weapon group, has its geometry centered several meters from its pivot. Both subtrees are now named and explicitly left out of the calculation, otherwise every forge-upgraded weapon inherited a ribbon three times too wide.

The rest is carried by an additive shader: opacity fades along the tail, the hand-side edge is softened, and the leading edge burns toward a tint specific to the category. The base color stays that of the rarity, just like the forge aura. At a glance, the trail tells you both what type of weapon it is and which tier it belongs to.

Then we removed the trail from the staff

The staff had never had a trail, for lack of a motion to sample. The new system gave it one, following the casting circle and dissolving as the orb was launched. It was pretty.

We removed it two days later, and the halberd's along with it.

The reason is simple: neither one sweeps. The staff casts a spell, and the orb and its burst already tell you everything there is to understand. The halberd pushes a straight thrust along its own axis. In both cases, the ribbon added no information, it blurred something that was already clear. A trail should say "this strike swept this space"; when no space is swept, it lies.

So the profile table now holds only four entries, and the type that guards it is built by excluding those two categories. Removing an entry without touching the type, or the other way around, breaks the build. That is our way of stopping ourselves from making the same mistake in six months after forgetting why it had been fixed.

The second project: one strike per category

In parallel, each weapon family got its own strike animation, and above all its own moment of impact. That last point is what changed the readability of fights the most.

  • The dagger traces a horizontal quarter circle from the hip, slicing across. It is held in a reverse grip, so it sweeps, it doesn't stab. Impact at 0.12 seconds.
  • The sword and the blunt weapon start from a full body rotation. The blade only closes on the opponent at the end of the rotation, so the impact is set at 0.4 seconds. Setting it earlier, as was the case before, made the target react while the weapon was still behind the shoulder.
  • The staff is raised, casts, then fires. Its impact is the sum of those three durations, projectile included.
  • The halberd reaches full extension 0.1 seconds after the strike starts.

Everything syncs to that value: the target's reaction, the damage number popping up, the sound, the ribbon dissolving. A single number per category, and the whole fight falls into rhythm.

One detail we are happy with: the dagger's arc isn't hard-coded. Its radius is the distance between the hand and the body's axis, and its starting angle is that of the hand at rest, both read from the combat pose itself. Adjusting the weapon's grip in the workshop therefore moves the arc with it, instead of silently throwing it out of tune.

Idle poses

One last piece: brutes no longer hold their weapon in combat position when they aren't fighting. There are now two poses. In combat, the weapon is in hand. At rest, on your profile page and in brute selection, swords, maces and staffs are slung across the back, while short blades and the halberd stay in hand.

It isn't just a question of style. The brute model has no skeleton, and the right hand is attached to the weapon group: sending the weapon to the back takes the arm along with it. For each pose, we had to reattach the hand to its own anchor point. A hand you simply leave alone ends up inside the torso, since its geometry has no original position in the model.

What's next

The next project is the impacts themselves: for now, a brute reacts the same way to a scratch and to a hit that takes a third of its health, apart from the intensity. We would like the nature of a hit to be readable, not just its strength.

In the meantime, go watch a fight. If your brute wields a flamberge, you will see the difference right away. If it wields a staff, you won't see any trail, and that is exactly what we wanted. The demo replays a full duel, and the weapon tier list tells you what each category is worth once the animation is over.

Read next

Tourne ton telephone en portrait pour jouer