Shared Jumping Mode

​

Overview

• If any player jumps, all Soul Link players jump simultaneously
• Forced jumps only apply to players on the ground (prevents air-stacking)
• Jump velocity is synchronized across all players
• The system uses tick-end processing to prevent race conditions

​

How to Enable

1. Run /chaos to open the Chaos Modes GUI
2. Click on the Feather/Rabbit Foot icon (“Shared Jumping Mode”)
   • Feather = Disabled
   • Rabbit Foot = Enabled (yellow color)
3. Click the emerald “Confirm” button
4. Start a new run with /start

​

Gameplay Impact

​

Movement Challenges

​

Dangerous Scenarios

• Cliff edges: One player jumps, others fall off
• Lava lakes: Forced jump while crossing narrow paths
• The Nether: Jumping near ledges can be fatal
• Combat: Unexpected jumps ruin dodging attempts
• Elytra flying: Firework jumping affects all players

​

Strategic Opportunities

​

Advanced Mechanics

​

Tick-End Processing

1. Jump Detection: When a player jumps naturally, they’re added to jumpersThisTick set
2. Collection Phase: All jumps during the tick are collected
3. Processing Phase: At tick end, forced jumps are applied to non-jumping players
4. Cleanup: Tracking sets are cleared for the next tick

​

Ground Detection

// Only apply if player is on the ground (prevent air stacking)
if (!player.isOnGround()) {
    return;
}

​

Velocity Synchronization

• Invokes player.jump() for vanilla jump behavior
• Triggers exhaustion, statistics, and jump sounds
• Sends velocity packet to client for smooth synchronization

​

Implementation Details

​

Code Reference

// Track players who jumped naturally in the current tick
private static final Set<UUID> jumpersThisTick = new HashSet<>();

// Track players who have been forced to jump this tick
private static final Set<UUID> forcedJumpersThisTick = new HashSet<>();

public static void onPlayerJump(ServerPlayerEntity player) {
    // Add to jumpers set and defer processing
    jumpersThisTick.add(player.getUuid());
}

public static void processJumpsAtTickEnd(MinecraftServer server) {
    // Force all non-jumping players to jump
    for (ServerPlayerEntity player : server.getPlayerManager().getPlayerList()) {
        if (jumpersThisTick.contains(player.getUuid())) continue;
        if (forcedJumpersThisTick.contains(player.getUuid())) continue;
        
        applyForceJump(player);
        forcedJumpersThisTick.add(player.getUuid());
    }
}

​

State Management

• lastCollectedTick: Last tick where jumps were collected
• lastProcessedTick: Last tick where jumps were processed
• processingJumps: Flag to prevent recursive processing

​

Strategy Guide

​

Safe Exploration

​

Building Adaptations

• Make bridges 3+ blocks wide instead of 1-2
• Build walls along the sides of bridges
• Create safety platforms below dangerous areas
• Use scaffolding for vertical movement (more forgiving)
• Avoid parkour-style gaps between platforms

​

Combat Tactics

• Use shields and blocking instead of dodging
• Fight in enclosed spaces (prevents fall damage)
• Coordinate who engages mobs
• One player kites while others shoot from safety
• Avoid cliff-edge combat entirely

​

Manhunt Mode Interaction

• Only Runners share jump mechanics
• Hunters jump independently with vanilla mechanics
• Hunters can exploit this to force Runners into dangerous situations
• Runners must coordinate even more carefully

​

Related Modes

​

Known Issues

• Clears tracking sets between ticks only after processing completes
• Prevents double-counting if called during processing
• Handles tick advancement edge cases gracefully