How to access Configuration data through code about serverlistplus

[stephan-gh]

If you load after SLP (with depend or soft depend) you should be able to get the SLP instance and then access the parsed configuration classes through the configuration manager. To avoid conflicts between SLP and your plugin, you could then call the function that implements /slp disable (this will also persist across reboots).

Note however that this isn't officially part of the public API (only Replacement API and Ban API is public, see API page in SLP wiki). You would be directly accessing internal classes of SLP that may change in the future. Given the maintenance-only state of SLP I doubt that any of this will change in the future, though.

I'm also just spontaneously looking at the classes and may have typos, but I think it should roughly work like this:

ServerListPlusCore slp = ServerListPlusCore.getInstance();
ServerStatusConf conf = slp.getConf(ServerStatusConf.class);
// ... parse config ...

// run /slp disable, returns true if enable state changed, or throws an exception
slp.getProfiles().setEnabled(false);

There is also PluginConf.class and (on Bukkit) BukkitConf.class for the !Plugin and !Bukkit part of the configuration, but I guess these aren't too interesting.

SLP transforms the ServerStatusConf to a PersonalizedStatusPatch, available via slp.getStatus().getPatch() and slp.getStatus().getHosts(). There the strings are already partially pre-processed (certain static placeholders applied, possibly color codes replaced, ...). I guess this is also not helpful for you, so looking at the ServerStatusConf is probably best.

[Andre601]

Yeah, been looking at the patches one with getDefaults, getPersonalized and getBanned so far...

[Andre601]

It is done