The resource-pack unifier for Minecraft: Java Edition

<h2>Commands</h2>
<code>creative-central</code> only has the necessary commands to administrate server's resource-pack
and to apply it to players. The commands are:
<h3>Command <code>/central help</code></h3>
Permission: <code>creative-central.command.help</code> (Default for everyone)
Or just <code>/central</code>, sends a list of all commands to the player. Similar
to this page.
<h3>Command <code>/central reload</code></h3>
Permission: <code>creative-central.command.reload</code> (Default for operators)
Reloads the plugin's configuration, regenerates and exports the server
resource-pack, and sends it to all players connected to the server.
<h3>Command <code>/central apply [target]</code></h3>
Permissions:
<ul>
<li><code>creative-central.command.apply</code> (Default for everyone, but won't let them apply the resource-pack for others)</li>
<li><code>creative-central.command.apply.others</code> (Default for operators)</li>
</ul>
Applies the server resource-pack to the given player (Specified in the [target]
argument) or to the player who executed the command if no target is specified.
As the <code>[target]</code> argument, you can use a player's name or <code>@a</code> to apply the resource-pack
to all players connected to the server.

Commands

<h2>Actions / Feedback</h2>
The <code>creative-central</code> also has an actions/feedback system, that is, execute
certain actions when the player accepts, successfully downloads, rejects or
fails to download the server's resource-pack.
The actions can be: send a message to the player, send a title to the player,
kick the player.
<h3>Configuring</h3>
Open <code>config.yml</code> and go to the <code>feedback</code> section, you will find something
like this:
<pre><code class="hljs language-yaml">feedback:
 accepted: ...
 success: ...
 declined: ...
 failed: ...
</code></pre>
Those subsections have a list of actions to execute when the player:
<ul>
<li><code>accepted</code>: accepted the resource-pack</li>
<li><code>success</code>: finished downloading the resource-pack</li>
<li><code>declined</code>: declined the resource-pack</li>
<li><code>failed</code>: failed to download the resource-pack</li>
</ul>
The supported actions are:
<ul>
<li><code>message</code>: Just sends a chat message to the player</li>
<li><code>title</code>: Sends a title to the player, has <code>title</code>, <code>subtitle</code>,
<code>fade-in</code>, <code>stay</code> and <code>fade-out</code> options</li>
<li><code>kick</code>: Just kicks the player with the given message, which can be multi-line</li>
</ul>
Examples:
<pre><code class="hljs language-yaml">feedback:
 accepted:
 - message: 'You just accepted the resource-pack!'
 - message: 'Yay!'
 success:
 - title:
 title: 'You just downloaded the resource-pack!'
 subtitle: 'Yay!'
 fade-in: 20
 stay: 20
 fade-out: 20
 - message: 'You are so cool!'
 - message: 'Yay!'
 declined:
 - kick: 'Please accept!'
 failed:
 - kick: 'You failed to download the resource-pack :('
</code></pre>

Actions / Feedback

<h2>Custom Resources</h2>
<code>creative-central</code> lets you add your own resources to the resource-pack, those
resources will be automatically merged with the resources that plugins add.
The resources that you add will be called the base resource-pack, since it is
loaded first, and then plugin resources are added and merged. (Note that merging
is done by the plugins, not by creative-central)
<h3>Where is the base resource-pack?</h3>
The base resource-pack "lives" in <code>/plugins/creative-central/resources/</code>. By default,
you will find two files: <code>pack.mcmeta</code> and <code>pack.png</code>
<h3>How should I modify it?</h3>
The only necessary file is <code>pack.mcmeta</code>, here are some tips:
<ul>
<li>You MUST keep the <code>pack_format</code> version in sync with your server's version, you
can find a table <a href="https://minecraft.fandom.com/wiki/Pack_format#Resource_Pack">here</a></li>
<li>You CAN update the <code>description</code> to whatever you want, it is shown in the
resource-pack selection list</li>
</ul>
<pre><code class="hljs language-json">{
 "pack": {
 "description": "&#x3C;gray>A &#x3C;light_purple>creative &#x3C;gray>description",
 "pack_format": 9
 }
}
</code></pre>
creative-central also works as a pre-processor, so you can use MiniMessage there,
soon we will support non-strict JSON syntax (supporting comments)
There is also the <code>pack.png</code> file, it is optional and you can replace it by your own
resource-pack icon, the recommended size is 64x64px.
<img src="https://github.com/unnamed/creative-central/raw/main//.github/pack-in-resource-pack-selection.png" alt="Pack in Resource Pack Selection Screen">

Custom Resources

<h2>Pack Exporting/Hosting</h2>
<code>creative-central</code> relies on collecting the required assets (textures, assets,
fonts, etc.) on the server start-up, compile the resource-pack and then export
it.
In this section we will explore the export stage, <code>creative-central</code> supports
the following methods of exporting:
<ul>
<li>MCPacks (External hosting) (Default export method)</li>
<li>Localhost (Self hosting)</li>
<li>File (Not hosted)</li>
<li>Folder (Not hosted)</li>
</ul>
<h3>MCPacks</h3>
(Default export method) <code>creative-central</code> can automatically upload the generated
resource-pack to <a href="https://mc-packs.net/">MCPacks</a>, a public &#x26; free resource-pack host.
(Please note that we are not part of MCPacks development team).
To make <code>creative-central</code> do this, open <code>config.yml</code> and set <code>export.type</code>
to <code>mcpacks</code>, like this:
<pre><code class="hljs language-yaml">export:
 type: 'mcpacks'
</code></pre>
Please consider <a href="https://mc-packs.net/">donating to MCPacks</a> if you use their
free hosting service!
<h3>Polymath</h3>
<code>creative-central</code> can automatically upload the generated resource-pack to a Polymath
server, the Oraxen's resource-pack hosting server.
To make <code>creative-central</code> do this, open <code>config.yml</code> and set <code>export.type</code> to
<code>polymath &#x3C;url> &#x3C;secret></code>, replacing &#x3C;url> by the desired Polymath server's
URL and &#x3C;secret> by the Polymath server's secret.
Example:
<pre><code class="hljs language-yaml">export:
 type: 'polymath https://mypolymathserver.com/ oraxen'
</code></pre>
<h3>Localhost (Self hosting)</h3>
We can set up a resource-pack server, on your server!
Note that this export method requires you to have access to one additional port. If
your hosting service doesn't provide you additional ports, consider using another
export method.
To start using self-hosting, open <code>config.yml</code> and set the following options:
<pre><code class="hljs language-yaml">export:
 type: 'localhost'
 localhost:
 # Enables the local resource-pack server, this is required even if you
 # have already set 'type' to 'localhost'
 enabled: true
 # Your server's address
 address: ''
 # The port to use
 port: 7270
 # The public address
 public-address: ''
</code></pre>
The settings you may want to modify now are:
<ul>
<li><code>address</code>: The address that the resource-pack server will use. If you leave it
empty, the plugin will automatically detect your server's public IP address, however,
if you want to skip the detection, you can manually set it too. Note: If you use
NAT (Network Address Translation), set this to <code>0.0.0.0</code> and pay extra attention to
the <code>public-address</code> setting explanation</li>
<li><code>port</code>: The port that the resource-pack server will use. It can't be the same as
your Minecraft server's port!</li>
<li><code>public-address</code>: The public address, sent to players to ask them to download the
server's resource pack. If you use NAT, you will have to set your public's address
or domain</li>
</ul>
<h3>File</h3>
Export the resource-pack to a ZIP file! However, this export type is not hosted,
so players will not be automatically asked to download the resource-pack.
To make <code>creative-central</code> export the resource-pack as a ZIP file, open <code>config.yml</code>
and set:
<pre><code class="hljs language-yaml">export:
 type: 'file'
</code></pre>
And that's it! The resource-pack will be created at <code>/plugins/creative-central/output.zip</code>
<h3>Folder</h3>
<code>creative-central</code> can also export the resource-pack to a folder! This is pretty
similar to the <code>file</code> export method, and is also not hosted, so players will
not be automatically asked to download the resource-pack.
To make <code>creative-central</code> export the resource-pack as a folder, open <code>config.yml</code>
and set:
<pre><code class="hljs language-yaml">export:
 type: 'folder'
</code></pre>
And that's it too! The resource-pack will be created at <code>/plugins/creative-central/output/</code>

Pack Exporting/Hosting

<h2>Resource Pack Prompt</h2>
<code>creative-central</code> lets you configure everything. In this page we are explaining
how to configure the resource-pack prompt. All the settings for the resource-pack
prompt can be found in the <code>config.yml</code> file.
This is what the configuration section for it looks like:
<pre><code class="hljs language-yaml">send:
 request:
 required: true
 prompt: '&#x3C;#ff8df8>Creative Central &#x3C;dark_gray>| &#x3C;gray>Please accept the server resource pack to enjoy the full server experience'
 delay: 0
</code></pre>
<h3><code>required</code></h3>
The <code>required</code> setting tells the Minecraft client whether it is necessary or not to
use the resource-pack to play in your server. Note that setting this to true
will not necessarily kick the player from the server if they don't download the
resource-pack, to do that, you will have to configure the actions.
<h3><code>prompt</code></h3>
The resource-pack prompt message, shown in the prompt screen. Supports MiniMessage
format and newlines with <code>\n</code>, or using YAML's <code>|-</code>
<pre><code class="hljs language-yaml">send:
 request:
 required: true
 prompt: |-
 Welcome!
 Please accept the resource-pack!
 delay: 0
</code></pre>
<h3><code>delay</code></h3>
The resource-pack prompt delay, in seconds, determines how much time to wait before
sending the resource pack to the player. Set to zero or less to send immediately.
<h3>And that's it!</h3>
Now when you join your server, you should see a screen like this:
<img src="https://github.com/unnamed/creative-central/raw/main//.github/resource-pack-prompt.png" alt="Resource Pack Prompt Screen">
And please note that, the Minecraft client will remember the player's choice, so
the screen will appear only once. If you want to be asked again, do the following:
<ul>
<li>Go back to the Server List screen</li>
<li>Select your server and click 'Edit'</li>
<li>Click the <code>Server Resource Packs</code> button until it says 'Server Resource Packs: Prompt'</li>
</ul>

Resource Pack Prompt

Configuration

<h2>Creative Central</h2>
Welcome to the <code>creative-central</code> documentation, creative-central is a plugin
that unifies the server's resource-pack, allowing other plugins to
programmatically add resources to the server's resource-pack
<code>creative-central</code> allows administrators to use multiple plugins that
use resource-packs without generating conflicts
<h3>I don't understand yet...</h3>
Do you know <a href="https://github.com/MilkBowl/Vault">Vault</a>? Vault provides an API to
unify the server's permissions, chat and economy, imagine a plugin that could do
this, but for resource-packs, that's <code>creative-central</code>!
<h3>Features</h3>
<ul>
<li>Add resources from your manually created resource-pack</li>
<li>Automatically generate the server's resource-pack</li>
<li>Automatically upload the resource-pack to a server or host it locally</li>
<li>Automatically send the resource-pack to everyone</li>
<li>Plug &#x26; play!</li>
<li>Say goodbye to bloated resource-packs! With <code>creative-central</code>, you can even have an empty resource-pack!</li>
<li>..and all the benefits from <a href="https://unnamed.team/docs/creative">creative</a></li>
<li>
<ul>
<li>Validate and compress your resource-pack</li>
</ul>
</li>
<li>
<ul>
<li><code>adventure</code> support!</li>
</ul>
</li>
</ul>

Creative Central

<h2>API Introduction</h2>
<h3>Adding central to your project</h3>
The first step to using <code>creative-central</code> is to add it to your project, you can do
this using Gradle (recommended) or Maven
<h4>Gradle</h4>
If you are using Gradle, you have to add our repository and the central dependency
to your build script (<code>build.gradle(.kts)</code>)
<h5>Kotlin DSL:</h5>
<pre><code class="hljs language-kotlin">repositories {
 maven("https://repo.unnamed.team/repository/unnamed-public/")
}

dependencies {
 compileOnly("team.unnamed:creative-central-api:1.3.0")
}
</code></pre>
<h5>Groovy DSL:</h5>
<pre><code class="hljs language-groovy">repositories {
 maven {
 url "https://repo.unnamed.team/repository/unnamed-public/"
 }
}

dependencies {
 compileOnly "team.unnamed:creative-central-api:1.3.0"
}
</code></pre>
<h4>Maven</h4>
If you are using Maven, you have to add our repository and the central dependency
to your <code>pom.xml</code>
<pre><code class="hljs language-xml">&#x3C;repositories>
 &#x3C;repository>
 &#x3C;id>unnamed-public&#x3C;/id>
 &#x3C;url>https://repo.unnamed.team/repository/unnamed-public/&#x3C;/url>
 &#x3C;/repository>
&#x3C;/repositories>

&#x3C;dependencies>
 &#x3C;dependency>
 &#x3C;groupId>team.unnamed&#x3C;/groupId>
 &#x3C;artifactId>creative-central-api&#x3C;/artifactId>
 &#x3C;version>1.3.0&#x3C;/version>
 &#x3C;scope>provided&#x3C;/scope>
 &#x3C;/dependency>
&#x3C;/dependencies>
</code></pre>
<h3>Declaring a dependency on central</h3>
If you are developing a plugin that uses <code>creative-central</code>, you should declare a dependency
on it in your plugin's <code>plugin.yml</code>, this will make sure that your plugin will not be loaded
if <code>creative-central</code> is not present
plugin.yml in Bukkit plugins
<pre><code class="hljs language-yaml">name: ...
main: ...
version: ...
...
depend: [creative-central]
</code></pre>
<h3>Getting an instance of the API</h3>
First of all, you need to obtain an instance of <code>CreativeCentral</code>, you can do this by using
your platform's service provider (preferred) or using <code>CreativeCentralProvider#get()</code>, the
static service provider
Using Bukkit's service provider
<pre><code class="hljs language-java">RegisteredServiceProvider&#x3C;CreativeCentral> provider = Bukkit.getServicesManager().getRegistration(CreativeCentral.class);
if (provider != null) {
 CreativeCentral central = provider.getProvider();
 // ...
}
</code></pre>
Using the static service provider
<pre><code class="hljs language-java">CreativeCentral central = CreativeCentralProvider.get();
</code></pre>
Now that we have a <code>CreativeCentral</code> instance, we can get to the next step

API Introduction

<h2>API Usage</h2>
Now that we have a <code>CreativeCentral</code> instance, we can use it to subscribe to
events, fire the resource-pack generate event, etc.
<h3>Adding resources to the server resource-pack</h3>
You can add your own resources to the server resource-pack by subscribing
to the <code>ResourcePackGenerateEvent</code>, which is called when the server is
loading or when the <code>/central reload</code> command is executed.
<pre><code class="hljs language-java">CreativeCentral central = ...;

central.eventBus().listen(plugin, ResourcePackGenerateEvent.class, event -> {
 ResourcePack resourcePack = event.resourcePack();
 
 // now we do the most important part, adding our own resources to
 // the resource-pack, imagine that we want to add a texture, we
 // would do the following:
 
 // here we create the texture for the minecraft note block
 Texture texture = Texture.builder()
 .key(Key.key("minecraft:block/note_block.png"))
 .data(Writable.file(new File("path/to/texture.png"))
 .build();
 
 // here we register the texture
 resourcePack.texture(texture);
});
</code></pre>
For more information, check the <a href="/docs/creative-central/developers/getting-started">creative API</a>

API Usage

Developers

<h2>ItemsAdder</h2>
<code>creative-central</code> supports ItemsAdder by default, it can take the resource-pack
that ItemsAdder generates and merge it with the resource-pack that <code>creative-central</code>
generates, this way you can use ItemsAdder and any plugin that uses <code>creative-central</code>
at the same time.
<h3>Configuration</h3>
You need to make some changes to ItemsAdder's configuration in order to make it work
with <code>creative-central</code>.
<h4>1. Disable hosting</h4>
First of all, disable ItemsAdder resource-pack hosting in <code>config.yml</code>. By default,
it shouldn't be enabled, but if you have it enabled, you need to disable it:
<pre><code class="hljs language-yaml">resource-pack:
 hosting:
 no-host:
 enabled: true # &#x3C;-- Set this to true
 self-host:
 enabled: false # &#x3C;-- Set this to false
 server-ip: ...
 pack-port: ...
 external-host:
 enabled: false # &#x3C;-- Set this to false
 url: ...
 skip-url-file-type-check___DONT_ASK_HELP_IF_SET_TRUE: false
 ...
</code></pre>
creative-central can upload/host resource-packs too, so this shouldn't be a problem.
<h4>2. Disable apply-on-join</h4>
Then, you need to set <code>resource-pack.apply-on-join</code> to <code>false</code>. <code>creative-central</code> can also
send the resource-pack to players when they join, so this shouldn't be a problem either.
<pre><code class="hljs language-yaml">resource-pack:
 ...
 apply-on-join: false
 ...
</code></pre>
<h4>3. Disable merging other resource-packs</h4>
Finally, you need to prevent ItemsAdder from merging other plugins' resource-pack
with its own resource-pack. This prevents a resource-pack from being merged twice.
<pre><code class="hljs language-yaml">resource-pack:
 ...
 zip:
 ...
 merge_other_plugins_resourcepacks_folders: [] # &#x3C;-- Set this to an empty list
 # or just remove known plugins
 # like ModelEngine from the list
</code></pre>
And that's it, you can now use ItemsAdder and creative-central at the same time!

ItemsAdder

<h2>ModelEngine 4</h2>
<code>creative-central</code> supports ModelEngine 4 by default, it can take the resource-pack
that ModelEngine generates and merge it with the resource-pack that <code>creative-central</code>
generates, this way you can use ModelEngine and any plugin that uses <code>creative-central</code>
at the same time.
<h3>No extra configuration needed!</h3>
You don't need to do anything to make <code>creative-central</code> work with ModelEngine 4,
just have both plugins installed and they will work!

ModelEngine 4

<h2>Oraxen</h2>
<code>creative-central</code> supports Oraxen by default, it can take the resource-pack
that Oraxen generates and merge it with the resource-pack that <code>creative-central</code>
generates, this way you can use Oraxen and any plugin that uses <code>creative-central</code>
at the same time.
<h3>Configuration</h3>
You need to make some changes to Oraxen's configuration in order to make it work
with <code>creative-central</code>.
<h4>1. Disable upload</h4>
First of all, disable Oraxen resource-pack upload in <code>settings.yml</code>:
<pre><code class="hljs language-yaml">Pack:
 ...
 upload:
 enabled: false # &#x3C;- Set to false here
 type: ...
 ...
</code></pre>
creative-central can upload resource-packs too, so this shouldn't be a problem.
If you are using Polymath hosting, you can also configure <code>creative-central</code> to
upload the resource-pack to that Polymath server.
<pre><code class="hljs language-yaml"># (creative-central's config.yml)
export:
 # e.g. 'polymath atlas.oraxen.com atlas'
 type: 'polymath &#x3C;server> &#x3C;secret>'
</code></pre>
<h4>2. Disable receive</h4>
Then, you need to set <code>Pack.receive.enabled</code> to <code>false</code>. <code>creative-central</code> can also
manage actions on resource-pack feedback, so this shouldn't be a problem either.
<pre><code class="hljs language-yaml">Pack:
 ...
 receive:
 enabled: false # &#x3C;- Set to false here
 ...
</code></pre>
And that's it, you can now use Oraxen and creative-central at the same time!

Oraxen

External

<h2>Reporting Pack Errors</h2>
When you join a server that needs a resource-pack, the server asks your client (your
Minecraft game) to download it. However, there might errors while downloading a
resource-pack.
In this quick troubleshooting guide, we will check what the error was, so that we can
easily report it to the server administrators (or to the plugin developers).
<h3>Step 1: Open output log</h3>
Close the game, re-open the launcher and enable the "Open output log when Minecraft:
Java Edition starts" setting. We do this to see the game logs, all the errors should
be visible there.
If you use a launcher other than vanilla launcher, you will have to find a similar setting
and enable it.
<ul>
<li>Go to the launcher Settings (Should be in the bottom-left corner)
<img src="https://github.com/unnamed/creative-central/raw/main//.github/settings-button-in-the-minecraft-launcher.png" alt="Settings"></li>
<li>Check the "Open output log when Minecraft: Java Edition starts" setting
<img src="https://github.com/unnamed/creative-central/raw/main//.github/open-output-log-when-game-starts-setting.png" alt="Open output log setting"></li>
<li>Start the game. When the game starts, there should be another window open,
and should look like this:
<img src="https://github.com/unnamed/creative-central/raw/main//.github/game-output-example.png" alt="Game Output Example"></li>
</ul>
<h3>Step 2: Join the server</h3>
Now all you have to do is to try joining the server you are having trouble with,
and check the game output window after you get kicked from the server.
There should be some error (in red text), similar to this example error:
<img src="https://github.com/unnamed/creative-central/raw/main//.github/example-error-in-game-output.png" alt="Error Example">
Don't worry if you don't understand the error, you just have to send it to the
server administrators (or to the plugin developers) and they will help you!
<h3>Why do I need to do this?</h3>
Sadly, the vanilla Minecraft client doesn't tell the server why the resource
packs fail to load, it just tells the server that it just failed.

Reporting Pack Errors

Troubleshooting

<h2>Pack Exporting/Hosting</h2>
<code>creative-central</code> relies on collecting the required assets (textures, assets,
fonts, etc.) on the server start-up, compile the resource-pack and then export
it.
In this section we will explore the export stage, <code>creative-central</code> supports
the following methods of exporting:
<ul>
<li>MCPacks (External hosting) (Default export method)</li>
<li>Localhost (Self hosting)</li>
<li>File (Not hosted)</li>
<li>Folder (Not hosted)</li>
</ul>
<h3>MCPacks</h3>
(Default export method) <code>creative-central</code> can automatically upload the generated
resource-pack to <a href="https://mc-packs.net/">MCPacks</a>, a public &#x26; free resource-pack host.
(Please note that we are not part of MCPacks development team).
To make <code>creative-central</code> do this, open <code>config.yml</code> and set <code>export.type</code>
to <code>mcpacks</code>, like this:
<pre><code class="hljs language-yaml">export:
 type: 'mcpacks'
</code></pre>
Please consider <a href="https://mc-packs.net/">donating to MCPacks</a> if you use their
free hosting service!
<h3>Localhost (Self hosting)</h3>
We can set up a resource-pack server, on your server!
Note that this export method requires you to have access to one additional port. If
your hosting service doesn't provide you additional ports, consider using another
export method.
To start using self-hosting, open <code>config.yml</code> and set the following options:
<pre><code class="hljs language-yaml">export:
 type: 'localhost'
 localhost:
 # Enables the local resource-pack server, this is required even if you
 # have already set 'type' to 'localhost'
 enabled: true
 # Your server's address
 address: ''
 # The port to use
 port: 7270
 # The public address
 public-address: ''
</code></pre>
The settings you may want to modify now are:
<ul>
<li><code>address</code>: The address that the resource-pack server will use. If you leave it
empty, the plugin will automatically detect your server's public IP address, however,
if you want to skip the detection, you can manually set it too. Note: If you use
NAT (Network Address Translation), set this to <code>0.0.0.0</code> and pay extra attention to
the <code>public-address</code> setting explanation</li>
<li><code>port</code>: The port that the resource-pack server will use. It can't be the same as
your Minecraft server's port!</li>
<li><code>public-address</code>: The public address, sent to players to ask them to download the
server's resource pack. If you use NAT, you will have to set your public's address
or domain</li>
</ul>
<h3>File</h3>
Export the resource-pack to a ZIP file! However, this export type is not hosted,
so players will not be automatically asked to download the resource-pack.
To make <code>creative-central</code> export the resource-pack as a ZIP file, open <code>config.yml</code>
and set:
<pre><code class="hljs language-yaml">export:
 type: 'file'
</code></pre>
And that's it! The resource-pack will be created at <code>/plugins/creative-central/output.zip</code>
<h3>Folder</h3>
<code>creative-central</code> can also export the resource-pack to a folder! This is pretty
similar to the <code>file</code> export method, and is also not hosted, so players will
not be automatically asked to download the resource-pack.
To make <code>creative-central</code> export the resource-pack as a folder, open <code>config.yml</code>
and set:
<pre><code class="hljs language-yaml">export:
 type: 'folder'
</code></pre>
And that's it too! The resource-pack will be created at <code>/plugins/creative-central/output/</code>

<h2>API Introduction</h2>
<h3>Adding central to your project</h3>
The first step to using <code>creative-central</code> is to add it to your project, you can do
this using Gradle (recommended) or Maven
<h4>Gradle</h4>
If you are using Gradle, you have to add our repository and the central dependency
to your build script (<code>build.gradle(.kts)</code>)
<h5>Kotlin DSL:</h5>
<pre><code class="hljs language-kotlin">repositories {
 maven("https://repo.unnamed.team/repository/unnamed-public/")
}

dependencies {
 compileOnly("team.unnamed:creative-central-api:1.0.0")
}
</code></pre>
<h5>Groovy DSL:</h5>
<pre><code class="hljs language-groovy">repositories {
 maven {
 url "https://repo.unnamed.team/repository/unnamed-public/"
 }
}

dependencies {
 compileOnly "team.unnamed:creative-central-api:1.0.0"
}
</code></pre>
<h4>Maven</h4>
If you are using Maven, you have to add our repository and the central dependency
to your <code>pom.xml</code>
<pre><code class="hljs language-xml">&#x3C;repositories>
 &#x3C;repository>
 &#x3C;id>unnamed-public&#x3C;/id>
 &#x3C;url>https://repo.unnamed.team/repository/unnamed-public/&#x3C;/url>
 &#x3C;/repository>
&#x3C;/repositories>

&#x3C;dependencies>
 &#x3C;dependency>
 &#x3C;groupId>team.unnamed&#x3C;/groupId>
 &#x3C;artifactId>creative-central-api&#x3C;/artifactId>
 &#x3C;version>1.0.0&#x3C;/version>
 &#x3C;scope>provided&#x3C;/scope>
 &#x3C;/dependency>
&#x3C;/dependencies>
</code></pre>
<h3>Declaring a dependency on central</h3>
If you are developing a plugin that uses <code>creative-central</code>, you should declare a dependency
on it in your plugin's <code>plugin.yml</code>, this will make sure that your plugin will not be loaded
if <code>creative-central</code> is not present
plugin.yml in Bukkit plugins
<pre><code class="hljs language-yaml">name: ...
main: ...
version: ...
...
depend: [creative-central]
</code></pre>
<h3>Getting an instance of the API</h3>
First of all, you need to obtain an instance of <code>CreativeCentral</code>, you can do this by using
your platform's service provider (preferred) or using <code>CreativeCentralProvider#get()</code>, the
static service provider
Using Bukkit's service provider
<pre><code class="hljs language-java">RegisteredServiceProvider&#x3C;CreativeCentral> provider = Bukkit.getServicesManager().getRegistration(CreativeCentral.class);
if (provider != null) {
 CreativeCentral central = provider.getProvider();
 // ...
}
</code></pre>
Using the static service provider
<pre><code class="hljs language-java">CreativeCentral central = CreativeCentralProvider.get();
</code></pre>
Now that we have a <code>CreativeCentral</code> instance, we can get to the next step

<h2>Oraxen</h2>
<code>creative-central</code> supports Oraxen by default, it can take the resource-pack
that Oraxen generates and merge it with the resource-pack that <code>creative-central</code>
generates, this way you can use Oraxen and any plugin that uses <code>creative-central</code>
at the same time.
<h3>Configuration</h3>
You need to make some changes to Oraxen's configuration in order to make it work
with <code>creative-central</code>.
<h4>1. Disable upload</h4>
First of all, disable Oraxen resource-pack upload in <code>settings.yml</code>:
<pre><code class="hljs language-yaml">Pack:
 ...
 upload:
 enabled: false # &#x3C;- Set to false here
 type: ...
 ...
</code></pre>
creative-central can upload resource-packs too, so this shouldn't be a problem.
<h4>2. Disable receive</h4>
Then, you need to set <code>Pack.receive.enabled</code> to <code>false</code>. <code>creative-central</code> can also
manage actions on resource-pack feedback, so this shouldn't be a problem either.
<pre><code class="hljs language-yaml">Pack:
 ...
 receive:
 enabled: false # &#x3C;- Set to false here
 ...
</code></pre>
And that's it, you can now use Oraxen and creative-central at the same time!

<h2>API Introduction</h2>
<h3>Adding central to your project</h3>
The first step to using <code>creative-central</code> is to add it to your project, you can do
this using Gradle (recommended) or Maven
<h4>Gradle</h4>
If you are using Gradle, you have to add our repository and the central dependency
to your build script (<code>build.gradle(.kts)</code>)
<h5>Kotlin DSL:</h5>
<pre><code class="hljs language-kotlin">repositories {
 maven("https://repo.unnamed.team/repository/unnamed-public/")
}

dependencies {
 compileOnly("team.unnamed:creative-central-api:1.1.0")
}
</code></pre>
<h5>Groovy DSL:</h5>
<pre><code class="hljs language-groovy">repositories {
 maven {
 url "https://repo.unnamed.team/repository/unnamed-public/"
 }
}

dependencies {
 compileOnly "team.unnamed:creative-central-api:1.1.0"
}
</code></pre>
<h4>Maven</h4>
If you are using Maven, you have to add our repository and the central dependency
to your <code>pom.xml</code>
<pre><code class="hljs language-xml">&#x3C;repositories>
 &#x3C;repository>
 &#x3C;id>unnamed-public&#x3C;/id>
 &#x3C;url>https://repo.unnamed.team/repository/unnamed-public/&#x3C;/url>
 &#x3C;/repository>
&#x3C;/repositories>

&#x3C;dependencies>
 &#x3C;dependency>
 &#x3C;groupId>team.unnamed&#x3C;/groupId>
 &#x3C;artifactId>creative-central-api&#x3C;/artifactId>
 &#x3C;version>1.1.0&#x3C;/version>
 &#x3C;scope>provided&#x3C;/scope>
 &#x3C;/dependency>
&#x3C;/dependencies>
</code></pre>
<h3>Declaring a dependency on central</h3>
If you are developing a plugin that uses <code>creative-central</code>, you should declare a dependency
on it in your plugin's <code>plugin.yml</code>, this will make sure that your plugin will not be loaded
if <code>creative-central</code> is not present
plugin.yml in Bukkit plugins
<pre><code class="hljs language-yaml">name: ...
main: ...
version: ...
...
depend: [creative-central]
</code></pre>
<h3>Getting an instance of the API</h3>
First of all, you need to obtain an instance of <code>CreativeCentral</code>, you can do this by using
your platform's service provider (preferred) or using <code>CreativeCentralProvider#get()</code>, the
static service provider
Using Bukkit's service provider
<pre><code class="hljs language-java">RegisteredServiceProvider&#x3C;CreativeCentral> provider = Bukkit.getServicesManager().getRegistration(CreativeCentral.class);
if (provider != null) {
 CreativeCentral central = provider.getProvider();
 // ...
}
</code></pre>
Using the static service provider
<pre><code class="hljs language-java">CreativeCentral central = CreativeCentralProvider.get();
</code></pre>
Now that we have a <code>CreativeCentral</code> instance, we can get to the next step

<h2>API Introduction</h2>
<h3>Adding central to your project</h3>
The first step to using <code>creative-central</code> is to add it to your project, you can do
this using Gradle (recommended) or Maven
<h4>Gradle</h4>
If you are using Gradle, you have to add our repository and the central dependency
to your build script (<code>build.gradle(.kts)</code>)
<h5>Kotlin DSL:</h5>
<pre><code class="hljs language-kotlin">repositories {
 maven("https://repo.unnamed.team/repository/unnamed-public/")
}

dependencies {
 compileOnly("team.unnamed:creative-central-api:1.2.0")
}
</code></pre>
<h5>Groovy DSL:</h5>
<pre><code class="hljs language-groovy">repositories {
 maven {
 url "https://repo.unnamed.team/repository/unnamed-public/"
 }
}

dependencies {
 compileOnly "team.unnamed:creative-central-api:1.2.0"
}
</code></pre>
<h4>Maven</h4>
If you are using Maven, you have to add our repository and the central dependency
to your <code>pom.xml</code>
<pre><code class="hljs language-xml">&#x3C;repositories>
 &#x3C;repository>
 &#x3C;id>unnamed-public&#x3C;/id>
 &#x3C;url>https://repo.unnamed.team/repository/unnamed-public/&#x3C;/url>
 &#x3C;/repository>
&#x3C;/repositories>

&#x3C;dependencies>
 &#x3C;dependency>
 &#x3C;groupId>team.unnamed&#x3C;/groupId>
 &#x3C;artifactId>creative-central-api&#x3C;/artifactId>
 &#x3C;version>1.2.0&#x3C;/version>
 &#x3C;scope>provided&#x3C;/scope>
 &#x3C;/dependency>
&#x3C;/dependencies>
</code></pre>
<h3>Declaring a dependency on central</h3>
If you are developing a plugin that uses <code>creative-central</code>, you should declare a dependency
on it in your plugin's <code>plugin.yml</code>, this will make sure that your plugin will not be loaded
if <code>creative-central</code> is not present
plugin.yml in Bukkit plugins
<pre><code class="hljs language-yaml">name: ...
main: ...
version: ...
...
depend: [creative-central]
</code></pre>
<h3>Getting an instance of the API</h3>
First of all, you need to obtain an instance of <code>CreativeCentral</code>, you can do this by using
your platform's service provider (preferred) or using <code>CreativeCentralProvider#get()</code>, the
static service provider
Using Bukkit's service provider
<pre><code class="hljs language-java">RegisteredServiceProvider&#x3C;CreativeCentral> provider = Bukkit.getServicesManager().getRegistration(CreativeCentral.class);
if (provider != null) {
 CreativeCentral central = provider.getProvider();
 // ...
}
</code></pre>
Using the static service provider
<pre><code class="hljs language-java">CreativeCentral central = CreativeCentralProvider.get();
</code></pre>
Now that we have a <code>CreativeCentral</code> instance, we can get to the next step

Commands

Command `/central help`

Command `/central reload`

Command `/central apply [target]`

Commands

Command /central help

Command /central reload

Command /central apply [target]

Command `/central help`

Command `/central reload`

Command `/central apply [target]`