UNET trouble, trying to synchronize client data?

Unity Engine
1

So I’ve been having an issue trying to figure this out, but I want to set variables for individual players in the game, referring to networking UNET. I’ve been trying to get familiar with it, and I get a few things but get lost on a lot more. I’m aiming to give all clients a variable, but each client has a different value based on it’s choice. Example would be, all clients have a string startingWeapon, one client could have a sword while another has a dagger. How would I go about transferring that data? Here was my attempt to sync client variables:

    [SyncVar (hook = "onLoad")]
    public int x = 0;
    void Update()
    {
       if (hasAuthority)
        { CmdChangeValue(PlayerPrefs.GetInt("customizedHead", 0)); }
    }
    void onLoad(int n)
    {
        Debug.Log("value was changed: " + n);
    }
    [Command]
    void CmdChangeValue(int value)
    {
        x = value;
    }

This code makes it to where whoever holds the server overpowers all clients with it’s variable. So if the host had a value of 3, all clients have a value of 3, which is not what I’m aiming for. I’d like each client to have it’s own value, but synchronized across the game. I’m trying to word this the best I can, lol, it’s hard for me to describe networking, but am I on the right track with what I want to do? Cause, honestly, I have no idea.

EDIT: okay now the code is half working, through the standalone it works, but through the editor, it doesn’t. Ugh I’m so lost

2

Calling a Command every frame like you’re doing doesn’t make a lot of sense. You’re going to be generating a lot of useless network traffic.

So every frame you check PlayerPrefs for customizeHead, then send it to the server, which changes a SyncVar to that value, which then sends it back to the client. There has to be a better way to accomplish what you’re trying to do than sending the same value 60 or so times a second back and forth.

Also, Unet was deprecated almost 2 years ago, was never finished, and was left in a still buggy state. Now is a terrible time to just be learning it. Learn another network API.

3

Alright, that sucks, but rather learn about it now then later, thanks. Any network api you would suggest?