Serversigns что за плагин
Описание плагина ServerSigns:
Команды плагина ServerSigns:
/svs add — Добавляет команду на табличку;
/svs edit — Изменяет табличку;
/svs list — Листок табличек.
Список всех команд: ТЫК
Права плагина ServerSigns:
Права для игроков:
serversigns.use.* — Позволяет использовать все таблички ServerSigns на сервере
serversigns.use — Позволяет использовать все таблички ServerSigns, у которых нет специального набора разрешений
serversigns.use.promote — Позволяет использовать все таблички ServerSigns, для которых установлено разрешение «promote»
Права для админов:
serversigns.admin — Предоставляет доступ ко всем функциям ServerSigns.
serversigns.updatenotification — Позволяет видеть уведомления об обновлениях в чате
serversigns.command.add — Доступ к команде /svs add
serversigns.command.set_cancel — Доступ к команде /svs setcancel
serversigns.command.cancel_permission — Доступ к команде /svs cancelpermission
serversigns.command.confirmation — Доступ к команде /svs confirmation
serversigns.command.copy — Доступ к команде /svs copy
serversigns.command.create — Доступ к команде /svs create
serversigns.command.edit — Доступ к команде /svs edit
serversigns.command.grant — Доступ к команде /svs grant
serversigns.command.held_item_criteria — Доступ к команде /svs hic
serversigns.command.holding — Доступ к команде /svs holding
serversigns.command.import — Доступ к команде /svs import
serversigns.command.insert — Доступ к команде /svs insert
serversigns.command.list — Доступ к команде /svs list
serversigns.command.long — Доступ к команде /svs long
serversigns.command.option — Доступ к команде /svs option
serversigns.command.price_item — Доступ к команде /svs pi
serversigns.command.price_item_criteria — Доступ к команде /svs pic
serversigns.command.reload — Доступ к команде /svs reload
serversigns.command.reload_config — Доступ к команде /svs reloadconfig
serversigns.command.reload_signs — Доступ к команде /svs reloadsigns
serversigns.command.remove — Доступ к команде /svs remove
serversigns.command.reset_all_cooldowns — Доступ к команде /svs resetallcd
serversigns.command.reset_cooldown — Доступ к команде /svs resetcd
serversigns.command.resetcooldowns — Доступ к команде /svs resetcooldowns
serversigns.command.set_cooldown — Доступ к команде /svs setcooldown
serversigns.command.select — Доступ к команде /svs select
serversigns.command.set_cooldown — Доступ к команде /svs setcooldown
serversigns.command.set_global_cooldown — Доступ к команде /svs setglobalcooldown
serversigns.command.set_loops — Доступ к команде /svs setloops
serversigns.command.set_permission — Доступ к команде /svs setpermission
serversigns.command.set_price — Доступ к команде /svs setprice
serversigns.command.set_price — Доступ к команде /svs setprice
serversigns.command.set_uses — Доступ к команде /svs setuses
serversigns.command.silent — Доступ к команде /svs silent
serversigns.command.timelimit — Доступ к команде /svs timelimit
serversigns.command.void — Доступ к команде /svs void
serversigns.command.xp — Доступ к команде /svs xp
Часто задаваемые вопросы по плагину ServerSigns :
Как я могу отправить сообщение игроку с помощью ServerSign?
Есть несколько способов отправить игроку сообщение, но все они включают команду «/svs add». Вот несколько примеров:
Почему игроки не могут использовать созданные мной таблички?
ServerSigns
The Bukkit Plugin ServerSigns provides the ability to bind commands, messages and actions to signs and every other block in Minecraft.
As soon as a player clicks on a ServerSign, the configured actions are executed in the order and with the settings you specified.
Download ServerSigns at bukkit.org
Download ServerSigns at bukkit.orgMain Features:
ServerSigns has been developed, maintained and regularly updated since 2011. Starting with only the possibility to bind simple commands to a sign, it has become a large and feature rich Bukkit Plugin.
Some of the main features:
Help Pages / Documentation
Installation
Configuration
Permissions
Command Reference
Frequently Asked Questions (FAQs)
Reporting Bugs / Requesting Features
When reporting bugs, requesting features, or providing any other constructive feedback that will require code alterations you must submit a ticket here to have your voice heard and action taken (if required). Any topics of this nature that are presented through any other means will henceforth be ignored.
Before you create a ticket, you need to make sure that the feature you are requesting isn’t already implemented (read all of the wiki pages which show ServerSigns features), or the bug you want fixed hasn’t already been resolved in the latest development build (a rolling change log is kept on the development build page, use this for reference)
Once you have submitted a ticket, rest assured that it will be handled. We do not give a definite time frame for replies or actual alterations, but we try our absolute best to get tickets resolved as soon as possible. Please do not: bump tickets, raise multiple tickets for the same issue, send PMs to our developers, or discuss the ticket in the comments section. Tickets that do not meet the expectations outlined here will likely be declined without comment.
Bukkit
ServerSigns
Bukkit Plugins
ServerSigns
Table of Contents
Please check our Wiki before asking questions or submitting tickets
ServerSigns (SVS) provides the ability to bind player-dispatched and server-disptached commands, messages and actions to signs and every other block in Minecraft.
As soon as a player clicks on a ServerSign, the configured actions are executed in the order and with the settings you specified.
Main Features:
Please note that version 2.6 and above will notify you when a ServerSigns developer joins, this is so you’re aware of who we are when we join, and we can help you with any issues you may be having with ServerSigns as quickly as possible. Version 4.1 and above will also send the developer a message stating the current plugin version.
This plugin utilizes an auto-updating feature that will check for the latest ServerSigns build and automatically download that build if it is newer than the currently installed one. This can be disabled by setting ‘check_for_updates’ to false in the config.yml
This plugin uses Metrics to gather basic non-identifiable statistical data such as the number of ServerSigns you are using, your plugin version, and other standard mcstats.org data. You can opt-out of this feature by setting ‘metrics_opt_out’ to true in the config.yml. A full list of gathered information can be found here: http://mcstats.org/plugin/ServerSigns
Click Here to view Tutorial Videos
Known bugs
Reporting Bugs / Requesting Features
When reporting bugs, requesting features, or providing any other constructive feedback that will require code alterations you must submit a ticket to have your voice heard and action taken (if required). Any topics of this nature that arise in the comments section will henceforth be ignored.
Before you raise a ticket, you need to make sure that the feature you are requesting isn’t already implemented (read all of the help pages which show SVS features), or the bug you want fixed hasn’t already been resolved in the latest development build (a rolling change log is kept on the development build page, use this for reference)
Once you have submitted a ticket, rest assured that it will be handled. We do not give a definite time frame for replies or actual alterations, but we try our absolute best to get tickets resolved as soon as possible. Please do not: bump tickets, raise multiple tickets for the same issue, send PMs to our developers, or discuss the ticket in the comments section. Tickets that do not meet the expectations outlined here will likely be declined without comment.
Bukkit
ServerSigns
Bukkit Plugins
ServerSigns
Table of Contents
Please check our Wiki before asking questions or submitting tickets
ServerSigns (SVS) provides the ability to bind player-dispatched and server-disptached commands, messages and actions to signs and every other block in Minecraft.
As soon as a player clicks on a ServerSign, the configured actions are executed in the order and with the settings you specified.
Main Features:
Please note that version 2.6 and above will notify you when a ServerSigns developer joins, this is so you’re aware of who we are when we join, and we can help you with any issues you may be having with ServerSigns as quickly as possible. Version 4.1 and above will also send the developer a message stating the current plugin version.
This plugin utilizes an auto-updating feature that will check for the latest ServerSigns build and automatically download that build if it is newer than the currently installed one. This can be disabled by setting ‘check_for_updates’ to false in the config.yml
This plugin uses Metrics to gather basic non-identifiable statistical data such as the number of ServerSigns you are using, your plugin version, and other standard mcstats.org data. You can opt-out of this feature by setting ‘metrics_opt_out’ to true in the config.yml. A full list of gathered information can be found here: http://mcstats.org/plugin/ServerSigns
Click Here to view Tutorial Videos
Known bugs
Reporting Bugs / Requesting Features
When reporting bugs, requesting features, or providing any other constructive feedback that will require code alterations you must submit a ticket to have your voice heard and action taken (if required). Any topics of this nature that arise in the comments section will henceforth be ignored.
Before you raise a ticket, you need to make sure that the feature you are requesting isn’t already implemented (read all of the help pages which show SVS features), or the bug you want fixed hasn’t already been resolved in the latest development build (a rolling change log is kept on the development build page, use this for reference)
Once you have submitted a ticket, rest assured that it will be handled. We do not give a definite time frame for replies or actual alterations, but we try our absolute best to get tickets resolved as soon as possible. Please do not: bump tickets, raise multiple tickets for the same issue, send PMs to our developers, or discuss the ticket in the comments section. Tickets that do not meet the expectations outlined here will likely be declined without comment.
Bukkit
ServerSigns
Bukkit Plugins
ServerSigns
Table of Contents
Please check our Wiki before asking questions or submitting tickets
ServerSigns (SVS) provides the ability to bind player-dispatched and server-disptached commands, messages and actions to signs and every other block in Minecraft.
As soon as a player clicks on a ServerSign, the configured actions are executed in the order and with the settings you specified.
Main Features:
Please note that version 2.6 and above will notify you when a ServerSigns developer joins, this is so you’re aware of who we are when we join, and we can help you with any issues you may be having with ServerSigns as quickly as possible. Version 4.1 and above will also send the developer a message stating the current plugin version.
This plugin utilizes an auto-updating feature that will check for the latest ServerSigns build and automatically download that build if it is newer than the currently installed one. This can be disabled by setting ‘check_for_updates’ to false in the config.yml
This plugin uses Metrics to gather basic non-identifiable statistical data such as the number of ServerSigns you are using, your plugin version, and other standard mcstats.org data. You can opt-out of this feature by setting ‘metrics_opt_out’ to true in the config.yml. A full list of gathered information can be found here: http://mcstats.org/plugin/ServerSigns
Click Here to view Tutorial Videos
Known bugs
Reporting Bugs / Requesting Features
When reporting bugs, requesting features, or providing any other constructive feedback that will require code alterations you must submit a ticket to have your voice heard and action taken (if required). Any topics of this nature that arise in the comments section will henceforth be ignored.
Before you raise a ticket, you need to make sure that the feature you are requesting isn’t already implemented (read all of the help pages which show SVS features), or the bug you want fixed hasn’t already been resolved in the latest development build (a rolling change log is kept on the development build page, use this for reference)
Once you have submitted a ticket, rest assured that it will be handled. We do not give a definite time frame for replies or actual alterations, but we try our absolute best to get tickets resolved as soon as possible. Please do not: bump tickets, raise multiple tickets for the same issue, send PMs to our developers, or discuss the ticket in the comments section. Tickets that do not meet the expectations outlined here will likely be declined without comment.