TMDevelopmentTinulica & Maiky

FlareTokensv4.1.1

The coin of your server; in-game store with drag & drop editor, cheques.

10,2K download3.9 (28)aggiornato 14 giorni fa
4.1.1

Added

  • Discord messages: a message in a Discord channel through a webhook when a timed sale or a booster for everyone starts, and when a player buys something for at least discord.purchase-min tokens. Set discord.enabled: true and discord.webhook-url in config.yml; each message can be turned off, texts are in lang/en.yml → discord. Mentions in product names are blocked and the address is never written in the console.
  • Booster boss bar (1.9+): while a booster is active players see it with the time left ("2x TOKENS · 45m"), for everyone or only for themselves. booster.bossbar in config.yml (on by default, color and style), texts booster.bossbar-global / bossbar-personal.
  • Daily button in /tokens menu (new installs): shows the days in a row and if the reward is ready, click to claim. It is shown only when daily rewards are on. On existing servers copy the daily element from the default menus/tokens.yml (see the wiki).
  • New check [enabled] <option> for show-if / hide-if and actions: daily, playtime, exchange, booster, paytoggle, drops.
  • Menu texts: {daily_streak}, {daily_status}, {daily_time}, {booster}, {booster_time} (no PlaceholderAPI needed).
4.1.0

Four new features. All of them are off by default (boosters work only when you start one), so nothing changes until you turn them on. The new options are added to config.yml and lang/en.yml on the first start.

Added

  • Daily reward (/tokens daily): tokens once per day, more for every day in a row (daily.rewards, day 1, day 2 ...). Missing a day starts again from day 1; repeat-last decides what happens after the last day. Players get a clickable reminder on join when it is ready. A new day starts at midnight of daily.timezone (empty = the server one). Saved with the balances, so with MySQL it is the same on every server. Turn it on with daily.enabled: true.
  • Tokens for time played: every playtime.every-minutes minutes online a player gets playtime.amount tokens, more with flaretokens.playtime.<rank> (playtime.ranks). Players who do not move or look around for afk-minutes are AFK and their timer stops. Message in the action bar, in chat or none. Turn it on with playtime.enabled: true.
  • Exchange (/tokens exchange buy|sell <amount>): money (Vault) to tokens and tokens to money, with the prices in exchange.buy-price / exchange.sell-price (0 = that way is off; selling must pay less than buying). If the economy plugin refuses the money, the tokens are given back. Turn it on with exchange.enabled: true.
  • Token boosters: /tokens booster <multiplier> <time> starts a booster for everyone (on every server with MySQL), /tokens booster 2 1h <player> gives one to a player, /tokens booster stop [player] ends it. Shops can sell them with the new action [booster] 2 1h. They multiply drops, daily rewards and playtime rewards (booster.applies-to); the highest active booster counts, and a weaker global booster does not replace a stronger one. /tokens booster shows the active ones to everyone.
  • Placeholders: %flaretokens_booster%, %flaretokens_booster_time%, %flaretokens_booster_global%, %flaretokens_booster_global_time%, %flaretokens_daily_streak%, %flaretokens_daily_ready%, %flaretokens_daily_time%, %flaretokens_playtime_next%.
  • Permissions: flaretokens.command.daily and flaretokens.command.exchange (everyone), flaretokens.command.booster (op), flaretokens.playtime.<rank>.
4.0.5

Added

  • Tax on payments: pay.tax-percent in config.yml (default 0 = off). The sender pays the full amount, the receiver gets it minus the tax, and the sender sees how much was taken. Decimals work (2.5). Players with flaretokens.bypass.tax pay no tax.
  • /tokens paytoggle (also /tokens togglepay): players can refuse incoming payments. Off by default, the server turns it on with pay.allow-toggle: true. Saved with the balances, so with MySQL it is the same on every server. Permission flaretokens.command.paytoggle (everyone).

The new options are added to your config.yml and lang/en.yml on the first start, the rest of the files is not touched.

4.0.4

Fixed

  • Closing /tokens editor with a menu item still on the cursor removed that item from the menu. It now goes back to the slot it was taken from (or the first free one) and is saved.
  • On 1.8 - 1.13 the editor showed admins an internal line in the lore of every item (⚙ ft:i:...). It is now invisible.
  • After removing an open-commands entry and /tokens reload, online players kept seeing the old command in the tab completion until they joined again (1.13+): the command list is now sent again to everyone online.
