How to store that player data?

What is the best way to store player data like isPlayerPoisoned, isPlayerBleeding, lastDeathTime? This values plugin will get very often.

 

public Map<String, Boolean> posisonedplayers = new HashMap<String, Boolean>();

posisonedplayers.put(player.getName(), true);

After that you can save it to the disk.

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

 

Yes, to the saving/loading stuff use this class:

Code:java

package io.github.samosaara;
 
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.ObjectInputStream;
import java.io.ObjectOutputStream;
 
/** SLAPI = Saving/Loading API
* API for Saving and Loading Objects.
* You can use this API in your projects, but please credit the original author of it.
* @author Tomsik68<[email][email protected][/email]>
*/
public class SLAPI
{
    public static <T extends Object> void save(T obj,String path) throws Exception
    {
        ObjectOutputStream oos = new ObjectOutputStream(new FileOutputStream(path));
        oos.writeObject(obj);
        oos.flush();
        oos.close();
    }
    @SuppressWarnings("unchecked")
    public static <T extends Object> T load(String path) throws Exception
    {
        ObjectInputStream ois = new ObjectInputStream(new FileInputStream(path));
        T result = (T)ois.readObject();
        ois.close();
        return result;
    }
}

Credits to the author.

 

bars96 depends on your code. If you intend to store more player flags like you listed then i recommend using Player Metadata.

This data is per plugin instance and already has included such logic like "how to store/get/remove the data" you only need to use those methods provided by bukkit API.

See http://jd.bukkit.org/rb/doxygen/d5/d74/interfaceorg_1_1bukkit_1_1entity_1_1Player.html and take a look at inherited methods from Metadatable - http://jd.bukkit.org/rb/doxygen/d5/d6f/interfaceorg_1_1bukkit_1_1metadata_1_1Metadatable.html

Since the Metadatable class is kinda hard to use as and is glued to the player object i would write my own class to reflect such data for easy access and storage.

(written from mind, might not work)

Code:java

 
public class PlayerData {
    private String pluginName = "my_plugin_name";
    private String playerName;
 
    public PlayerData(String playerName) {
        this.playerName = playerName;
    }
 
    public void setIsNotBleeding() {
        this.setIsBleeding(false);
    }
 
    public void setIsBleeding() {
        this.setIsBleeding(true);
    }
 
    private void setIsBleeding(Boolean flag){
        this.setMetadataValue("isBleeding", flag);
    }
 
    private MetadataValue getMetadataValue(String metadataKey)
        List<MetadataValue> metaData = this.getPlayer().getMetadata(metadataKey)
        if (!metaData.size() > 0) // not set
            return null;
 
        // only use our own metdata, since other plugins could use the same name
        // since there is no getMetaDataByPlugin we need to filter it on our own
        // I don't like to hardcode the plugin name here but its still better as passing or storing the whole plugin instance in my opinion
        for (MetadataValue metaValue : metaData) {
        if (metaValue.getOwningPlugin().getName().equals(this.pluginName))
            return metaValue;
        }
 
        // key was set by a foreign plugin (we don't want to use those values)
        return null;
    }
 
    private void setMetadataValue(String metadataKey, Object value) {
        this.getPlayer().setMetaData(metadataKey, new FixedMetadataValue Bukkit.getPluginManager().getPlugin(this.pluginName()), value);
    }
 
    private boolean hasMetaData(String metadataKey) {
        return (this.getMetadataValue(metadataKey) != null);
    }
 
    private Player getPlayer() {
        return Bukkit.getPlayerExact(this.playerName);
    }
}
 

I might hear you think "wow, this is a lot of work, why should i use this instead?" well its only hard work because there is no real API implemented yet as its not much used by plugin devs.

You might also read https://docs.google.com/document/d/1OPU1ITKY1qO6PyEDvx6NpLTfNIAHQLaXdIqIT0dZqGw/

Source: https://forums.bukkit.org/threads/metadata-q-a-i-wrote-the-metadata-api-ama.68447/

Take a look at that google doc. Should help explain how the system works. Checkout the github example. It shows another way of using metadata in your plugin.

Also note: Metadata is not persistent! You have to save them by yourself and load it on plugin enable and after a server reload.