Creating Your Own Player Class

Hello!
I'm trying to create my own player class, so each player can have their own attributes that I create. I can't figure out how to make each player that logins declare a new HNSPlayer class, with their name as the identifier.
I also can't figure out how to convert from bukkit's player class to my own HNSPlayer class, i.e. when I use commands like bukkit.getonlineplayers(), I'd like to have that list be of HNSPlayer, not of bukkit's player class.

Please help! Thanks.

 

Can't you just create separate object and store it in hashmap with player's name as a key ?

 

It would probably be easier to save player names in a HashMap/Map/List than to create a class that extends Player.

 

Just make a new class thats called HSNPlayer with the methods in it you like, have these variables and methods

Code:java

 
protected Player player;
protected String name;
//Any other variables
 
 
//The constructor
public HSNPlayer(Player player){
     this.player = player;
     this.name = player.getName();
}
 
public boolean isHNS(){
    //if your list contains the player or whatever return true, else false
}
 
//Other methods you want
public Player[] getHNSPlayers(){
     Player[] online;
     int i = 0;
     for(Player p: Bukkit.getOnlinePlayers()){
          HNSPlayer pl = new HNSPlayer(p);
          if(p.isHNS()){
               online[i] = p;
               i++;
          }
     }
     return online;
}
[/i]

 

Thanks! I've tried what you suggested, I just don't understand how the method isHNS() would work. Don't I need to have isHNS(Player player) and then compare it to a list of players?

How would I do that? Thanks. CubixCoders

 

You should really look into OOP (Object oriented programming)

It takes a while to learn, but it's sooo worth it

 

For one, don't store player objects that can easily cause memory leaks.

For two, for storing and retrieving the HNSPlayers I would suggest having a static HashMap of <String, HNSPlayer> then on the last line of your constructor you can store the HNSPlayer like this:

Code:

//Above constructor
private static HashMap<String, HNSPlayer> allHNSPlayers = new Hashmap<String, HNSPlayer>();
 
//Last line of constructor
allHNSPlayers.put(playerName, this);

then you can have a method like this to get the player:

Code:

public static HNSPlayer getHNSPlayer(String playerName)
{
    if(allHNSPlayers.containsKey(playerName))
    {
        return allHNSPlayers.get(playerName);
    }
    return null;
}

That way you can get the players from anywhere fairly easily. I do a similar type of thing for my TARDIS plugin and it has worked really well so far.

 

It's not a good practice to publish this reference before an object is constructed. You can use a static factory method instead, that will create an object and then will add it to a static map.

 

That's why I said to put it as the last line in the constructor so as long as he isn't using multiple threads and not using it to extend from another class he should be fine. The problem I see with the static factory method is if there are multiple arguments so each time he wants to retrieve a player he would have to send in each argument even if the HNSPlayer for that Player is already created. If you only have to send in the name then you should probably do it that way unless you don't want to create an HNSPlayer for every Player but only a few select ones.

 

https://github.com/lenis0012/Marriage/blob/master/src/main/java/me/lenis0012/mr/Marriage.java#L137