Why does Anim Montage section jump only run on the server?

PlayMontage replicates Play but section jumps via JumpToSection don't auto-replicate. Either call from a Multicast RPC or set bReplicateMontage in the AnimInstance for native replication.

The Play Montage Blueprint node has built-in replication via the Character. JumpToSection is a separate call; wrap it in Multicast that all clients run.

Why not always Multicast?

Bandwidth. Many montage transitions per second per character add up. Use the AnimInstance native replication for predictable cases; Multicast for one-off events.

Fix: Unreal Anim Montage Section Jump Server-Only

Quick answer: Wrap JumpToSection in a Multicast RPC. Or set bReplicateMontage = true on the AnimInstance for native replication.

Combo system jumps to the next combo section on the server. Clients see the montage stuck on section 1.

The Fix

// C++: AnimInstance opt-in
UPROPERTY(EditDefaultsOnly, Replicated)
bool bReplicateMontage = true;

// Or BP: Multicast wrap
UFUNCTION(NetMulticast, Reliable)
void Multicast_JumpComboNext();

void ACombatant::Multicast_JumpComboNext_Implementation() {
    if (auto* AI = Mesh->GetAnimInstance()) {
        FName NextSection = GetNextComboSection();
        AI->Montage_JumpToSection(NextSection, ComboMontage);
    }
}

Server calls Multicast; everyone executes JumpToSection. AnimInstance bReplicateMontage is the lighter-weight path for predictable montage flow.

Verifying

Two-client PIE. Server triggers combo. Both clients see section transitions. Without replication: only server sees correct progression.

“Replicate the section. Combo agrees on all clients.”

Related Issues

For replication scope, see replication. For Anim BP cached pose, see cached pose.

Multicast or native replication. Section lands.