Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/xMrAfonso/Runway/llms.txt

Use this file to discover all available pages before exploring further.

This page covers common issues you might encounter with Runway and how to resolve them.

​
Common Issues

If your messages aren’t being formatted even with the [mm] prefix:Check your configuration:
  • Verify require-prefix.minimessage is set to true in config.yml
  • Ensure the prefix is included somewhere in the message text
  • The prefix can be at the beginning, middle, or end of the message
Enable the appropriate listener:
  • Check if the relevant listener is enabled in config.yml
  • For example, if system messages aren’t working, ensure listeners.system-messages: true
Test with prefix disabled:
require-prefix:
  minimessage: false
If this works, the issue is with prefix detection. Re-enable and verify prefix placement.
You may see this warning in console:
Detected Legacy colors! Runway is now ignoring legacy colors.
To avoid receiving this message again, disable legacy colors in the config.
What this means:
  • Runway detected legacy color codes (§) in a message
  • These codes are automatically converted to & to prevent conflicts
  • The plugin automatically enables ignore-legacy: true
To resolve:
  1. Update your messages to use MiniMessage format instead of legacy codes
  2. Set ignore-legacy: true in config.yml to suppress the warning
  3. Legacy codes will be replaced with & and treated as literal text
Example migration:
# Old (legacy)
"§aGreen text §cRed text"

# New (MiniMessage)
"[mm]<green>Green text</green> <red>Red text</red>"
If you see warnings about PlaceholderAPI not being found:Check plugin installation:
  • Ensure PlaceholderAPI is installed in your plugins folder
  • Download from Hangar
  • Restart your server after installing
Verify configuration:
placeholder-hook:
  placeholderapi: true  # Must be enabled
Note: PlaceholderAPI is optional. If you don’t need placeholders, set it to false.
Similar to PlaceholderAPI, if MiniPlaceholders warnings appear:Install MiniPlaceholders:
  • Download from Hangar
  • Place in your plugins folder
  • Restart the server
Enable in config:
placeholder-hook:
  miniplaceholders: true
Note: You can use both PlaceholderAPI and MiniPlaceholders simultaneously.
If placeholders show as literal text:Verify prefix usage:
  • Placeholders require both [mm] and [p] prefixes by default
  • Example: [mm][p]Hello %player_name%!
Check prefix requirements:
require-prefix:
  minimessage: true
  placeholders: true  # Requires [p] prefix
Disable prefix requirement:
require-prefix:
  placeholders: false  # Parse all placeholders automatically
Ensure placeholder plugin is enabled:
  • PlaceholderAPI or MiniPlaceholders must be installed
  • Hook must be enabled in Runway’s config
  • Required expansions must be downloaded (for PlaceholderAPI)
If item names and lore aren’t being formatted:Enable item listeners:
listeners:
  items: true  # For held items, drops, etc.
  inventory:
    items: true  # For inventory GUI items
Check italic settings: By default, Runway disables italics in item text:
disable-italics: true
If you want italics, set this to false.
Enable the appropriate listeners:
listeners:
  tablist: true    # For tablist header/footer
  titles: true     # For title and subtitle
Reload the plugin:
/runway reload
After modifying config.yml:Reload the plugin:
/runway reload
If reload doesn’t work:
  • Check console for configuration errors
  • Verify YAML syntax (indentation, colons, etc.)
  • Restart the server as a last resort
Minimum requirements:
  • Paper 1.20.6 or higher (earlier versions are untested)
  • Java 21
Folia support:
  • Runway fully supports Folia servers (folia-supported: true)
Protocol compatibility:
  • Runway uses PacketEvents for protocol-level modifications
  • Should work with ViaVersion, ViaBackwards, and ViaRewind
  • Older client versions may have limited MiniMessage support
If Runway conflicts with another plugin:Disable specific listeners: Disable only the conflicting listener:
listeners:
  system-messages: false  # Example: disable if conflicting
Check load order:
  • Runway loads before optional dependencies (PlaceholderAPI, MiniPlaceholders)
  • Check paper-plugin.yml for dependency order
Report compatibility issues:
  • Contact the developer on Discord: @mrafonso
  • Open an issue on GitHub with details about both plugins

​
Testing Your Setup

Use the parse command to test MiniMessage formatting: 
/runway parse <gradient:red:blue>Test Message</gradient>
This will show you how Runway processes your text in real-time.

​
Getting Help

If your issue isn’t covered here:
  • Check the FAQ for common questions
  • Contact via Discord: @mrafonso
  • Open an issue on GitHub
When reporting issues, include:
  • Runway version
  • Server software and version (Paper, Folia, etc.)
  • Java version
  • Relevant config sections
  • Console errors or warnings

Build docs developers (and LLMs) love

Get started for freeTalk to us