ShadowCrazyChest

The version of this file.

Leave it as it is: the plugin sets it. On update your files (this one, prices.yml, chesttypes.yml, crates.yml and lang/) are moved to the new version automatically: every value you changed or added stays, the new options arrive with their comments, and what you deleted stays deleted. The old copies are in backup/<date>/, and if something needs your attention you will find PORTING-<version>.txt in the plugin folder.

The fallback prefix, used only when a language file has none of its own. The real one is the "prefix" key inside lang/<language>.yml.

The language of the server. A lang/<default>.yml file must exist. Two of them ship with the plugin: en and it. Set "it" here for an Italian server.

true  -> every player sees the messages in the language of their
         client, if a file for that language exists.
false -> everybody sees the language above.

Either way an explicit choice by a player (/scc lang) always wins, and is remembered in the database.

The table prefix. Change it and the plugin creates new tables and starts from scratch: handy for two servers on the same database.

MySQL configured but out of reach: with true the plugin says so in the console and falls back to the local file, so the server still starts.

How often modified chests are written to the database. They are also written on shutdown and with /scc save, so this only decides how much a sudden crash could cost you.

Records every sale in the history table (the "earned today" statistics need it). On a server with hundreds of SellChests the table grows fast: the cleanup below keeps it under control.

Imports the data of the old YAML version once (the instances/ and enderchests/ folders). The files are not deleted, only renamed.

Lets more than one process open the same H2 file. Only needed if you want to inspect the database with an external tool while the server is running.

false switches off everything to do with money: the chests keep collecting and piling up, but they do not pay and do not charge.

AUTO   -> ShadowEconomy if present, else Vault, else nothing
SHADOW -> ShadowEconomy only
VAULT  -> Vault only
NONE   -> no economy

The named currencies the server uses, besides the default one. They are here so the editor can offer them and so you can write them as "currency:<id>" in crate rewards or in sell.payout of a chest type. The one that really creates them is ShadowEconomy: this only lists the names. Example: [tokens, gems]

Where the sale price of an item comes from.

AUTO   -> first the prices of the single chest type, then the server
          shop through ShadowEconomy, then prices.yml. This is the right
          choice nearly always: the server prices stay a single set, and
          you do not have to keep two lists in step.
SHADOW -> the prices of the ShadowEconomy shop only
LOCAL  -> chesttypes.yml and prices.yml only, ignoring the shop

Total chests a player may place, adding up every type. -1 = no global limit (only the per-type ones count). It can be raised per rank with shadowcrazychest.limit.total.<number>.

Worlds where chests cannot be placed.

true = a chest is only placed where the player may build according to ShadowRegions / WorldGuard / ShadowSkyBlock.

true = a SellChest only collects what the owner and their island mates break. With false it collects everything that happens within its radius, whoever does it: on a server with islands or claims that is the quickest way to have the neighbour steal your work.

true = a SellChest never sells nor destroys an item from Oraxen, ItemsAdder or the like, unless that exact id has a price written in prices.yml. Without this, void mode would make somebody's custom sword disappear after it ended up in there by mistake.

Who draws them.

AUTO                 -> ShadowEssentials, then DecentHolograms, then
                        HolographicDisplays, then the internal one
SHADOW_ESSENTIALS    -> forces the hologram module of the suite
DECENT_HOLOGRAMS     -> forces DecentHolograms
HOLOGRAPHIC_DISPLAYS -> forces HolographicDisplays
INTERNAL             -> always the internal one (TextDisplay, no
                        dependencies at all)

How often the numbers refresh (earnings, fill level, timers).

Height above the block.

View distance, as a multiplier. Applies to the internal one.

The BASE address of the activation service: the plugin appends /claim and /check itself. It is what makes it possible to write

/scc license claim <purchase-code>

How many days of grace before falling back to free when something does not add up: a subscription that just expired (the renewal has nearly always gone through already) or an address that does not match (far more often a NAT or a proxy than a thief).

Asks the licence service (activation-url + /ip) what public address this server has: it answers with the address it sees, and nothing about the server is sent. Needed behind NAT, where the server sees none of its own public addresses and a licence tied to the domain would not be recognised. Switch it off and the plugin only uses the addresses it sees from the inside. Only when a licence is installed: a server without a key asks nobody. false = never ask.

Prints every query in the console. Useful to work out a problem, very noisy in production.

false = booster items do nothing, the booster button leaves every panel and /scc booster and /scc givebooster refuse. Nothing else changes. A single type can also opt out with "boosters: false" in chesttypes.yml.

Every crate key is made of this item, whatever crates.yml says for that crate (its name, lore and model stay its own): one look, one meaning. Empty = each crate uses the material written in crates.yml.

Close the opening screen by itself once the reward has been handed out.

How long the particle trail that shows where every column sends its items stays visible, in seconds.

Permission needed to place it. Empty = everybody.

The storage: 6 rows of 9 slots, a single page.

custom-item: 'oraxen:sell_chest' item-model: 'myserver:sellchest'

