I an noticing that I get a different randomized name and a different UUID every time my mod runs.  Even if the same world is loaded.  Why is that?  Can that be changed?  I can't seem to find how.

Edited October 22, 20186 yr by MrChoke

Just now, MrChoke said:

I an notcing I get a different randomized name and a different UUID e

Because you are not specifying your account that you want to play as in the program arguments. There is a post on here about that and it was posted in just recently.

You mean when you run it from Eclipse, right? All you need to do is make sure your Run Configuration includes the program arguments for your username and password.

 

It is a good tip to specify this because many times when modding you want continuity between test runs (like having same things in inventory, or having certain Capability values retained.)

56 minutes ago, jabelar said:

having same things in inventory, or having certain Capability values retained.

These are in no way related to UUIDs in single player which is where you will spend most of your time modding. Player data is stored within the level.dat file and that includes the capabilities.

 

However when you are modding for multiplayer you also might want the UUID to be random to generate random players to join them all to a server.

 

In general I see little point in keeping the player login data consistent. It doesn't matter in single player and you want different players for multiplayer. There are however cases when you need to store something about the player by the UUID - say their relationship points with villagers - those would be stored in a map<UUID, Integer> in the entity. But these edge cases are far and between.

8 minutes ago, V0idWa1k3r said:

These are in no way related to UUIDs in single player which is where you will spend most of your time modding. Player data is stored within the level.dat file and that includes the capabilities.

 

I don't think you understand the problem. If you don't set the run configuration, every time you run in single player you will be a new player (Player123, etc.). If you have anything in your mod that depends on this, (usually things that "remember the player" like tamed animals and such) -- for example I have tile entities which keep track of which player placed them, then anything you do in one game session will not persist in the next.

 

Technically, the game DOES save in the dat for the previous player, but you can't really access that because you can't log in as that player again.

 

You're not the same player each time you run from Eclipse unless you force it with the Run Configuration.

24 minutes ago, jabelar said:

If you have anything in your mod that depends on this, (usually things that "remember the player" like tamed animals and such) -- for example I have tile entities which keep track of which player placed them, then anything you do in one game session will not persist in the next.

36 minutes ago, V0idWa1k3r said:

There are however cases when you need to store something about the player by the UUID - say their relationship points with villagers - those would be stored in a map<UUID, Integer> in the entity. But these edge cases are far and between.

 

24 minutes ago, jabelar said:

You're not the same player each time you run from Eclipse unless you force it with the Run Configuration.

I was just clarifying this point of yours

1 hour ago, jabelar said:

having same things in inventory, or having certain Capability values retained.

These are independent of which player you are since these are stored in the level.dat file.

Okay, I stand corrected about single player mode. There are things like inventory and capabilities that persist, but modded things like tameable entity ownership can have trouble.

 

I always test in dedicated server mode -- I highly recommend most modders should do this to avoid all those "side-only" problems people invariably run into. As you mentioned, in the dedicated server (i.e. multiplayer) mode, each new run of a client that connects will cause inventory and capabilities to disappear affecting continuity of your testing unless you force the login.

 

In both cases, it is probably "safest" to force the login if you're doing things related to specific players.

Like, how does one force logging in with the same UUID in different singleplayer sessions?
I'm having trouble in singleplayer keeping my UUID consistent. (I can't  touch my machines and drawers anymore)

On 10/22/2018 at 7:23 PM, jabelar said:

You're not the same player each time you run from Eclipse unless you force it with the Run Configuration.