DevTools turns an editable PocketMine plugin folder into a PHAR you can move to another server. Build the small ModonixWorkshop command below, package it, then check its reply inside Minecraft. Keeping that first command simple makes the path from source code to a working plugin easy to follow.
Install DevTools on a compatible PocketMine server. The commands below run in the server console, without a leading slash; use /workshop for the final in-game check.

The installed example PHAR replies “ModonixWorkshop 0.0.1 is ready.” The pier is our demonstration build, not a map supplied with DevTools.
Start with the matching server and DevTools file
For this example, start Axolotl-PM 5.49.1 in a separate development folder with PHP 8.3.29 ZTS and the server’s required extensions. Keep your regular server separate while learning the build steps. A Minecraft client is only needed when you want to try the command in game.
Stop that server, place DevTools 1.17.2 in its plugins folder as DevTools.phar, then start it again. Enter:
plugins
genplugin ModonixWorkshop Modonix
The first command lists loaded plugins. The second creates plugins/ModonixWorkshop/plugin.yml and plugins/ModonixWorkshop/src/Main.php. Use these names in the example code below: the author name also becomes part of the PHP namespace.
Creating the folder does not immediately load the new plugin. Stop the server before editing these files, then restart it after the changes.
Give the example one command you can test
Replace plugins/ModonixWorkshop/plugin.yml with:
name: ModonixWorkshop
version: 0.0.1
main: Modonix\ModonixWorkshop\Main
api: 5.44.3
src-namespace-prefix: Modonix\ModonixWorkshop
commands:
workshop:
description: Check the workshop plugin
permission: modonixworkshop.command.workshop
permissions:
modonixworkshop.command.workshop:
default: op
The sample above retains API 5.44.3 as its minimum from the original walkthrough. A freshly generated file may name the running server’s API instead; the value shown here is the sample’s declaration. DevTools itself declares minimum API 5.0.0. Changing either number does not update plugin code for an older API.
Replace plugins/ModonixWorkshop/src/Main.php with:
<?php
declare(strict_types=1);
namespace Modonix\ModonixWorkshop;
use pocketmine\command\Command;
use pocketmine\command\CommandSender;
use pocketmine\plugin\PluginBase;
class Main extends PluginBase{
public function onCommand(CommandSender $sender, Command $command, string $label, array $args): bool{
if($command->getName() !== "workshop"){
return false;
}
$sender->sendMessage("ModonixWorkshop 0.0.1 is ready.");
return true;
}
}
Restart the server. DevTools enables folder-plugin loading, so plugins lists both DevTools and ModonixWorkshop. Run workshop; the command replies ModonixWorkshop 0.0.1 is ready. This provides a simple result to check before packaging.
The command permission defaults to operators. Use an operator account for the first in-game /workshop check. If ordinary players need the command later, grant its modonixworkshop.command.workshop permission deliberately instead of making everyone an operator.
Build the PHAR from the loaded folder
With ModonixWorkshop loaded, enter:
makeplugin ModonixWorkshop
DevTools writes the archive under plugin_data/DevTools/ModonixWorkshop_v0.0.1.phar. Keep the ModonixWorkshop source folder as your editable project. The PHAR is the copy to install on the other server.
If makeplugin reports an invalid plugin name, run plugins and check that ModonixWorkshop loaded after restart. For a load error, fix the first relevant console error before packaging. If PHP reports that PHAR creation is disabled, set phar.readonly=0 in the development server’s PHP configuration and restart it.
Install the package on a separate server
To move the plugin to another installation, prepare a separate server with the same server and PHP setup. While it is stopped, copy the archive into its plugins directory; ModonixWorkshop.phar is a convenient filename. The plugin name still comes from plugin.yml inside the archive.
Keep DevTools and the editable source folder in the first server. Start the second server and run:
plugins
workshop
The second server should load ModonixWorkshop and the command should return ModonixWorkshop 0.0.1 is ready. Keep the folder and PHAR on separate servers so the same plugin is not loaded twice. You can also check the packaged version on your development server: stop it, move the source folder out of its active plugins directory, install the PHAR and restart. That is the packaged version shown in the Minecraft image above.
Keep the client and server compatible
Choose the server API listed for the selected file in Files. Match a connecting Bedrock client to the server’s game protocol separately from the plugin’s minimum API.
The upstream PocketMine-MP and DevTools repositories are archived. Use the supported setup listed with the file when studying or maintaining this server; a newer client cannot connect to every older server protocol.
Comments 0
Share what worked, ask for help or reply to another player.
Use your Modonix account to join the discussion and manage your comments.
Sign in to commentNo comments yet. Share what worked for you.