How often it empties and sells what is inside. Twenty seconds is the right compromise: you watch the money come in while mining, and it is not frequent enough to scroll the chat with notifications.

Destroys what nobody buys instead of leaving it inside. Off on purpose: it is a deletion all the same, and on this chest the player expects to be able to get back what they mined. Each owner can still switch it on for a single chest from its panel.

The collector: drops within the radius go into the chest instead of falling on the ground.

Also what is already on the ground: the stuff dropped by hand, what pops out of a furnace, what another plugin makes appear. Whoever throws it is still checked like whoever mines, so the chest takes what YOU throw and not what somebody else tosses over to a friend.

0 = the chest chunk only. Every unit adds one ring of chunks around it (4 at most).

true = the drop turns into money without ever entering the storage.

Keeps selling while the owner is offline, but at 75%. Whoever plays earns more than whoever leaves the server running, which is exactly the incentive you want.

Tells the owner in the action bar on every automatic sale.

What this chest pays in:

money            the default currency
currency:gems    a named ShadowEconomy currency
xp / xp-levels   experience (only while the owner is online)
tokens           the token plugin of the server

How many items it handles at most in one cycle. 0 = no cap. This is the valve that keeps the server standing under an industrial farm: what is left over is not lost, it stays inside and goes to the next cycle.

How much this chest may earn in a day. 0 = no cap. Off out of the box because it is a balance choice of the single server. Once the cap is reached the chest STOPS SELLING instead of selling without paying: the goods stay inside and tomorrow they really are sold. The tally survives a restart.

Five levels: it sells more and it sells more often. At maximum a SellChest is worth double and works at double the speed, which makes it a real goal without breaking the economy.

The 3D model spins on itself. Only matters with display.enabled.

Prices by custom item id, again for this type only. The ids go in quotes because they contain a colon.

'oraxen:ruby': 300.0

The starting filters of every new chest of this type. Each chest then has its own, editable from the panel: two SellChests of the same player nearly always serve two different farms.

item-model: 'myserver:unitchest'

No levels: there is nothing to grow. The capacity is already unlimited and this chest does not sell.

What a hopper must not be able to push into it. An item with enchantments or a name does not go in anyway: in a counter it would lose everything that makes it different.

item-model: 'myserver:megachest'

One page open at the start, one more per level: five levels for six pages.

item-model: 'myserver:bigenderchest'

One page open at the start, one more per level: two levels for three pages.

The pass-through storage: one row only, because what comes in must leave again, not pile up.

item-model: 'myserver:shadowhopper'

How often it sucks up and ships. One second is the rhythm of a hopper: slower would show, faster would be pointless.

By default it does not sell: it is a hopper, not a chest. Turning it on, what it collects becomes money instead of leaving.

This is the suction, and it is the reason it exists.

0 = one block around. Every ring adds sixteen blocks of radius, and that is what the levels raise.

The hopper's own pull, in BLOCKS: this at level 0, +bonus-radius per level, never above max-collect-radius. And how high above itself it looks.

Four levels: it ships more and sucks up from further away. bonus-radius in blocks, bonus-filters in columns: 3 -> 7 blocks and 7 -> 35 columns over four levels.

Empty = everything passes. Writing materials in it, the hopper sucks up ONLY those: that is how you put a hopper under a mixed farm and take away one thing only.

What it must never touch.

Where the opening happens:

MENU   the classic one: a window opens and the strip scrolls inside it.
       Precise, readable, fine with twenty people standing around.
WORLD  the Hypixel way: nothing opens, the lid lifts and the prize
       appears in mid-air above the block among the particles. Everyone
       else sees it too, which is exactly why it exists.

Where the opening happens:

MENU   the classic one: a window opens and the strip scrolls inside it.
       Precise, readable, fine with twenty people standing around.
WORLD  the Hypixel way: nothing opens, the lid lifts and the prize
       appears in mid-air above the block among the particles. Everyone
       else sees it too, which is exactly why it exists.

Where the opening happens:

MENU   the classic one: a window opens and the strip scrolls inside it.
       Precise, readable, fine with twenty people standing around.
WORLD  the Hypixel way: nothing opens, the lid lifts and the prize
       appears in mid-air above the block among the particles. Everyone
       else sees it too, which is exactly why it exists.

Where the opening happens:

MENU   the classic one: a window opens and the strip scrolls inside it.
       Precise, readable, fine with twenty people standing around.
WORLD  the Hypixel way: nothing opens, the lid lifts and the prize
       appears in mid-air above the block among the particles. Everyone
       else sees it too, which is exactly why it exists.

How far above the block the spinning item appears, and how big it is.

Where the opening happens:

MENU   the classic one: a window opens and the strip scrolls inside it.
       Precise, readable, fine with twenty people standing around.
WORLD  the Hypixel way: nothing opens, the lid lifts and the prize
       appears in mid-air above the block among the particles. Everyone
       else sees it too, which is exactly why it exists.

How far above the block the spinning item appears, and how big it is.