4.0.3

Fixed

  • Ranks in the top were empty for offline players: the LuckPerms expansion of PlaceholderAPI gives nothing for them. %luckperms_prefix%, %luckperms_suffix% and %luckperms_primary_group_name% now come straight from LuckPerms for offline players (also without PlaceholderAPI). Nothing to change in your files.
  • After updating from 4.0.0 / 4.0.1, /tokens help still showed /tokens version. The old line is now replaced with the /tokens about one, only if you never edited it.
  • Permission multipliers of drops.yml were given to every OP: flaretokens.multiplier.vip / mvp are not plugin.yml permissions, and Bukkit gives undeclared permissions to OPs. Now a multiplier counts only when the permission is really given (permissions plugin, * included).
  • Saving from /tokens editor wrote the whole shop file again: quotes, lists and long lines changed, and on 1.8 - 1.17 the comments inside the file were lost. Now only what changed is written, in the same style as the rest of the file, everything else stays as you wrote it.
  • /tokens settings removed a comment at the end of the line of the option it changed: now it stays.
  • /tokens remove said "Removed 1,000" when the player had less: it now shows what was really removed.
  • /tokens shop <shop> <player> from the console with a wrong shop sent the error to the player instead of the console.
  • After removing an open-commands entry and /tokens reload, the old command kept answering "There is no shop called ..." until a restart (Paper): now it answers like an unknown command.
4.0.2

New

  • Ranks in the top: PlaceholderAPI placeholders in the top menu (menus/top.yml) and in /tokens top chat are now of the player of each line, not of the one looking at it. For a rank before the name: "&#b57bff#{position} %luckperms_prefix%&f". With LuckPerms the rank shows also for offline players.
  • /tokens about (also /tokens version): plugin version in green when it is the latest or in red "OUTDATED! Please update!" with the download link, server version and type, Java and storage, update notifier on/off, plugin hooks (PlaceholderAPI, LuckPerms, Vault, ItemsAdder, ExecutableItems) and a clickable list of every permission with what it does. The new texts are added to lang/en.yml by themselves.

Fixed

  • A sale started on one server of the network was announced on the others with the time left when they got it ("1m 29s" or "57s" instead of "1m 30s" / "1m"). Now every server announces the same time.
4.0.1

Fixed

  • The Confirm button of the confirm menu also bought with Q, Ctrl+Q, the number keys and F. Now every menu (shops, plugin menus, settings) reacts only to left, right and shift clicks. Shop items that ask for another click on purpose ([DROP], [MIDDLE]...) still get it.
  • Items given by a product didn't stack with the same items got in another way.
  • On 1.8 the titles with a gradient were cut after a few letters.
  • Editor: the first value written in chat in the product settings (price, limit, stock, permission...) was not saved, and the first click on confirm / sale / admins only could be lost.
  • Updates added the new options to config.yml, lang/en.yml and menus/admin.yml by saving the whole file again: on 1.8 - 1.17 every comment was lost, on newer versions the quotes changed. New options are now added with their comment, in their section, and the rest of the file is not touched.

Improved

  • When another server of the network gives or takes tokens, the player gets the "You received ..." message (network.notify-changes: true, added to your config by itself).
  • A sale started or stopped on one server reaches the others within a few seconds (was about 30).
  • The time left of a sale reads the same on every server: "1m", "1m 30s", "2h", "1h 30m" (before, another server could announce a 2m sale as "1m", and a 1m sale showed "60s").
  • Open menus update by themselves when the balance changes (price lines, "you need X more"), and every few seconds when show-if / hide-if / permissions now show another item.
  • Offline-mode servers without BungeeCord / Velocity no longer look up the skins of player heads: no more warnings in the console. Online players still show their skin when the server knows it (for example with SkinsRestorer).
  • Items sold with the editor are given exactly as they were in your hand.
  • Changing the main shop from /tokens settings now confirms it in chat.
  • Example files: the history icon for "set" and the golden apples name use the plugin colors.
4.0.0

FlareTokens is back: rebuilt from scratch, faster, and now the coin of your whole server or network, with an in-game store you build with drag and drop. Updating from 3.x is automatic: just replace the jar, your balances, shops and cheques keep working.

Compatibility

  • One jar for Spigot, Paper, Purpur and forks from 1.8.8 to 26.x, Java 8 or newer. Newer features (boss bars, hex colors, title timings) are used only where the server supports them.

