Multicraft — The Minecraft Hosting Solution — How-To’s

Multicraft - The Minecraft Hosting Solution - How-To's Хостинг

15 day money back guarantee

In the unlikely event that you are not completely satisfied with our software, we are happy to provide you with a full refund for the cost of your initial Owned or Dynamic license purchase. To claim a refund under the money back guarantee you simply need to

within 15 days of the original purchase date, stating why it was not to your satisfaction and your money will be refunded in full.

The Money Back Guarantee applies to new clients and initial Owned and Dynamic license payments done through PayPal or Credit Cards only.

Accepting the minecraft eula

Minecraft versions after 1.7.9 require you create a file called eula.txt that contains the line «eula=true» in your server directory.

Adding region fixer support

Multicraft comes with a feature that allows you to run an arbitraty world repair tool, for example «Region Fixer» (


In order to configure Multicraft to use Region Fixer you can use the following instructions:

Additional information

Please evaluate the free version first. License keys cannot be combined.

Prices on this page may change at any time. Errors and omissions excepted.

The daemon will verify its license with our servers and requires a working Internet connection. None of your personal information will be transmitted in the process.

Bedrock alpha

LinuxWindows

Built-in commands

Built-in commands can be called — just like Minecraft console commands — by using them in the «Run» field.

Canarymod

You can simply download the

file and place it in the «jar» directory of your daemon to be able to use CanaryMod like Craftbukkit or vanilla Minecraft.

Alternatively you can directly add CanaryMod in your panel using the following values under Settings->Update Minecraft->Add or Remove Files:
Multicraft - The Minecraft Hosting Solution - How-To's

The «File URL» is:

Cancellations & refunds policy

Dynamic licenses may be canceled at any time. No notice period is required, and the cancellation will be effective from the date the cancellation request is made or processed. Requests for cancellation should be submitted using the link you have received with your license purchase.

Any monies paid for Dynamic license renewals prior to a cancellation request being submitted are non-refundable.

xhost.ch GmbH reserves the right to cancel payments and access to the software at any time. If a customer breaks the terms of the Multicraft EULA, a refund will not be available.

Outside the 15 Day Money Back Guarantee period, no refunds will be issued. Refunds are not issued for server failure/issues, lack of features, installation issues or if your server does not meet the Software Requirements. Installation charges are not refundable under any circumstances.

Change the listen address

Edit your «my.cnf» and change the «bind-address» setting to your internet IP. If the setting does not exist you can create it in the «[mysqld]» section of that file. Make sure to remove any line that reads «skip-networking». For example, if the internet IP of your MySQL server is 1.2.3.4:

bind-address=1.2.3.4
#skip-networking

Then restart MySQL:

service mysql restart


The service might be called differently on your system, for example «mysqld» instead of «mysql».

Cloud installation / mass deployment

With the Dynamic license one Multicraft control panel can manage multiple Minecraft instances distributed over multiple physical or virtual machines.

To use Multicraft in such a configuration:

Once this is done each server can dynamically be assigned to one of the running daemons directly in the server settings. The daemons are automatically detected as soon as they are started trough an entry they create in the shared database.

Commands


You can define new chat commands or change the role required to run built-in commands.

Configuring mysql

The above assumes that your MySQL server is already accepting remote connections. If this is not the case you have to configure MySQL to do so.

Custom jar files

We do not take any responsibility for any of the links used in this and the following sections regarding custom JARs. These links are provided by the JAR authors themselves and they are not checked by us

Daemon callbacks

The daemon allows you to hook into and influence certain events. You can configure callback scripts for these events that get passed a JSON string with the callback arguments. The return value is expected to be JSON formated as well.


These callbacks can be configured in the [advanced] section of the multicraft.conf file like this:

[advanced]
callbackServerStart = /path/to/script.py
callbackServerStop = /path/to/script.py
callbackServerLogLine = /path/to/script.py
callbackServerChatMsg = /path/to/script.py
callbackServerPlayerConnected = /path/to/script.py
callbackServerPlayerDisconnected = /path/to/script.py
callbackServerGetResourceUsage = /path/to/script.py (2.4.0 )
callbackServerCommand = /path/to/script.py (2.4.0 )

Parameters marked with a * are mutable, meaning you can return them in the JSON response with a different value to override them.

The return value of the script has to be 0 on success and any other value on failure. Cancelable events will be canceled on failure.

Example for script argument and return value:

Default settings for all jars

Starting with 2.0.0 Multicraft will read the default settings to use for all JARs from the config file «default_server.conf». You can rename the «default_server.conf.dist» that ships with Multicraft to «default_server.conf» and edit the file to your needs to override the default values. Whenever no .conf file is found or the .conf filed doesn’t explicitly set a value the values from this file will be used.

Delivery policy

Upon completion of your order we will send out an email containing your license key to the email address entered during checkout. You can use this license key to unlock the additional features of your existing installation or during a new installation.

Orders are typically completed instantly but our fraud check processes can delay this. If you have not received your product key within 24h please submit a ticket containing proof of purchase so we can look up the status of your order.

Different java versions

By default the .jar.conf files call Java through the {JAVA} variable in the «command» setting, e.g.:

[start]
command = "{JAVA}" -Xmx{MAX_MEMORY}M -Xms{START_MEMORY}M -jar "{JAR}" nogui


This variable will simply be replaced by the «java» setting in your multicraft.conf file, by default:

java = /usr/bin/java

You can change this setting to the path of the «java» binary you’d like to use.

If the different server types you offer require different Java versions it’s no longer possible to use the same {JAVA} variable in all .jar.conf files. Instead you can use the path to the correct version of Java directly in that «command» setting, e.g.:

[start]
command = /usr/bin/java -Xmx{MAX_MEMORY}M -Xms{START_MEMORY}M -jar "{JAR}" nogui


That way you can ensure each JAR uses the correct Java version and for example keep {JAVA} for the version that is supported by most JARs or that is the current LTS release.

Example 2 — add an «accept eula» button to the server settings (advanced)

On your panel, add the following code to «protected/controllers/ServerController.php» after line 172:

Examples

Simple templates for installing additional mod files

In it’s simplest form a template is just a directory that contains a «files» directory with any kind of files in it. Upon installation of the template the files in the «files» directory will be copied to the server directory. The name of the template is the name of the directory within your «templates» directory. For example, two templates named «template1» and «template2» might look like this:

Multicraft - The Minecraft Hosting Solution - How-To's


To have a JAR file install «template1» when that JAR file is selected, set the following in the .jar.conf file:

forceTemplate = template1

In this example that would cause the file «MOD FILES HERE» to be copied to the server directory the first time the server is started using this JAR.

Copy an additional test.conf file to the server directory

copyfile.zip/                           # Can either be a zip file or a plain directory
             template.conf              # The template configuration, optional
             files/                     # Everything in here will be copied to the server directory
                   test.conf

template.conf contents:

[general]
name=Copy test.conf

Configure the server with an additional config file, print a message before installing the template, do post processing using a script, enable certain server startup parameters, disallow deleting the server directory as part of the template installation

configure.zip/
              afterSetup.sh             # This script will be run after the setup has been completed
              template.conf
              files/
                    some_config.conf

template.conf contents:

Flexibility and scaling

Multicraft is most commonly used in one of the ways described below. Please contact us if you have a different kind of deployment in mind.

For individual servers

If you just want to accept the eula for your server it is sufficient to create this file or change the line to «eula=true» if it already exists. You can use your panel FTP file access to achieve this.

Free license

The free edition of this panel will allow you to run one server (for managing multiple servers, please see above). It can be used for free as long as it is not used for commercial* purposes. It will print a small text banner ingame on a regular basis.

* Commercial means that the software is used in any way intended for or directed toward commercial advantage or monetary compensation

License description


Multicraft is an application that will help you get your Minecraft server hosting going in no time. It’s extremely flexible and scalable, you can easily manage thousands of servers on a single panel installation.

Limit disk space / quota support (linux only, new in 2.0.0)

If you have already configured Quota support for your system you can enable the Multicraft quota feature by editing your multicraft.conf file and changing:

#enableQuota = false
enableQuota = true

or by adding the setting to the [system] section if it does not exist yet. The other «quota*» settings can be used to fine tune this feature.

The daemon has to be restarted for the enableQuota setting change to take effect.

Multicraft — the minecraft hosting solution — news

Multicraft version 2.4.2 is a maintenance release with several minor bugfixes over 2.4.1. Upgrading is recommended if any of the listed changes affect your installation.

For large installations we recommend testing the new version with a representative installation using the same system and data as your main installation to ensure that the upgrade on the main installation works as intended.

Please let us know if you have any feedback for this version or if you have feature suggestions for the next releases. We’re committed to continuing our time-tested approach of improving Multicraft based mainly on customer feedback.

If you find a security relevant issue with Multicraft we also offer a bug bounty with varying cash rewards depending on the severity of the issue.

Multicraft 2.4.2 ChangelogLatest build number: 913068 — Updated Oct 04.

In preparation for the 2.5.0 release we are making the latest PREVIEW build of Multicraft available for public testing. This build currently has to be considered experimental.

There have been many changes to lower level systems to improve stability and performance. Among the larger new features are:
Experimental: New web FTP client with drag and drop support (enable under Settings — Panel Configuration)
Experimental: Ability to keep servers running through daemon restarts (Docker only)
— New daemon parameter to run daemon commands through the command line
— The new Flat-Light theme is now the default

Changelog for 2.5.0-pre1:
- Added command line parameter to show current daemon version
- Added new built-in _zip_cwd command for zipping relative to a directory (used in web FTP client)
- Added new settings related to web FTP client
- Added recommended Docker parameters
- Added setting to disable binding all interfaces when using Docker
- Added warning when FTP server is run separately and uses the same log file as the daemon
- Changed default logfile for daemon in FTP separate mode
- Changed default theme to flat-light
- Don't delete full server backups when autodelete is disabled even when total count is over the maximum
- Fail config/jar updates on HTTP errors to prevent corrupting files
- Fixed MLST FTP command
- Fixed race condition that could cause the daemon to lose the database connection
- Fixed race condition when finishing multiple server moves in parallel
- Fixed rare case of the daemon losing connection to a server console
- Fixed server move information dialog interfering with server control buttons
- Fixed stacktrace in launcher
- Forward environment variables to server process when using launcher
- Implemented ability for servers using Docker to keep running when the daemon shuts down and reattach when the daemon   starts
- Implemented ability to send daemon commands through the command line
- Implemented new web FTP client with drag and drop support
- Launcher directory no longer automatically gets chmod/chowned
- Log full command line when running scripts
- Log script errors more clearly
- Log script name in errors related to a specific script
- More clearly mark some warning messages
- Moved main server config changes to after extracting template to avoid overwriting changes
- Performance optimizations
- Show FTP server exceptions as bugs

The preview release is available here:
Linux: Multicraft 2.5.0 Preview 64bit

Some Minecraft server versions require a new version of Java to work. We’ve added a new how-to entry for changing the Java version or running multiple different Java versions with Multicraft:

Different Java Versions

We’ve also updated the Windows standalone package to Java 16:

Today between around 09:00 CEST and 09:45 CEST we’ve been experiencing an incident on our infrastructure that affected user installations in unintended ways.

This was not caused by a compromise or a software bug with the Multicraft software itself but the result of human error during a system maintenance.

Our licensing mechanism is designed to allow for extended outages on our side without any effect on licensing. We’ve increased these tolerances further with version 2.4 of Multicraft to make sure such issues are never affecting user installations but any version of Multicraft can tolerate at least several hours before the first licensing warning is issued in the log. For a license to be fully affected at least 24h would have to pass. Daemons are never shut down due to automated licensing checks.
Unfortunately today there was a chain of events that negated these built-in safety precautions.

Here’s a breakdown of the events to our current knowledge:

For now we have reverted any change that had a role in this incident and the blacklist has been disabled completely.

We are extremely sorry this has happened and would like to apologize to anyone affected by this incident. We have disappointed both our users and ourselves today and we will take steps to ensure that this issue does not happen again. We see the following failures that need to be addressed:

  • Incomplete tests: While we have tested the process before deployment we have not had the most up to date data for the tests. The invalid entry should have been part of our test set before deployment.
    We intend to address this by enforcing a delay between infrastructure changes to allow for more rigorous testing.
  • Missing validity checks: There was no way for the system to create the offending entry automatically, all data is checked beforehand and inserts only happen with valid data. However, once manually introduced, the validity checks for data returned by the database were insufficient and enabled this behavior.
    We intend to address this by re-implementing the blacklist functionality entirely with today’s situation in mind and with every line of code being absolutely sure of the data it is handling.
  • Piracy handling: As we know it most famously from games, piracy is a real issue and it’s been an issue for us as well with a large number of pirated installations in the wild a while ago. We’ve taken a lot of steps to deal with this, always careful to not affect legitimate users in a negative way. Up until today this has worked very well, we’ve been able to reduce the number of pirated installations without adversely affecting other users. However, just as how anti piracy measures in games that prevent legitimate users from playing are unacceptable, it’s unacceptable for our own measures to affect our legitimate users.
    We intend to address this in two ways:
    1. Allow for more time for affected installations. While it’s usually clear what’s a pirated installation and what’s not, there’s always room for doubt so we intend to greatly increase any time delays related to licensing. For example the time delay between a piracy warning and the actual daemon shutdown will be increased.
    2. Clear communication: Right now when an installation is identified as pirated, there is not enough warning for users. Some of that is intentional as crackers will use such messages as starting point for creating patches. Nevertheless, we’re going to add clearer log messages as well as admin messages within the panel itself so users always stay informed.

Customers who have been affected by this issue can contact us at

info@multicraft.org

.

We are aware of an issue affecting several customer installations. A fix has been deployed at approximately 09:45 CEST.

Daemons will usually recover automatically within less than 60 minutes but you can speed this up by restarting affected daemons. Daemons prior to 2.4 may also have shut down so they would have to be restarted.

We will investigate the cause and post a full report here as soon as we have all the necessary information. Customers who have been affected by this issue can contact us at info@shhost.ru

Multicraft version 2.4.1 is a maintenance release with several minor bugfixes over 2.4.0. Upgrading is recommended if any of the listed changes affect your installation.

For large installations we recommend testing the new version with a representative installation using the same system and data as your main installation to ensure that the upgrade on the main installation works as intended.

Please let us know if you have any feedback for this version or if you have feature suggestions for the next releases. We’re committed to continuing our time-tested approach of improving Multicraft based mainly on customer feedback.

If you find a security relevant issue with Multicraft we also offer a bug bounty with varying cash rewards depending on the severity of the issue.

Multicraft 2.4.1 Changelog

Multicraft version 2.4.0 is now available after an extended period of testing as a preview release. A lot has changed under the hood to ensure compatibility with new systems and to futher improve performance and stability. We’ve also implemented a new modern flat theme (light and dark) as an alternative to the centered theme.

For large installations we recommend testing the new version with a representative installation using the same system and data as your main installation to ensure that the upgrade on the main installation works as intended.

Please let us know if you have any feedback for this version or if you have feature suggestions for the next releases. We’re committed to continuing our time-tested approach of improving Multicraft based mainly on customer feedback.

If you find a security relevant issue with Multicraft we also offer a bug bounty with varying cash rewards depending on the severity of the issue.

Multicraft 2.4.0 ChangelogLatest build number: 913020 — Updated Dec 11.

In preparation for the 2.4.0 release we are making the latest PREVIEW build of Multicraft available for public testing. This build currently has to be considered experimental.

After the previous round of preview releases we’ve had to react to several changes in external plugin lists and released multiple hotfixes for 2.3 to address them. We’ve used the delays this caused in the 2.4 release schedule to finalize the new theme and prepare it for inclusion with 2.4 already. We’ve also taken this additional time to update several large underlying libraries to future proof the daemon and the panel as well as to address a few compatibility issues with newer systems.

Changelog for 2.4.0-pre12:
- Added filter to only show users with roles in server user list
- Allow MySQL SSL connections without client certificate
- Compilation optimization to improve performance
- Don't scroll JAR dropdown search box
- Fixed sidebar flashing when reloading page in collapsed state
- Minor fixes for new themes
- Recursively send signals to child processes (fixes Kill button not working when using launcher)
- Updated Yii framework
Changelog for 2.4.0-pre11:
- Fixed quota update and display not always working correctly
- Fixed server command callback not overriding all variables
- Added CONF_FILE variable
- Improved backup delay display when a previous backup completed successfully
- Make sure the WORKING_DIR variable is set even before the server is started
- Several minor fixes for both centered and flat themes
- Show file size on full backup restore page
- Updated DE translation
- Flat theme: Fixed main menu display on small screens
- Flat theme: Fixed plugin page display
- Flat theme: Fixed sidebar flashing when reloading page with the sidebar collapsed
Changelog for 2.4.0-pre10:
- Added default command for full backup on server creation
- Added separate limit for number of full backups
- Added setting to disable automatic deletion of full backups after reaching the limit
Changelog for 2.4.0-pre9:
- Added additional parameters to server stop and get usage callbacks
- Added daemon_id parameter to all callbacks
- Fixed stacktrace in get usage callback
- Fixed stacktrace in command handling
Changelog for 2.4.0-pre8:
- Added TTL value when creating CloudFlare subdomain
- Added ability to run scripts as daemon
- Added callback for modifying reported server resource usage
- Added callback for overriding daemon server commands
- Added drop shadow to resource display for better visibility
- Added fullBackupCommand setting
- Added getMoveStatus API call
- Added new parameter to findServers API call to return all server details
- Added runScript/getScript API calls
- Added setting for forced templates per conf file allowing for fully automated mod installation
- Added support for using font icons instead of images
- Added theme configuration file to allow for more flexible theming of the panel
- Allow headers to be overridden in the main config file
- Allow server to start with nonexistent template
- Always allow superusers to edit a user theme
- Enabled online plugin list by default
- Expand variables in select server conf settings
- Fixed MySQL DB password update for some MySQL versions
- Fixed TERM signal not always being sent on Windows
- Fixed a rare issue where a scheduled task would never run depending on the scheduled time
- Fixed an error when creating a player without a server
- Fixed an issue where an invalid theme can prevent user profile display
- Fixed an issue where server console could become stuck
- Fixed backup buttons when using delayed daemon queries
- Fixed conf file daemon ID filter not always working correctly
- Fixed configuration reloading not working under certain conditions
- Fixed current page not being marked on lists with multiple pages
- Fixed daemon filter in getStatistics API call
- Fixed encoding issue with command cache under Windows
- Fixed local plugin list losing sort/filter settings when running a plugin action
- Fixed navbar overlapping with datepicker
- Fixed plugin downloads
- Fixed resource display on initial page load
- Fixed timezone in web FTP client
- Implemented CPU limit support for Docker containers
- Implemented IPv6 support for daemon connections
- Implemented SSL support for MySQL connections
- Implemented UDP support for Docker containers
- Implemented ability to get script output
- Implemented delayed daemon query setting to speed up page loads
- Implemented new JAR dropdown list with support for icons and lookup
- Implemented new full backup method with support for external directories
- Implemented new theme
- Implemented support for conditional scheduled tasks
- Implemented support for grouping parameters for the Startup Parameters feature
- Implemented support for stopping servers using signals instead of console commands
- Improved JAR/conf download compatibility
- Improved daemon list performance in server view
- Improved log output for failed scripts
- Improved plugin downloads to be faster for some sources
- PHP compatibility fixes
- Return memory usage of all daemons in getConnectionMemory API call when daemon ID is 0
- Updated libraries used to generate themes
- Use POST requests in sample API implementation if CURL isn't available

The preview release is available here:
Linux: Multicraft 2.4.0 Preview 64bit

We are releasing Multicraft 2.3.5 to address plugin download issues some installations are seeing and to facilitate future updates related to download issues. To that end we have implemented an external downloader binary that will be used by the daemon to download plugins.

Future updates that exclusively address plugin download issues can be installed by simply replacing the downloader without the need for a daemon update or restart.

To upgrade from 2.3.2 and later it’s sufficient to replace the «bin/multicraft» file of your daemon and copy the «downloader» directory from the archive to your daemon directory. Please make sure that none of these files are writable by «others» and that the «downloader/downloader» binary is executable.

Update — 05 Mar 2020
The downloader has been updated to address download issues with the Bukkit plugin list.

Update — 10 Mar 2020
The downloader has been updated to address download issues with the Spigot plugin list.
The release packages have been updated with a new downloader binary so if you are experiencing these issues and you are already running version 2.3.5 you can simply replace the «downloader» directory of your daemon. The SHA256 checksums have been updated for the new packages.

We are releasing Multicraft 2.3.4 to address plugin download issues some installations are seeing. These issues are caused by the lists hosting the plugins and/or the CDN they use to serve the downloads. To upgrade from 2.3.2 and later it’s sufficient to replace the «bin/multicraft» file of your daemon.

Multicraft release 2.3.3 is a maintenance release that addresses an issue with plugin downloads due to changes in the way these plugins are hosted.

We highly appreciate all feedback, bugreports and suggestions and we will continue improving Multicraft based on your feedback.

If you find a security relevant issue with Multicraft we also offer a bug bounty of up to 750$ per issue depending on severity.

UPDATE: In the mean time download restrictions have changed again, causing downloads to fail for some users. We have updated Multicraft again to version 2.3.3. Note that this upgrade is not required if you’re not seeing issues with file downloads in 2.3.2.
If you are already on 2.3.2 and you’re seeing download issues, please add the following two lines to the [multicraft] section of your multicraft.conf file:

downloadHeadersPlugins = {"Accept": "text/html,application/xhtml xml,application/xml;q=0.9,*/*;q=0.8", "Accept-Language": "en-US,en;q=0.5", "Accept-Encoding":"gzip, deflate", "User-Agent": "Mozilla/5.0 (Multicraft Plugin Manager) like FireFox/45.0", "DNT": "1", "Connection": "keep-alive"}
downloadHeaders = {"Accept": "text/html,application/xhtml xml,application/xml;q=0.9,*/*;q=0.8", "Accept-Language": "en-US,en;q=0.5", "Accept-Encoding": "deflate", "User-Agent": ""}

We appreciate all feedback, bugreports and suggestions. We will also award monetary bounties for certain security critical bugs, please contact us for details if you think you may have found an applicable bug.

Multicraft release 2.3.1 is a maintenance release that addresses several minor issues and updates some of the libraries used by Multicraft. A recent issue with certain downloads failing when using the plugin downloader has also been addressed.

Changelog:

We highly appreciate all feedback, bugreports and suggestions and we will continue improving Multicraft based on your feedback.

If you find a security relevant issue with Multicraft we also offer a bug bounty of up to 750$ per issue depending on severity.

Multicraft release 2.3.0 is now available after an extended period of testing as a preview release. There have been a number of minor fixes and improvements over the course of this preview release period. If you’re using any of the features mentioned in the changelog we do recommend upgrading to the final release.

We’re always looking for user feedback so if you’d like to see anything implemented or changed in Multicraft please do let us know, we continuously extend and improve Multicraft based on such feedback.

If you find a security relevant issue with Multicraft we also offer a bug bounty of up to 750$ per issue depending on severity.

The full changelog can be found further down in this post, heres an short list of a few highlights:

See the

Full Multicraft 2.3.0 Changelog

We highly appreciate all feedback, bugreports and suggestions and we will continue improving Multicraft based on your feedback.

The Windows installer for Multicraft has been updated to be more user friendly and more flexible. All services related to Multicraft (webserver, database server and Multicraft daemon) are installed as Windows services so you can start/stop them directly in the Windows service manager.

The installer is designed to support multiple installations in different locations. When re-installing to the same location it will keep existing user/server data. We still highly recommend backing up your user and server data prior to doing any changes to your installation.

Please let us know how the installer worked for you and if you have any suggestions for further improving it or additional feature requests.

We are commited to protecting your personal information and your right to privacy. We have always handled all personal data of our customers with great care and to comply with GDPR we have now also published our new privacy policy for you to review on our website:

Pricacy Policy

Please to let us know if you have any questions, concerns or general feedback regarding our privacy policy. You can always reach us using our contact form or by sending an email to info@shhost.ru.

We are announcing the availability of a new maintenance release for Multicraft. Version 2.2.1 fixes an issue related to plugin downloads using the online plugin list, an incompatibility with the Docker port range feature as well as several other minor issues.

Changelog:

As always, we highly appreciate all feedback, bugreports and suggestions and we will continue improving Multicraft based on your feedback.

We are very pleased to announce the release of version 2.2.0 of Multicraft! After several months of preview releases and after that several weeks of release candidate testing by us and customers who wanted to get early access to the new package we are marking the current build the final release of version 2.2.0.

There have once again been some minor fixes thanks to our Bug Bounty Program where we offer up to 750$ for relevant security issues.

The full changelog can be found further down in this post, heres an short list of a few highlights:

See the

Full Multicraft 2.2.0 Changelog

We highly appreciate all feedback, bugreports and suggestions and we will continue improving Multicraft based on your feedback.

Multicraft 2.1.1 has been released as a first maintenance release of the latest Multicraft version. This release contains mostly minor cosmetic changes and fixes as well as improvements to Docker support so upgrading is optional and only required if you are encountering any of the issues listed in the changelog.

On the daemon it is sufficient to replace the «bin/multicraft» binary. On the panel you can replace the panel files without running the install.php since there have been no database changes.

Changelog:

As always, we highly appreciate all feedback, bugreports and suggestions and we will continue improving Multicraft based on your feedback.

We are sorry to see the BukGet project being shut down and we would like to extend a warm thank you to the people who have maintained this project in the past.

If you are using Multicraft version 2.1 the plugin browser should continue working as expected.

In older versions of Multicraft the plugin browser will no longer work so we recommend updating to the latest version to address this. If that’s not (yet) possible for you the issue can be worked around temporarily by replacing line 14 (the API URL) of the «protected/models/BgPlugin.php» file with the following:

    static $apiUrl = 'https://plugins.multicraft.org/bg_compat/bukkit';

We are proud to announce the release of version 2.1.0 of Multicraft! As with previous releases we have begun offering preview releases for this version over an extended period of time, mainly to be able to quickly implement and adapt new features suggested by users without affecting users who wish to remain on a stable version. This release is again a result of a lot of user suggestions and we encourage any kind of feedback and feature requests for the next release. If you’re running a preview release we strongly recommend upgrading to the final 2.1.0 version.

We have been able to address some minor security related issue thanks to our Bug Bounty Program and we have raised the maximum reward to 750$ to encourage even more submissions.

The full changelog is once more too long to fit into the news entry so here’s a short list of the most important changes with the full list available below:

See the

Full Multicraft 2.1.0 Changelog

We highly appreciate all feedback, bugreports and suggestions and we will continue improving Multicraft based on your feedback.

The steady growth of Multicraft has motivated the creation of several apps for different platforms. While Multicraft comes with a mobile theme that works on most devices out of the box we wanted to highlight some community created apps that can help control your servers. Most apps support basic controls and server access and even multi-server management. All of these highlighted apps are completely free and they have been created independently, we are not affiliated with them in any way.

To use these apps a recent version of the control panel is required (2.0 ), also the hosting provider needs to supply an API key for you to enter to use the app.

(in order of last update)

  • Remote for Multicraft (Android)
    The Remote for Multicraft App is for Minecraft server admins that use Multicraft control panel. Connect to your Multicraft control panel to check your server status and players from your phone. Features:
  • MobileCraft (iOS)
    MobileCraft is the portable version for the famous hosting platform «Multicraft». It fits anyone from server hosts to casual server owners. All you need to have to control your server, just one click away.
    You can view your console, kick players, start and stop your server anytime of the day with just a click in MobileCraft.
    • Server management (start, stop, restart, delete, suspend, resume)
    • Console (view console, and send console commands)
    • Online players (kick and ban players directly from the app with a button)
    • User management (change password, delete users, list servers)
    • MYSQL database (create, change password)
    • And many more!
  • PocketPanel for Minecraft (Android)
    Server Administration shouldn’t be hard — now, it’s easy:

All Multicraft billing system modules are being updated for Multicraft 2.0. The Blesta module has already supported features that the other modules lacked but it’s also being updated for the latest changes in Multicraft. The WHMCS module is currently in beta at a lowered price and it’s expected to be released soon. The BoxBilling module has already been released and its documentation updated.

Blesta
The module supports most functions already, some new server fields will be added with the next release. The module is developed and maintained by Blesta so it’s included for free with the billing system.

WHMCS
The module has been overhauled to allow all settings to be configured with added support for configurable options and custom fields for any server/module setting. Changes and documentation can be found here. Once it’s released the new module can be requested through a support ticket from an address that has previously purchased the module.

BoxBilling
The module has been updated for the latest version of BoxBilling and additional server/module settings have been added. The updated documentation can be found here. The new module can be requested through a support ticket from an address that has previously purchased the module.

Multicraft 2.0.1 has been released as a first maintenance release of the latest Multicraft version. This release contains mostly minor cosmetic changes and fixes so upgrading is optional and only required if you are encountering any of the issues listed in the changelog.

On the daemon it is sufficient to replace the «bin/multicraft» binary. On the panel you can replace the panel files without running the install.php since there have been no database changes.

As always, we highly appreciate all feedback, bugreports and suggestions and we will continue improving Multicraft based on your feedback.

We are proud to announce the release of version 2.0.0 of Multicraft! A lot of effort has gone into making sure that we can implement as many user suggestions as possible with this new version of Multicraft to make it even more powerful and easy to use. The release has been postponed a number of times because of feature requests that we consider to be very useful to the vast majority of Multicraft users. Due to this we have begun offering preview releases for download longer before the final release than usual. If you’re running a preview release we strongly recommend upgrading to the final 2.0.0 version.

In addition to implementing countless new features and improvements we have also been able to make Multicraft even more secure thanks to the researchers who have contributed to our Bug Bounty Program we have running with Bugcrowd.

As part of this release we are replacing the Windows all-in-one package with the Multicraft Bitnami Stack for Windows for personal use. There is also a Multicraft Bitnami Stack for Linux that we recommend for personal use if you cannot install all requirements for Multicraft. For hosting providers we still recommend using our Linux packages for maximum security and flexibility.

In good Multicraft tradition the length of the changelog is record breaking. There have been so many new features and changes that even a summarized list of the most important changes would be too long for this news entry so here’s just a small selection:

See the

Full Multicraft 2.0.0 Changelog

We highly appreciate all feedback, bugreports and suggestions and we will continue improving Multicraft based on your feedback.

As a last step before the finalization of the new release we have ordered a security review for Multicraft and we have launched a Bug Bounty program with the good folks over at

Bugcrowd

.

The program has initially been launched as private so if you’re interested in participating and earning monetary rewards for reporting security critical bugs please head over to

bugcrowd.com

to register for a researcher account.
Once you have done so please let us know so we can add you as a researcher to our program.

The bug bounty program will be made public in the future once we have left the initial selection of researchers enough time to review the code.

We are happy to announce that the good folks over at

Blesta

have developed a module to fully support Multicraft with their billing software platform. A video of the module in action can be seen in their blog entry regarding this development:

Blesta Blog: New Multicraft Module

The module is part of the official v3.3 release of Blesta so you do not have to install any addons to use this module. If you are using an older version of Blesta you can download the module separately from this forum post.

The documentation for this new module can be found here:
Blesta Multicraft Module Documentation

You can try the new module without obligation by installing the free trial of Blesta and connecting it to your existing Multicraft installation.

We will also be sending out 15% discount coupons for Blesta owned licenses with every new purchase of any Multicraft license.

Pocketmine-mp


PocketMine-MP can be run using the pocketmine.phar.conf file below. Thank you to Shoghi from pocketmine.net for providing this file!

The following instructions can be used to start a PocketMine-MP server:

Requirements

For the all-in-one package you only need to have Java installed.

For all the packages the following requirements have to be fulfilled:


Excellent tutorials on how to set up these requirements for recent systems can be found over at DigitalOcean:

Secure mysql

A first step should always be to run «mysql_secure_installation»:

mysql_secure_installation

Say «Y» to all questions (except for the first one if you don’t want to change the root password).

Server templates (new in 2.0.0)

The server template feature has been added in Multicraft 2.0.0 to make it easier to deploy mods and pre-installed servers. Templates can consist of files and scripts that are used to initialize the server directory.

The basic function of a template is to provide a set of files that will be copied to the server directory before the server starts. To achieve this all you have to do is to create a new folder in the «templates» directory of your daemon (by default «/home/minecraft/multicraft/templates») and put all files you want to have copied to a server into the «files» directory within your new template folder.

Special scripts

The following script names are reserved as they have special functions:

Spigot and bungeecord

You can simply download the

file and place it in the «jar» directory of your daemon to be able to use Spigot/BungeeCord like Craftbukkit or vanilla Minecraft.

Alternatively you can directly add Spigot/BungeeCord in your panel using the following values under Settings->Update Minecraft->Add or Remove Files:

In the first field enter either «spigot.jar» or «bungeecord.jar». Leave the «File URL» empty and for the «Conf URL» enter one of the following depending on the JAR you wish to install:

Upgrading

See the

page.

What others say

See our long list of customer feedback to find out

Your advantages


In terms of features Multicraft is currently unrivaled (

) but of course features aren’t everything. The following is a comparison of a few of the things Multicraft does better than the competition.

Send mails using smtp instead of php mail()

If you want to send emails directly through an SMTP server instead of using the PHP mail() function you can edit the file

protected/config/internal/application.php

and look for the line:

'transportType'=>'smtp'

Оцените статью
Хостинги