Configuration

Summary – Configuration: config.yml & lang.yml

Main Page Purpose

The main page of the “Configuration” section acts as a hub, helping users quickly understand the structure and find the right configuration file to edit. It provides context, directs users to detailed subpages, and explains the importance of each file. This organization improves clarity, especially for new staff or server owners, and ensures efficient navigation between the different aspects of plugin setup.

Part 1: config.yml Configuration

• Purpose: The config.yml file manages the main settings of LifeMod, including plugin behavior, enabled features, Discord integration, command toggles, and moderation tool customization.

• Key Features:

  • Centralizes all core plugin options.

  • Lets you enable/disable commands and features.

  • Supports Discord webhook integration for alerts.

  • Customizes moderation items (names, descriptions, materials, slots).

  • Provides help menu and plugin/server info sections.

• Customization:

  • Adapt the prefix, colors, and item names to fit your server branding.

  • Add/remove moderation tools and adjust their appearance in the GUI.

  • Use variables like %player%, %message%, %plugin_version% for dynamic content.

• Best Practices:

  • Always back up your file before editing.

  • Use /lifemod reload to apply changes instantly.

  • Keep formatting consistent for a professional look.

Part 2: lang.yml Configuration

• Purpose: The lang.yml file centralizes all messages shown to players and staff, allowing full customization of feedback, notifications, and command responses.

• Key Features:

  • Organizes messages by command and function (errors, system, moderation, etc.).

  • Supports dynamic variables (%player%, %target%, %prefix%, etc.).

  • Allows tone and language adaptation for your community.

  • Includes GUI titles, help menus, update notifications, and more.

• Customization:

  • Change messages for clarity, humor, or branding.

  • Use color codes for readability and emphasis.

  • Adjust messages for accessibility (colorblind-friendly, concise).

• Best Practices:

  • Always back up your file before editing.

  • Test all changes with /lifemod reload to avoid display errors.

  • Maintain consistency in tone and formatting.