Updating from 3.x

  • Your old files are saved in backup-3.x/, the settings move to the new config.yml and your shops move to shops/ (same format, they work as they are).
  • Balances are not touched: same SQLite file, MySQL table and YAML file.
  • Cheques made with 3.x can still be redeemed. The 3.x placeholders and permissions keep working.
  • Messages are now in lang/en.yml: if you edited the old locale/en.yml, copy your texts from the backup.

New

  • In-game store: as many menus as you want in shops/ (a hub with categories, ranks, kits, keys...), linked with [open] <menu> and [back]. New example files: main.yml (hub), ranks.yml, items.yml.
  • Products: price, give (items), commands, confirm (confirm menu), limit per player (once, per day, week or month), stock for the whole server, permission, show-if / hide-if. The price, "you need X more tokens", "sold out" lines are added by themselves (texts in each shop file).
  • Drag and drop editor: /tokens editor. Move items, add glass panes and buttons, link menus, create new menus and sell the item in your hand with exactly its enchantments and name. Price, limit, stock, permission and commands from a menu, no YAML needed. Same editor as the other Flare plugins.
  • /tokens settings: every option in one menu, plus player access (what normal players can use).
  • /tokens menu (balance, shop, top, history), a top menu and a history menu with pages. Their layouts are in menus/ and can be edited like the shops.
  • History: every change of balance is saved (who, how much, why, on which server, when): /tokens history [player]. Kept 90 days by default (history.keep-days).
  • Timed sales: /tokens sale 20 2h [shop] lowers the prices by 20% for 2 hours, with an announcement; %flaretokens_sale% and %flaretokens_sale_time% for scoreboards.
  • Network coin: with MySQL, balances changed on another server show up within about a second, and history, limits, stock and sales are shared by every server. tokens give <uuid> <amount> for web stores.
  • Menu files use the same format as the other Flare plugins: title, rows, open-commands, open-permission, slots: "0-8,45-53", material: head:{player} / texture:<value>, admin-only, and decorations drawn under the items (a border can't cover a button any more).
  • Hex colors, gradients, rainbow, click and hover in every message (MiniMessage tags and & codes). The 3.x <GRADIENT:#a-#b> syntax still works.
  • Clear files with short explanations: config.yml, lang/en.yml, shops/, menus/, drops.yml. New options and messages are added to your files by themselves in future updates.
  • /tokens top, /tokens migrate <yaml|sqlite|mysql>, /tokens withdraw all, amounts like 2.5k.
  • /tokens version: plugin, server and Java version, and whether a new FlareTokens is out. Admins also get a clickable message when they join (turn it off with update-check: false).
  • New aliases: /token, /ftokens, /ftoken (the 3.x ones keep working).
  • Sneak + right click redeems a whole stack of cheques.
  • Mob drops (drops.yml): tokens for kills with chance, random amounts, permission multipliers, spawner and world filters (off by default).
  • 3.x shop options still work, plus priority, view_requirements, separate [LEFT] / [RIGHT] actions, live items (update: true), {missing:<price>} placeholder and a click cooldown against double purchases.
  • New actions: [open], [back], [BROADCAST], [REFRESH], [DELAY], short [TITLE], [SOUND], [EFFECT] and [BOSSBAR] forms.
  • New checks: [has_tokens] 100, [has_money] 100, [has_permission] node, [expression] a >= b (the 3.x check(...) forms still work).
  • PlaceholderAPI: %flaretokens_tokens%, _tokens_formatted, _tokens_commas, top_<n>_name, top_<n>_tokens, position, sale, sale_time. They also work for offline players (holograms, leaderboards).
  • Developer API: FlareTokensAPI and the cancellable TokensChangeEvent.
  • Every balance change is written in logs/transactions.log.
  • Missing PlaceholderAPI is downloaded and started automatically.

Improved

  • Balances of online players are kept in memory and saved in the background: the server never waits for the database.
  • Placeholders of offline players no longer freeze the server: the balance is read in the background.
  • Several se

Accedi

Nuovo? Scrivi solo la tua email: l'account nasce quando clicchi il link. Nessuna password.

oppure

Ti mandiamo un link che ti fa entrare con un clic. Vale per account nuovi ed esistenti.

Entra con la password

Continuando accetti i Termini e condizioni e la Privacy policy.

Staff: apri “Entra con la password” e scrivi il tuo nome utente al posto dell’email. Dopo la password ti chiediamo il codice 2FA.