что такое bukkit yml

MySQL Configuration example:

Note: , , , , and are not actual variable names that Bukkit uses like in the SQLite example. They just represent data you should change to get the MySQL configuration to work correctly.

*OPTIONAL* worlds

This section lets you define the generators for the worlds that bukkit loads by default.

Источник

Configuring Bukkit’s bukkit.yml Quick and Easy for 1.17

Bukkit is a Mod for Minecraft that provides a plugin API for the Minecraft Server that came out in 2011. It provides an easy way to customize the Vanilla experience, allowing you to install plugins that can change every bit of the server. While previously being maintained at https://bukkit.org, the project is now primarily maintained by SpigotMC.

Configuring Bukkit can be a little difficult, so here’s a full breakdown of configuring the bukkit.yml that’s generated by default when you run Bukkit.

Quick Definitions:

settings

This section is used to define generic settings that the Minecraft Server will follow. None of these settings will improve performance, and are just configuration for Bukkit.

settings.allow-end (default: true )

settings.warn-on-overload (default: true )

This configuration option is added by Bukkit to alert you when your server is running behind. It will send a message that looks like:

settings.permission-file (default: permissions.yml )

This setting sets the default permission file, which is generally used to group permission nodes together. We’re not going to go in-depth on the file format here, but you can find the Bukkit Wiki article here.

settings.update-folder (default: update )

settings.plugin-profiling (default: false )

settings.connection-throttle (default: 4000 )

settings.query-plugins (default: true )

This option is used when the Minecraft Server is asked about what plugins it has installed in two different spots:

settings.deprecated-verbose (default: default )

This option is used in several places regarding whether the server will report on a plugin doing deprecated actions. It should be left to default unless you have a reason to use it in another mode ( off / on ).

settings.shutdown-message (default: Server closed )

settings.minimum-api (default: none )

spawn-limits

This section is used to define how many of each entity type can spawn in the world. This can be used to improve performance a lot, especially because ambient (bats) and water-animals/water-ambient mobs do not need as high of a count as these defaults. Reducing these values can reduce the amount of entities that are attempted to be spawned, improving performance.

chunk-gc

The chunk-gc.period-in-ticks allows you to configure how long a chunk loaded by a plugin stays loaded. Generally this shouldn’t need to be changed.

ticks-per

This section is used to define how often certain systems in the game get ticked. It can be used to tune your server performance, specifically reducing how much mob spawning hurts the performance.

These settings have a few possible options for configuration.

ticks-per.autosave (default: 6000 )

Bukkit allows you here to configure how often the worlds and player data is saved. You should set this value as high as you can tolerate data loss, which the default 5 minute ( 6000 ticks ) is generally a good default for this.

If for some reason you’d like to not save this data, you can set it to 0 to disable the autosave.

aliases

Finishing Up

If you’d like to read more articles about configuring and optimizing your 1.17 Minecraft Server, they’re coming soon!

Источник

BukkitWiki

This Wiki is home to Bukkit’s documentation and regulations surrounding the Bukkit Project and it’s services. Want to help out? We would love to have you! Signup to get started!

Commands.yml

commands.yml is a configuration file that houses custom defined aliases and command block overrides for your CraftBukkit server.

The command block override system provides a quick and easy way to force the server to use the commands provided by Mojang (as opposed to the ones built into Bukkit) for command blocks specifically, leaving all other commands untouched. While the aliases system, essentially, gives power user server admins the ability to define custom commands and force specific versions of a command to be used for the default commands.

Out of the box, Bukkit provides a useful fallback system for commands that has the following priorities:

On top of this, we provide untouchable ultimate fallbacks for every command which can be used by users or the Aliases system to use specific versions of a command:

Of course, for each fallback we also provide permissions to allow you to control access to each command (except for Plugin Commands which depend on the plugin’s handling of permissions):

Contents

Default commands.yml

command-block-overrides

This section of the commands.yml controls what is known as the command block overrides feature. Since Bukkit has historically provided its own version of some Minecraft commands, we’ve added the ability to force the server to use the Mojang provided version for command blocks specifically. Commands used outside of command blocks will use the Bukkit (or plugin) version as usual.

Note: Since Bukkit has no control over the Mojang version of a command, we cannot guarantee that they will work as expected.

If the custom map you’re running uses the /summon and /give commands, you probably want to enable command block overrides for them. To do this, you simply add them to the command-block-overrides list and your commands.yml would look something like this:

If, on the other hand, the custom map uses most of the Minecraft commands, you can also easily enable command block overrides for all valid commands by using a *, like so:

aliases

This section of the commands.yml allows you to define custom aliases for commands on your server. At its core, an alias allows you to create custom commands that can perform multiple functions at once. This is a powerful tool that allows you to define easier to remember commands for your server staff.

Alongside letting you redefine commands, the Aliases System provides extra useful features that allow you to create some powerful custom commands for you server:

Alias Examples

Add an alternative way to run the /version command

In this example we’re registering an alias called «icanhasbukkit» which will execute the version command when used.

Removing a command

In this example we’re registering an alias called ‘summon’ that is mapped to nothing. By doing this, we are telling the server to unregister the command and, as a result, prevent it from existing/functioning.

Note: If you are looking to prevent people from using a command, you should remove their permission to use the command instead of removing it with an alias.

Rename the /version command

In this example we’re registering an alias called «icanhasversion» which will execute the version command when used and creating an alias called «version» that is mapped to nothing to remove it.

Note: If you are looking to prevent people from using a command, you should remove their permission to use the command instead of removing it with an alias.

Requiring a parameter

In this example we’re creating an alias called ‘givedirt’ that requires providing an argument (in this case a player’s name) before the alias will successfully run.

Running multiple commands

In this example we’re creating an alias called ‘givedirtmsg’ which will execute two commands that require an argument before the alias will successfully run.

Using a command supplied by a plugin

In this example we’re overriding the built in /time command to use the version supplied by the plugin ScrapBukkit instead.

Using a command supplied by Mojang

In this example we’re overriding the built in /time command to use the version supplied by Mojang instead.

Using a command supplied by Bukkit

In this example we’re overriding the built in /time command to use the version supplied by Bukkit instead.

Accepting all parameters

In this example we’re creating an alias called ‘broadcast’ that will execute the ‘say’ command and accept any arguments passed to it.

Requiring the first parameter while keeping the second optional

In this example we’re overriding the built in ‘ban’ command. This alias will require the first argument (which in this case is a player’s name) while providing support for an optional ban reason. When the alias is used, the player will be banned and a /say message will be broadcasted, informing the people on the server that someone has been banned.

Источник