I'll try it once I get back in a few days and post back. Thank you for taking the time.

So the update: Your code works on both client and server. The issue before was that I kept the server running, made changes in the editor and only restarted the client. Then I expected the same code to magically run on the server as well... Very dumb mistake on my part.

@Override
    public InteractionResultHolder<ItemStack> use(Level level, Player player, InteractionHand hand) {

        Double distance = 500.0D;

        if (player instanceof ServerPlayer serverPlayer) {

            HitResult viewedBlock = player.pick(distance, 0.0F, false);
            Double x = viewedBlock.getLocation().x;
            Double y = viewedBlock.getLocation().y;
            Double z = viewedBlock.getLocation().z;
            y += 1;
            
            player.teleportToWithTicket(x, y, z);
            // serverPlayer.connection.teleport(x, y, z, 0.0F, 0.0F);
        }

        return super.use(level, player, hand);
    }

So I ended up using the .teleportToWithTicket as Luis_ST initially suggested, so I don't have to adapt the head positioning.

You're right, but this Double value might be null in the future, whereas double value cannot be null. I'll change it to just double for now, since it is a fixed value for now. 

A Double value should never be null.
If you wish to disable the logic use a value which will deactivate the code (like 0).
Then execute the code only if the value not the deactivation value (in this case is larger than 0).

Edited August 2, 20223 yr by Luis_ST

4 hours ago, Luis_ST said:

A Double value should never be null.
If you wish to disable the logic use a value which will deactivate the code (like 0).
Then execute the code only if the value not the deactivation value (in this case is larger than 0).

A Double (with a capital D) absolutely can be null, because it's an Object that boxes a double (lower case d).

I understood that the Double with capital D is an object, used for complex methods, whereas double with non-capital d can be used for simple computation/methods. In general there aren't many cases where you could go wrong using Double instead of double and vice-versa. At least for simple projects as in Minecraft modding. Please do correct me, if I am in any way wrong. 

Another topic that I have: 

If I want to create skill points, example teleport. I've created a global static variable inside the ability class:

public class Ability {

    public static int teleport;

and then I increase the variable with:

Ability.teleport += 1;

On the server the teleport variable is stored as long as the server is running, once I reset the server the variable is reset and null again. Which in theory should not be an issue since the server is always running. And on the client it is the same, as long as I don't shut down the client the variable is stored and I can enter/exit as much as I like and don't lose the value of the variable. However, how would I store the value of a variable inside the world save?

Edited August 2, 20223 yr by Gepardius

3 hours ago, Draco18s said:

A Double (with a capital D) absolutely can be null, because it's an Object that boxes a double (lower case d).

Yeah it could but it should not.

1 hour ago, Gepardius said:

On the server the teleport variable is stored as long as the server is running, once I reset the server the variable is reset and null again. Which in theory should not be an issue since the server is always running. And on the client it is the same, as long as I don't shut down the client the variable is stored and I can enter/exit as much as I like and don't lose the value of the variable. However, how would I store the value of a variable inside the world save?

The best and recommended way would be a Capability.