The sword is not rendering when using SlashBlade Resharped.

[sakuraimikoto33]

When using SlashBlade Resharped, the sword is not rendering.

I'm not sure whether to report this to SlashBlade or YSM, but since there have already been similar reports regarding SlashBlade Resharped, I'll report it here.
0999312/SlashBlade_Resharped#174

[Hernes-vr]

After investigating on YSM 2.6.5-neoforge+mc1.21.1 with SlashBlade:Resharped 2.0.3-1.21.1, here's the root
cause analysis.

Two separate bugs are involved

Bug A — Blade model never renders

YSM's EntityRenderDispatcherMixin uses @WrapWithCondition on EntityRenderer.render(...) and short-circuits to
false whenever the custom YSM renderer takes over. That skips the vanilla LivingEntityRenderer.render() chain
entirely, so SlashBlade's LayerMainBlade (registered onto the vanilla PlayerRenderer via
EntityRenderersEvent.AddLayers) is never invoked — the blade item itself is never drawn.

Bug B — SlashBlade-specific animations never trigger

In the released 2.6.5 jar, the class shipping as com.elfmcys.yesstevemodel.o0000o000ooO00O00o0O0ooO (the SlashBlade
integration class) has all of its methods returning no-op values:

// (decompiled — method names obfuscated)
public static boolean   ...(ItemStack stack) { return false; }
public static String    ...(Context ctx)     { return ""; }
public static @Nullable RenderData ...(...)  { return null; }
// molang registration: ctx.setMolang("slashblade_animation", v -> "");

Because isSlashBlade() always returns false, the SlashBlade animation branch in the player animation controller is
never entered, so the slashblade.animation.json you ship (with 40+ matching keys like slashblade:idle,
slashblade:walk, slashblade:combo_a1 … slashblade:judgement_cut) never plays.

Suggested fix for Bug B

// isSlashBlade — the item tag is already present at
// data/yes_steve_model/tags/item/slashblade.json
return stack != null && stack.is(YsmItemTags.SLASHBLADE);
// (or equivalently: BladeStateAccess.of(stack).isPresent())

// getAnimationName — SlashBlade combo-state IDs map 1:1
// to your animation keys
LivingEntity entity = ctx.getModel().getEntity();
ItemStack mainHand  = entity.getItemInHand(InteractionHand.MAIN_HAND);
return BladeStateAccess.of(mainHand)
    .map(s -> s.peekCurrentComboStateTicks(entity).getValue().toString())
    .orElse("");

I verified this with a local Mixin patch — SlashBlade-specific body poses fire correctly on the default YSM model with
these two methods restored.

Bug A is harder

Any RenderLayer-based third-party integration (not just SlashBlade) is silently broken by the current
@WrapWithCondition, because layers attached to the vanilla PlayerRenderer never run.

Two reasonable fixes:

1. the YSM custom renderer invokes layers registered on the vanilla PlayerRenderer after drawing its own model, or
2. YSM exposes an explicit extension point (event / IClientItemExtensions-style hook) for "draw additional things
   bound to my bones".

Happy to share the patch source (NeoForge mixin mod, ~7 KB) if it's useful for cross-checking the official fix. Thanks
for all the work on YSM!