Bukkit

Config options

• allow-stacking - Allows sign posts to be built on top of sign posts; if false, an attempt to stack sign posts will result in the edit window appearing.
• break-protect - Protect signs from being broken by people other than their owner. Obviously signs owned by everyone can then be broken by everyone.
• orphaned-breakable - If the above is set to true, this controls whether signs owned by no-one can be broken by anyone.
• sneaking - One of "true", "false", or "both"; if true, you must be sneaking to edit signs, and if false, you must not be sneaking to edit signs. The default, "both", means that your sneaking status is not checked when determining if you should edit the sign.
• view-owner - The ID of the item used to see the owner of a sign by right-clicking. Defaults to stick.
• set-owner - The ID of the item used to set the owner of a sign by right-clicking. Defaults to feather
• auto-save - If set to false, SimpleSignEdit will not save the configuration on reload and shutdown. This is necessary if you want to be able to edit the config and then /reload to make the changes live. It will be ignored if you're not using a database. Defaults to true.
• default-owner - All newly placed signs will be set to have this owner. Valid values are the name of a player or one of the strings "placer" (indicating the player who placed it is the owner), "none" (indicating no-one owns it), and "*" (indicating everyone owns it).
• use-lwc - Use LWC to determine who can edit signs, if it is available. Normally SimpleSignEdit will continue to store sign ownership in its own database even when LWC is enabled; if you don't want this, see the next section. SimpleSignEdit will not automatically convert all your sign ownership data between LWC and its own database; however, ownership of a sign will generally be synced when you edit it.

Database Options

• database.class - Set to the class that implements the database driver for your chosen database. For example, if you're using SQLite, this would be 'org.sqlite.JDBC'. For MySQL, it would be 'com.mysql.jdbc.Driver'. For PostgreSQL, 'org.postgresql.Driver'.
• database.url - The JDBC url of your database. For example, for an SQLite database it might be 'jdbc:sqlite:path/to/database', or for a MySQL database you might use 'jdbc:mysql://localhost:666/mydatabase'.
• database.options - Anything else needed for your chosen database goes here; for example, username and password.

An example database configuration for MySQL:

database:
  url: 'jdbc:mysql://localhost/bukkit'
  class: com.mysql.jdbc.Driver
  options:
    user: wombat
    password: kumquat

If you don't want to track ownership, or you're using LWC and don't want sign ownership to be stored in two places, you can use this as your "database info":

database:
  url: 'none'

Permissions nodes

• simplesignedit.edit - Allows players to edit the signs they have placed as well as public signs (owned by everyone). If Permissions is not installed, everyone gets this.
• simplesignedit.edit.all - Allows players to edit any sign, including those with no owner and those placed by others. If Permissions is not installed, only ops get this
• simplesignedit.colour.<code> - Allows players to use the specified colour on signs. Available colours are listed here, but leave out the underscores and use all lowercase. Or you can just give simplesignedit.colour.*; also, the U in colour is optional. Currently this is restricted to ops if Permissions is not installed
• simplesignedit.setowner - Allows players to change the owner of a sign. If Permissions is not installed, only ops get this.