While we prefer to make things easy at CubedHost, this is one of the legacy items brought over from our old control panel that have not made its way into our Prisma control panel just yet. Fortunately, that's on the roadmap, but has some complications due to supporting other games/services in the future; available easily in Prisma soon!

There are a number of items that can be changed using our .tweaks file included with every Minecraft: Java Edition server. Below, you can find the appropriate options.

Java Garbage Collection & Memory Settings

Every server is different and may require different tweaks. We've exposed some options so that you can make the most of your server with us. If you have suggestions or feedback, we welcome you to contact us at any time using the blue button (Intercom) at the bottom right of any page.

GC Logging (Advanced Users Only)

Java's garbage collection logging allows you to log information regarding runtime statistics and information useful for tweaking the GC settings. This will be more prominently useful in the future with some additions we expect to offer.

.tweaks file excerpt:

## Java Garbage Collection Logging
#
# Possible values: true, false
# Default: false
#
# Toggles logging of GC information to a log file in your server's root directory.
# This can be helpful when you're trying to isolate the source of lag and/or
# memory-related performance issues. Check "gc.log" after enabling and restarting
# your server.
#
# i.e. -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -Xloggc:gc.log
#
gc-logging=false

Garbage Collection Type

This allows you to set the "type" of garbage collection settings you'd like to run; by default, this is auto; allowing our startup tools to determine the best presets for your server. To learn more, please click here.

## Java Garbage Collection Settings
#
# Possible values: auto, cms, g1, optimal, minimal
# Default: auto
#
# For additional information our Garbage Collection groups, please see:
# https://cubed.host/java-gc
#
gc-type=auto

Metaspace Maximum

Sometimes, servers will need additional Metaspace (pre-Java 8: PermGen) memory in order to operate, as the server may have too many Java class files to load and not enough memory.

By default, we provide 256MB included (for free) with every server. Any additional memory can be pulled from your server's memory allocation and set at any time. For example, if you have a 4GB server (4,096MB), need 384MB (128MB + 256MB), you will have 3,968MB (3.875GB) available for your server's Java Heap memory. For a complete explanation, please see this article (click here).

## Metaspace Maximum (in MB)
#
# Possible values: 256 up to 1024
# Default: auto (256 + (64 * ((Memory Max - 1024) / 1024)))
#
# Sets the maximum amount of metaspace allocated to your server.
# This is helpful in the situation that your server runs out of Metaspace memory.
# When increasing the maximum Metaspace memory to > 256MB, the additional memory
# above 256MB will be deducted from your server's usable heap memory.
#
# For example, if you allocate 512MB Metaspace memory on a 4GB server, your
# usable heap memory will be 3.75GB (0.25GB or 256MB less) to accommodate for the
# additional requested Metaspace memory.
metaspace-max=auto

Enable Graal JVMCI JIT Compiler (Experimental)

GraalVM provides the potential of various experimental runtime performance improvements.

## Enable Graal JVMCI JIT Compiler
# Possible values: true, false
# Default: false
#
# Enables or disables the new JIT compiler that offers experimental
# runtime performance improvements.
enable-graal=false

Minecraft: Java Edition Tweaks

From time to time, vanilla Minecraft will introduce new functionality that will offer various options in-game or repair the game. This section covers the options we've implemented.

Force Upgrade / Optimize World (1.13+)

As of 1.13, you can now run the Force Upgrade or Optimize World option on your server, similarly to what you'd see in singleplayer Minecraft. This will ensure your world format is updated to the latest version of Minecraft: Java Edition. This option does NOT disable itself after first run, so please be sure to disable it after starting the server.

## Force Upgrade (1.13+) / Optimize World
#
# Possible values: true, false
# Default: false
#
# Forcefully upgrade the full world prior to the start of the server.
# This option should be disabled after the first successful run and does not automatically disable itself.
#
## It is HIGHLY recommended that you complete a backup prior to enabling this!
#
force-upgrade=false

Erase Cache (1.14+)

This will erase various caches, including lighting, in your Minecraft: Java Edition world. When this is enabled, it is assumed that force-upgrade is to be enabled as well; force-upgrade does not need to be enabled explicitly. This option does NOT disable itself after first run, so please be sure to disable it after starting the server.

## Erase Cache (1.14+)
#
# Possible values: true, false
# Default: false
#
# Forcefully erases world caches, such as lighting, height maps, etc.
# This option should be disabled after a successful run and does not automatically disable itself.
#
## It is HIGHLY recommended that you complete a backup prior to enabling this!
## Please Note: force-upgrade is implied as enabled with this option.
#
erase-cache=false

Enable Debug Method Profiler

This option will enable the /debug profiler in vanilla Minecraft. This may be enabled by default in various builds, but as it was disabled by default with 1.13, it was left disabled by default in our tweaks. If the debug profiler option is set to false, this will not explicitly disable it in-game, it will simply omit the option from the command line entirely. If you have a specific use case that requires explicit disabling, please reach out to our team and we'll modify the behavior (may take up to 24 hours).

## Enable Debug Method Profiler
#
# Possible values: true, false
# Default: false
#
# Enables or disables the /debug method built into Minecraft.
enable-debug-profiler=false
Did this answer your question?