The HuskClaims API provides methods for interfacing with and editing claims and users, alongside a selection of API events for listening to when players perform certain actions.

Compatibility

The HuskClaims API shares version numbering with the plugin itself for consistency and convenience. Please note minor and patch plugin releases may make API additions and deprecations, but will not introduce breaking changes without notice.

Platforms

The HuskClaims API is available for the following platforms:

• bukkit - Bukkit, Spigot, Paper, etc. Provides Bukkit API event listeners and adapters to org.bukkit objects.
• common - Common API for all platforms.

Table of contents

1. Adding the API to your project
2. Adding HuskClaims as a dependency
3. Next steps

API Introduction

1.1 Setup with Maven

<repositories>
    <repository>
        <id>william278.net</id>
        <url>https://repo.william278.net/releases</url>
    </repository>
</repositories>

<dependency>
    <groupId>net.william278.huskclaims</groupId>
    <artifactId>huskclaims-PLATFORM</artifactId>
    <version>VERSION</version>
    <scope>provided</scope>
</dependency>

1.2 Setup with Gradle

allprojects {
    repositories {
        maven { url 'https://repo.william278.net/releases' }
    }
}

dependencies {
    compileOnly 'net.william278.huskclaims:huskclaims-PLATFORM:VERSION'
}

2. Adding HuskClaims as a Bukkit plugin dependency

Add HuskClaims to your softdepend (if you want to optionally use HuskClaims) or depend (if your plugin relies on HuskClaims) section in plugin.yml of your project.

name: MyPlugin
version: 1.0
main: net.william278.myplugin.MyPlugin
author: William278
description: 'A plugin that hooks with the HuskClaims API!'
softdepend: # Or, use 'depend' here
  - HuskClaims

3. Creating a class to interface with the API

• Unless your plugin completely relies on HuskClaims, you shouldn't put HuskClaims API calls into your main class, otherwise if HuskClaims is not installed you'll encounter ClassNotFoundExceptions

public class HuskClaimsAPIHook {

    public HuskClaimsAPIHook() {
        // Ready to do stuff with the API
    }

}

4. Checking if HuskClaims is present and creating the hook

• Check to make sure the HuskClaims plugin is present before instantiating the API hook class

public class MyPlugin extends JavaPlugin {

    public HuskClaimsAPIHook huskClaimsAPIHook;

    @Override
    public void onEnable() {
        if (Bukkit.getPluginManager().getPlugin("HuskClaims") != null) {
            this.huskClaimsAPIHook = new HuskClaimsAPIHook();
        }
    }
}

5. Getting an instance of the API

• You can now get the API instance by calling HuskClaimsAPI#getInstance()

import net.william278.huskclaims.api.BukkitHuskClaimsAPI;

public class HuskClaimsAPIHook {

    private final BukkitHuskClaimsAPI huskClaimsAPI;

    public HuskClaimsAPIHook() {
        this.huskClaimsAPI = BukkitHuskClaimsAPI.getInstance(); // Or, HuskClaimsAPI.getInstance() for the common API
    }

}

6. CompletableFuture and Optional basics

• HuskClaims's API methods often deal with CompletableFutures and Optionals.
• A CompletableFuture is an asynchronous callback mechanism. The method will be processed asynchronously and the data returned when it has been retrieved. Then, use CompletableFuture#thenAccept(data -> {}) to do what you want to do with the data you requested after it has asynchronously been retrieved, to prevent lag.
• An Optional is a null-safe representation of data, or no data. You can check if the Optional is empty via Optional#isEmpty() (which will be returned by the API if no data could be found for the call you made). If the optional does contain data, you can get it via `Optional#get().

Warning:

You should never call #join() on futures returned from the HuskClaims API as futures are processed on server asynchronous tasks, which could lead to thread deadlock and crash your server if you attempt to lock the main thread to process them.

7. Next steps

Now that you've got everything ready, you can start doing stuff with the HuskClaims API!

• Claims API — Get, create, resize, & delete claims, child claims, and admin claims, and manage claim blocks
• Trust API — Trust users, groups and trust tags in claims, and provide custom trust tags
• Highlighter API — Provide a custom claim highlighter
• API Events — Listen to events when players perform certain actions