Getting a players UUID?

Discussion in 'Plugin Development' started by ITaco, Jul 14, 2014.

Thread Status:
Not open for further replies.
  1. Offline

    ITaco

    So I am developing a resourceful plugin that gets the players UUID and tells the sender. But how would I use the getUniqueID()? Would I make a thing like: Bukkit.getServer().getPlayer(args[0]).getUniqueID();
    Then how would I send the message to the sender? Would I make it using a string or would I use a final?
     
  2. Offline

    football70500

    Code:java
    1. sender.sendMessage(ChatColor.GREEN + Bukkit.getServer().getPlayer(args[0]).getUniqueID(););
     
  3. Offline

    Starfire1337

    I believe something like:
    Code:
    @Override
    public boolean onCommand(CommandSender sender, Command cmd, String label, String[] args) {
        if (cmd.getName().equalsIgnoreCase("uuid")) {
                    sender.sendMessage(args[0] + "'s UUID: " + Bukkit.getServer().getPlayer(args[0]).getUniqueID());
            return true;
        }
        return false;
    }
     
  4. Offline

    Necrodoom

    football70500 you have duplicate ; there, and you are trying to add ChatColor to UUID.
    Starfire1337 missing args.length check and and you are also trying to get a UUID of a string.
     
  5. Offline

    ImDeJay

    getUniqueID() only works for players that have played on your server before.

    If your wanting UUID of player that has never played on your server before, you should look into UUID Fetcher

    If the players you will be looking up have played on your server before then simply do.

    Code:java
    1. if(getServer().getPlayer(args[0]) != null){ //Make sure the player is online before creating player object.
    2.  
    3. Player thePlayer = getServer().getPlayer(args[0]); //Player object.
    4. String playerUUID = thePlayer.getUniqueId().toString(); //Convert the UUID to string so you can send it to the sender.
    5.  
    6. sender.sendMessage("Player name: " + thePlayer.getName() + "\nPlayer UUID: " + playerUUID);
    7.  
    8.  
    9. }
     
Thread Status:
Not open for further replies.

Share This Page