See also: Command Reference and Sign Tutorial Converting to Essentials EconomyĬonverting to Essentials Economy from a currently supported system is fairly easy in most situations. You can create signs in-game (provided you have access) which will allow players to create trade shops, or simply buy or sell items. You can also charge per item repaired with the /repair command. For example you can set different prices for different kits using the above syntax. With these commands it is possible to charge more selectively. Some commands in Essentials support sub costs. For this reason, this option is not compatible with commands from other plugins. This also takes into account teleport delays and cooldowns. Unlike most command cost plugins, the Essentials command costs will only charge the user once the command completes successfully. In this example, Essentials will charge the user '100' any time they use /home command successfully. # Some commands like /repair have sub-costs, check the wiki for more information. # Defines the cost to use the given commands PER USE # Enable the logging of all EssEco API callsĬommand costs are also part of Essentials Eco, but are compatible with other economy plugins as well. ![]() # Enable this to log all interactions with trade/buy/sell signs and sell command # Setting this to 0, will disable overdrafts/loans completely. # Set the minimum amount of money a player can have (must be above the negative of max-money). # The amount is always limited to 10 trillions because of the limitations of a java double # Set the maximum amount of money a player can have # Set this to a currency symbol you want to use. # Defines the balance with which new players begin. These options will generally only effect servers running with Essentials Economy as their economy system. Most the options speak for themselves, and are fairly obvious, at least with the attached comment. There are a number of different options related to the internal economy system. (IE: The Nether, The End, Myscraft Worlds, Dimensional Doors Pocket Dimensions, ect.) Further information on how to do that may be found here.See also: Command Reference Configuration Options If your world has multiple dimensions some config modification may be necessary to transfer permissions to all the appropriate dimensions.Permissions should only show up in one group at a time, if multiple groups are intended to share permissions the inherit feature should be used.Group names cannot have spaces or special characters in them.Every group should have its world specified in your World column.Each other group should inherit is permissions from whatever appropriate group you choose. ![]() No other group may inherit its permissions from none, or have "*" in its Players column.
0 Comments
Leave a Reply. |