Looping Through Lists, and cancelling?

Hey guys, I was wondering if it was possible to cancel looping through a list?

Say for example:

Code:

for(Player p : bukkit.getOnlinePlayers()){
    if(admins.contains(p)){
          //Cancel Loop here.
    }
}

So, yea, something like that. I am looking for a player who is in an arraylist or something, and if I find one, cancel. Possible?

 

break or return will stop the loop kyledag500

 

Do be careful with return though, as it will return the entire method, break only breaks loops.

 

You should just break, since you are performing operations with the player found. Also, you should not store a Player object in a list or Map. Instead, store the player's Unique Id, and check from there.

Code:java

public ArrayList<UUID> admins = new ArrayList<UUID>();
Player admin;
for(Player p : bukkit.getOnlinePlayers()){
    if(admins.contains(p.getUniqueId())){
        admin = p;
        break;
    }
}

 

Not really sure what you're asking. If you want to find out if x player is in the a list of y people, then you'd use this

Code:java

Boolean isAdmin = listOfAdmins.contains(player);

If you want to make an array of all online players who are an admin, then you'd use this

Code:java

ArrayList<String> listOfPlayersThatAreAdmins = new List<String>();
for(Player p : bukkit.getOnlinePlayers()){
    if(admins.contains(p.getName())){
        listOfPlayersThatAreAdmins.add(p.getName());
    }
}

Not really sure what you're asking :/

 

You shouldn't use the player's name, it will cause conflicts when Minecraft 1.8 gets released, and players will be able to change their names. Use the UUID, like I already posted.

 

This depends. If you want to use it to send the player a message, and only for a short time, e.g. fixing a snowball metadata to have their name if they throw it, then the username is fine.
If you are doing something like a kit which has a cooldown, even if its not between restarts, or you are logging data, it is highly recommended to log their uuid.

 

totally invalid.

names cannot be changed at runtime, only persistent data like bans is affected.

 

Correct, but if the names are stored in a config file, then the player changes his/her name, and joins back, they will no longer be matched with the method, UNLESS their UniqueId is stored in the list/config file.

Overall, it's better to use the player's UUID, to get into the good habit.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

i see hashmap.

hashmap stored in memory, not config or hdd or mysql.

UUID have nothing with good habit, it's hysteria caused by stupid youtubers who claim any method marked deprecated "to be removed next week"

 

Because he just typed a quick example.. How would you expect a list of admins to persist a reload/restart? Config file.

 

List of admins is handmade... renaud444

Do you know your own UUID?

 

RawCode
Names CAN be changed in runtime. A player simply logs off, changes his name and logs back in.
The server still has the old name in it's HashMap and can't link it to the same player anymore.

Using UUID for storage IS the way to go nowadays. Names are only player session persistent.

 

List of admins is handmade... Syd

 

RawCode
How do you know?
All I see is, that the OP tries to check if a player is stored in a List - how this List has been filled is unknown.

Also, even if it's hand made (I guess you mean "hard coded" with it), it is STILL better to use UUID, than player names, as names still can change. If the data is longer valid than the session, it should be stored in UUID.

 

Yes, I do know my own UUID, and the list is only handmade in this example. COMMON SENSE would say to store the list in a YML file.