Skip to content

Streamline ​

StreamlineCore is a Minecraft plugin (and server-side mod) that extends server functionality through a module system. Modules are downloadable addons you place into the modules folder to add features to your server — from Discord integration to cross-network teleportation.

Server admins can mix and match modules to build the exact feature set they need, and developers can create their own modules using the Developer Framework.

Supported Server Types ​

Bukkit ​

Bukkit, Spigot, Paper, Folia, Purpur, ImmanitySpigot, and forks of the above that don't modify core code.

BungeeCord ​

BungeeCord, Waterfall, Travertine, Flamecord, XCord, and other BungeeCord/Waterfall forks that don't alter core code.

Velocity ​

Velocity and Velocity forks that don't modify core code.

Mod Loaders (Fabric, Forge, NeoForge) ​

StreamlineCore runs as a server-side mod on Fabric, Forge, and NeoForge. Each loader has its own jar per Minecraft version, named StreamlineCore-<Loader>-<version> (for example StreamlineCore-NeoForge-1211).

MinecraftFabricForgeNeoForgeJava
1.20.1✓✓✓17+
1.21.1✓✓✓21+
1.21.11✓✓✓21+
26.2✓✓✓25+
26.3✓✓✓25+

Requirements ​

PlatformRequiredOptional
Velocity—LuckPerms
BungeeCord—LuckPerms
BukkitBukkitOfUtilsLuckPerms, PlaceholderAPI
FabricFabric APILuckPerms
Forge / NeoForge—LuckPerms

Running without LuckPerms

LuckPerms is a soft dependency. Without it, Streamline has no prefixes, suffixes, groups, or meta, and cannot change permissions itself; permission checks fall back to the platform's own rules (Bukkit/proxy permissions, or operator level on mod loaders). On Bukkit and the mod loaders, nodes that modules mark as "everyone may use" are granted to all players by default; an explicit LuckPerms setting still wins.

Installation ​

  1. Download and install the required dependencies listed above for your platform.
  2. Download StreamlineCore from SpigotMC or Modrinth.
  3. Place the jar into your server's plugins folder (or mods folder on Fabric, Forge, and NeoForge).
  4. Start your server, then stop it. This generates the default configuration files.
  5. Add any Modules you want to use.
  6. Configure the plugin to your liking.
  7. Start your server again.

Configuration ​

Streamline's files live in plugins/StreamlineCore/ (or mods/StreamlineCore/ on mod loaders):

PathContents
main-config.yml, main-messages.yml, server-config.ymlCore settings and messages
commands/One file per command — label, aliases, permission, and messages are all editable
modules/Module jars
module-resources/Each module's own configuration folder

Here's how the file structure is laid out:

Main folder:Main Folder Explanation

Commands folder:Commands Folder Explanations

Core Commands ​

CommandAliasesPermissionDescription
/streamlinemodulesmodule, modules, pmodules, slmstreamline.command.streamlinemodules.defaultList, load, unload, enable, disable, reload, or download modules
/streamlinereloadslrl, slreload, slrstreamline.command.streamlinereload.defaultReload Streamline's configuration
/parsepar, rat-parsestreamline.command.parse.defaultParse placeholders
/proxyplaytimepplaytime, pplay, proxyplaystreamline.command.playtime.defaultView or edit a player's playtime
/ptagproxytagstreamline.command.tag.defaultList, add, or remove a player's tags
/setserveridentifiersetidentifier, setserverstreamline.command.setserveridentifier.defaultSet the name this server uses in cross-server messaging
/streamlinesyncslsyncstreamline.command.streamlinesync.defaultForce-save all loaded user data to the database
/streamlinedebugsldebugstreamline.command.streamlinedebug.defaultDebug tools

/modules sub-commands: list, load, unload, enable, disable, reload, reapply (each optionally followed by module names), and ecloud download <module> (version).

Namespaced commands on mod loaders

On Fabric, Forge, and NeoForge, every Streamline command (including module commands) is also registered as streamlinecore:<label> — for example /streamlinecore:modules. Use it when another mod registers the same command name.