Flectone Logo FlectonePulse

Module

Configuration for the core module of FlectonePulse

Information

If you encounter an error related to ASM when loading libraries, try starting the server with the flag -Dload.asm.jar=false (for example java -Dload.asm.jar=false -jar server.jar). This disables FlectonePulse's own loading of asm libraries and may resolve issues with custom cores or plugins


⚙️ Setting

Path config.yml → module
module:
  enable: true
  use_paper_message_sender: false
  use_bukkit_pre_login_listener: false

enable

Enables or disables the operation of all modules.

  1. Every module has a parent (the one located above it).
Example
house:
  door:
  chair:

house is the parent of door and chair.

  1. Every module depends on the parent's enable status.
Example
house:
  enable: false
  door:
    enable: true
  chair:
    enable: true

house is disabled, which means regardless of whether door and chair are enabled, they will also be disabled.

use_paper_message_sender

If enabled, FlectonePulse will use Paper as a tool for sending messages to a player's chat.

How does it work? First, the plugin creates a message internally and obtains FlectonePulse.Component; this object is converted into a standard String. Then, Paper itself is used to derive a Paper.Component from this string and send it to the player.

Warning

For this to work, PacketEvents must be installed on the server as a separate plugin, and the server core must be Paper or its fork.

use_bukkit_pre_login_listener

If enabled, for versions 1.20.2 and above, the Bukkit player login listener will be used instead of packets from PacketEvents. On lower versions, this listener is already used.

This resolves issues with plugins that interact with the player during login. For example, plugins that create fake players will only work with this setting enabled.


🔐 Permissions

Path
module:
  name: "flectonepulse.module"
  type: "TRUE"

name

Permission name

type

Permission type

TypeExplanation
TRUEAvailable to any player
FALSEAvailable to no one, must be granted separately (e.g., using LuckPerms)
OPAvailable to server operators
NOT_OPAvailable to NON-operators of the server

Last updated on

Edit on GitHub

On this page

Authors of page