[1.12.2] Proper way to set player speed on server? (Solved)

[ZephaniahNoah]

I'm trying to change the players speed from the server. I am sending a packet to the client that does Minecraft.getMinecraft().player.capabilities.setPlayerWalkSpeed(.15f); But it only changes the FOV and it seems inverted. I thought maybe it was a problem with the way I was sending the packet to the client but it does the same thing when I set the speed from the client. In singleplayer it works fine. Is there a better way I can set the speed from the server? I don't want to use potion effects.

Edited August 4, 2019 by ZephaniahNoah

[Animefan8888]

  On 8/3/2019 at 1:14 PM, ZephaniahNoah said:

Is there a better way I can set the speed from the server?

Expand  

Try adding a modifier to the speed attribute.

[ZephaniahNoah]

I already tried that. It gets reset when the player sprints.

EDIT: I mean, it works. But is reset when the player sprints.

Edited August 3, 2019 by ZephaniahNoah

[Animefan8888]

  On 8/3/2019 at 10:10 PM, ZephaniahNoah said:

I already tried that. It gets reset when the player sprints.

Expand  

Show what you tried.

[ZephaniahNoah]

Packet Handler:

  Reveal hidden contents

package com.zephaniahnoah.lakraces.packets;

import net.minecraft.client.Minecraft;
import net.minecraft.entity.SharedMonsterAttributes;
import net.minecraftforge.fml.common.network.simpleimpl.IMessage;
import net.minecraftforge.fml.common.network.simpleimpl.IMessageHandler;
import net.minecraftforge.fml.common.network.simpleimpl.MessageContext;

public class PlayerSpeedPacketHandler implements IMessageHandler<SendPlayerSpeed, IMessage> {
        
    @Override
    public IMessage onMessage(SendPlayerSpeed message, MessageContext ctx) {
    
    Minecraft.getMinecraft().player.getEntityAttribute(SharedMonsterAttributes.MOVEMENT_SPEED).setBaseValue(message.toSend);
    
    return null;
    }
}

 

Packet:

  Reveal hidden contents

 

package com.zephaniahnoah.lakraces.packets;

import io.netty.buffer.ByteBuf;
import net.minecraftforge.fml.common.network.simpleimpl.IMessage;

public class SendPlayerSpeed implements IMessage {

    public SendPlayerSpeed(){}

    public double toSend;

    public SendPlayerSpeed(double speed) {    
        this.toSend = speed;
    }

    @Override public void toBytes(ByteBuf buf) {
        buf.writeDouble(toSend);
    }

    @Override public void fromBytes(ByteBuf buf) {
        toSend = buf.readDouble();
    }
}

Registering It:

  Reveal hidden contents

 

...

    @EventHandler
    public void init(FMLInitializationEvent event) {
        INSTANCE.registerMessage(PlayerSpeedPacketHandler.class, SendPlayerSpeed.class, 1, Side.CLIENT);
    }

...

EDIT: I've tried setting the attribute in many places and it has the same effect. It works until I sprint. I tried saving the value from the packet to the client then setting the speed to it on KeyInputEvent but that fires before the player sprints. If there was a sprint event I could set it there.

Edited August 3, 2019 by ZephaniahNoah

[Animefan8888]

  On 8/3/2019 at 11:13 PM, ZephaniahNoah said:

.setBaseValue(message.toSend);

Expand  

I said apply a modifier to the attribute not change the base value.

Also why are you doing it on the client do it on the server.

[DavidM]

Do not do it on the client, even though the player movement is handled on the client.

The client can be a hack client that will simple ignore the packet.

Edited August 4, 2019 by DavidM

[ZephaniahNoah]

  On 8/4/2019 at 12:21 AM, Animefan8888 said:

I said apply a modifier to the attribute not change the base value.

Also why are you doing it on the client do it on the server.

Expand  

Aha! I'm sorry. I misunderstood you. This is my first time using attribute modifiers. I'll apply a modifier to the attribute.

Also, I was changing the speed on the client because I was originally using player.capabilities.setPlayerWalkSpeed(.15f); which threw no such method on the server. But I'll do it on the server now. Thank you!!

 

  On 8/4/2019 at 1:40 AM, DavidM said:

Do not do it on the client, even though the player movement is handled on the client.

The client can be a hack client that will simple ignore the packet.

Expand  

You're right. But I don't know what you mean by ignore the packet. Anyways I'm doing it on the server now.

Edited August 4, 2019 by ZephaniahNoah