Installation

Installing StrobeLights works like most Minecraft server plugins.

1. Install the plugin

Download the StrobeLights .jar file and place it inside your server’s:

/plugins/

directory.

For example:

server/
└── plugins/
    └── StrobeLights.jar

2. Restart the server

Start or restart your Minecraft server.

StrobeLights will automatically create its required files inside:

/plugins/StrobeLights/

A normal installation currently contains:

StrobeLights/
├── lang/
├── resource-pack/
├── config.yml
└── strobes.yml

Generated files

config.yml
Contains the main StrobeLights configuration.

strobes.yml
Stores information about the strobe lights created on the server.

lang/
Contains language and localization files used by the plugin.

resource-pack/
Contains files related to the StrobeLights resource pack and its delivery system.

Do not manually modify generated data files unless the documentation specifically indicates that it is safe to do so.

3. Configure the resource pack

StrobeLights includes an automatic resource pack delivery system. By default, the following configuration is generated inside config.yml:

resource-pack:
  enabled: true
  required: true
  send-delay-ticks: 10

  public-url: http://serverip.com:8250/strobelights/{token}.zip

  embedded:
    enabled: true
    bind-address: 0.0.0.0
    port: 8250

The default public-url is only an example and must be configured before using StrobeLights.

If the default address is left unchanged, StrobeLights will display a warning in the server console:

STROBELIGHTS SETUP REQUIRED: resource-pack.public-url still uses the default address.
Configure the public server URL in config.yml.

Server operators joining the server may also receive an in-game warning indicating that StrobeLights has not yet been configured.

Setting the Public URL

In the default configuration:

public-url: http://serverip.com:8250/strobelights/{token}.zip

replace:

serverip.com

with your server’s public IP address or domain name.

For example:

public-url: http://play.example.com:8250/strobelights/{token}.zip

or:

public-url: http://123.123.123.123:8250/strobelights/{token}.zip

Do not add the Minecraft server port to the address.

The port after : is used by the StrobeLights resource pack HTTP server and must not be the same port used by Minecraft.

For example, if your Minecraft server is running on:

25565

the resource pack server can use:

8250

but it must not use 25565.

The selected HTTP port must also be accessible from outside the server and allowed by your firewall or hosting provider.

Option 1 — Unrestricted Hosting

If your hosting provider allows you to use additional ports freely, you can use StrobeLights’ built-in resource pack server.

The default port is:

port: 8250

You can keep 8250 or replace it with another available port.

Example:

resource-pack:
  enabled: true
  required: true
  send-delay-ticks: 10

  public-url: http://play.example.com:8250/strobelights/{token}.zip

  embedded:
    enabled: true
    bind-address: 0.0.0.0
    port: 8250

The port configured in public-url must match the port configured under:

embedded:
  port:

Remember that this port must be different from your Minecraft server port.

Option 2 — Hosting with an Additional Allocated Port

Some Minecraft hosting providers block arbitrary ports but allow you to request or allocate an additional port from their control panel.

In this case:

1. Request or allocate one additional port.
2. Copy the port assigned by your hosting provider.
3. Set it as the StrobeLights embedded HTTP server port.
4. Use the same port in public-url.

For example, if your provider assigns port 18432:

resource-pack:
  enabled: true
  required: true
  send-delay-ticks: 10

  public-url: http://play.example.com:18432/strobelights/{token}.zip

  embedded:
    enabled: true
    bind-address: 0.0.0.0
    port: 18432

Again, this must not be the port used by the Minecraft server.

Option 3 — Restricted Hosting

Some hosting providers do not allow additional HTTP ports at all.

In this situation, the built-in StrobeLights resource pack server cannot be reached publicly.

You will need to host the resource pack externally, for example on:

• Your own website or web server.
• A CDN.
• Another file hosting service that supports direct downloads.

Then replace the default public-url completely with the external resource pack URL.

For example:

public-url: https://example.com/downloads/strobelights.zip

The URL must point directly to the downloadable resource pack file.

A link that opens a webpage, preview page, confirmation page or any other intermediate screen will not work.

Minecraft must be able to request the URL and immediately receive the resource pack file.

If you use an external host instead of the built-in StrobeLights server, make sure the external resource pack is kept updated when required by future plugin versions.

Resource Pack Compatibility

StrobeLights uses its resource pack for part of its 3D RGB lighting system.

Players do not need to manually install any mods or additional client-side software. When the server is configured correctly, the resource pack can be automatically downloaded when they join.

OptiFine is currently compatible with StrobeLights, although compatibility with future OptiFine versions cannot be guaranteed.

Compatibility with external shader packs and additional resource packs is also not guaranteed, as they may modify or override rendering systems used by StrobeLights.

For the full RGB lighting effect, Minecraft must use:

Graphics: Fabulous!

When using external shaders, Fabulous graphics generally need to be disabled. As a result, the RGB rendering used by StrobeLights will not be available and the colored lighting effects may not be visible.

For the best experience, use:

StrobeLights Resource Pack
+
Fabulous! Graphics
+
No External Shader Pack

After Configuration

Save config.yml and perform a full server restart.

Although StrobeLights supports configuration reloads, a complete restart is strongly recommended after configuring the resource pack system.

This ensures that the embedded HTTP server, resource pack delivery system and rendering components are initialized correctly.

Verifying the Server Setup

After restarting the server, check the console.

If the resource pack system has been configured correctly, StrobeLights should display messages similar to:

[StrobeLights] Enabling StrobeLights v0.9.6
[StrobeLights] 3D RGB shader available at http://your-server:8250/strobelights/{token}.zip
[StrobeLights] StrobeLights ready: 0 strobe(s) loaded. Light Painter RGB 3D is active for Fabulous graphics.

The exact IP address, domain, port and generated token will depend on your server configuration.

The important message is:

3D RGB shader available at ...

This indicates that StrobeLights has successfully initialized the resource pack delivery system and generated the resource pack URL.

The final startup message also confirms whether the RGB 3D rendering system is active for Fabulous graphics.

Verifying the Client Setup

Join the server after restarting it.

If everything is working correctly, Minecraft should automatically download and load the StrobeLights resource pack.

Once loaded, the player should receive an in-game message similar to:

StrobeLights: pack 0.9.6 loaded. Fabulous enables RGB;
external shaderpacks may block it.

This confirms that the StrobeLights resource pack has been successfully loaded by the client.

If the resource pack loads successfully but the expected colors are not visible, check the following first:

• Make sure Fabulous! graphics are enabled.
• Disable any external shader pack.
• Make sure the StrobeLights resource pack is enabled.
• Check that another resource pack is not overriding StrobeLights assets.

If Minecraft remains stuck on Downloading Resource Pack / Making Request, or the resource pack fails to load, verify the configured public-url, port, firewall and hosting restrictions.

4. Restart after configuration

Once the initial configuration is complete, perform a full server restart.

StrobeLights supports reloading, but a complete server restart is recommended whenever possible, especially after installation or major configuration changes.

A restart ensures that all plugin systems and resource pack settings are initialized correctly.