ВЕРСИИ (40)

26.1.1 support

- Remove leftover warning message for number rewards

- Add CraftEngine as an item resolver - Add CrackShot as an item resolver - Highly improve `/aurora debug itemid <level>` command - Make every type of reward a number reward (available automatically in every Aurora plugin) - Fix some teleport error when a world is unloaded

- Fix message migrator 1.20.4 compat - Add getLanguageProvider to AuroraAPI

- Fill placeholders in menus even if localization provider is not set - Make slots option higher priority than default slot

## Per player localization support added https://docs.auroramc.gg/aurora/per-player-localization `messages.yml` is now `messages_en.yml` and you can create more using proper language codes like `messages_de.yml` for german. Examples: `en-US`, `en-UK`, `en`, `de`, `sk`, `hu` In this file, you can add a new section, named `custom` (which is already there if you do a fresh install: ```yml custom: stash-title: Item stash prev-page: '&fPrevious Page' npc: quests: <white>Quests ``` These values are available in the plugin menus like item stash. You can reference them as `{{stash-title}}` or `{{npc.quests}}`. Notice the dot (**.**) notation for nested structures. These are also exposed as PlaceholderAPI placeholders: `%aurora_lang_<key>%` for example: `%aurora_lang_npc.quests%` This allows you to add per player localization to any plugin that supports PlaceholderAPI placeholders. ### To enable per player localiaztion: In your config.yml you have to: - add the language codes you support in `supported-languages` - choose your default language and set it to `locale` field - set `use-per-player-locale` to `true` And then you have to: - grant the `aurora.core.user.language` to the players so they have access to the `/language command` After all these, players will be able to use their desired language. Notice that in `config.yml` the `number-format` section also have a `locale` value. That is only used when per player locale is disabled, otherwise it will use the player's selected locale.

- Add item resolver priorities to config - Add item resolver for KGenerators plugin using `kgenerators:generator_id` - Add item interop for every supported item plugin with MythicMobs drops/equipment using `auroralib{item=namespace:item_id}`, example: `auroralib{item=nexo:forest_chestplate}` - Expose data saving/loading latency measurements via debug command: `/aurora debug latency` (should be ran after about half an hour of active player joining/leaving) - Offline players loaded through API aren't cached anymore to prevent potentional synchronization issues

- Mark blocks as player placed that are created using a builder wand from WildTools - Extend the API of RegionExpansion to work with just locations instead of blocks - Removed useless scheduler calls from actionbar/chat handlers - Actionbar utility now pauses AuraSkills idle/xp actionbar just like AuraSkills does when using its ProtocolLib hook

- Add support for ItemEdit in item resolvers with syntax `itemedit:server_item_id` - Add support for EvenMoreFish **2.0** in item resolvers with sytanx: `emf:rarity:fish_id` - Fix very rare race condition with user data loading

**New features** - Add `[meta] meta-key <comparator> value` condition/requirement - Add `===` for placeholder and meta requirements to check equality between actual numbers **Fixes/improvements** - Money reward (used by the other plugins) tries to fail safely if you don't actually have any economy provider - Improve Eco item handler, to make sure it safely fails when you are using EcoArmor in ways you are not supposed to (having disabled armor pieces in your inventory) - Fix `/stash view <player>` on folia

- Hotfix CommandDisptacher Update to this if you are on 2.1.5, otherwise your close menu buttons with [close] action won't work.

Fixes - Ignore non player entites (eg NPCs) in worldguard expansion - Handle kelp the same way as sugar_cane, bamboo, cactus - **Fix auto save not rescheduling itself properly when there are no data to save in one cycle** - Throw on empty command in CommandDispatcher New stuff - Add /aurora debug blockremove to force unregister player placed block - Builders for ItemConfig - Add /stash view <player>

- Skip paper plugin remapping - Change the way permission rewards save the new permission - Apply empty attribute map instead of iron sword default to items when HIDE_ATTRIBUTES flag is used - Fix economy expansion not loading when Vault is not present - Conditional lore option for items - `ItemBuilder#extraLore` api

- Ignore EntityBlockChangeEvent if the entity is not a falling block - Backport Eco item resolver to 1.20.4 - Add tooltip-style for item config 1.21.2+ - Ignore sand fall on folia - Remove Eco from plugin.yml since they can't fix their loading issues

- **New**: Items registered through `/aurora registeritem <id>` now can be used both ways id -> item and **item -> id** - Fixes various issues with Eco plugins in item resolvers - Compile against 1.21.4 - You can now use `item-model` on every menu/reward/etc item (required 1.21.4+)

- Fix various item resolver issues - Add Eco to plugin.yml as a softdepend - Make sure eco don't hijack oraxen/itemsadder/nexo items when they are not actually eco items

- Ignore IA, Oraxen and Nexo in EcoItemsResolver - Fix item resolver AIR with customfishing - Improve menu Requirement APIs

- Add support for Nexo in item resolvers - Remove placed block data 1 tick later to allow checking state in BlockItemDropEvent as well

- Add support for ExecutableBlocks in item resolvers.

Removed incomplete merchants feature that was left in by accident.

# AuroraLib 2.0.0 ## Block tracker With this version the old block tracker implementation will be dropped and the new one will take its place. This will use way less storage and it is way more performant. This change was needed since the old solution haven't really worked well on servers that has a lot of active players building. Now the information will be synced with the chunk on the chunk persistent data container with a very minimal storage overhead ## What does that mean for you? The tracking information for the already placed blocks will be lost. This means that players can increase their collection/quest progression with those blocks. **In reality, this almost doesn't matter and won't cause an issues**. Newly placed blocks will behave as before. For example if you place a sugar cane, then break it, you still won't progress your collections/quests just like before. I'm sorry if this causes some inconvenience for you, but the impact should be minimal and negligible. Thanks for understanding. If you use this build, you need to update AuroraQuests as well to the latest build. ## Other - Some more utils - Some more menu APIs - Fix minor sound issues in CommandDispatcher

- Added `[has-items]` and `[take-items]`, `[give-item]` as valid command dispatcher actions and requirements - Added `append-lore` to item-config for better item merging capabilities - Added bStats - Build against 1.21.3

This release adds many new features/APIs, improvements, and bug fixes. ### New features - Rework economy interface to support multiple currencies - Added new economy providers - Current list of supported economy providers: Vault, Essentials, CMI, PlayerPoints, CoinsEngine, EcoBits, EliteMobs, RoyaleEconomy, RoyaleEconomyBank - Both CommandDisptacher, MoneyReward and [money] menu requirement supports these new economies and currencies ### Improvements - Cache player profiles when creating skull items - HeadDatabase support for Item resolvers - Stash commands and APIs now handle larger amounts than the maximum stack size of the item. ### Bug fixes - Fix legacy color code replacer `&n -> <underlined>` - Fix custom GUIs title placeholder not including args - Fix AuroraMenu free slots API (for 3rd party plugins wanting to implement something like a backpack) - Don't build the actual item if the material is air in ItemBuilder

This release adds many new features/APIs, improvements, and bug fixes. ### New features - Fully customizable **GUI framework**. Create as many custom menus as you wish with the full power of AuroraLib item resolvers, command dispatcher, and requirement manager. All of these also have an extendable API for developers - ItemsAdder item support (meaning every aurora plugin can now use `ia:namespace:item_id`) - Command dispatcher now supports `[take-money]`, `[give-money]`, `[sound]`, `[open-gui]`, `[actionbar]` - **Item stash menu and commands**! Now every Aurora plugin can use this stash to put item rewards into it for example. It also has a straightforward API for other plugin developers to hook into. - You can now register items that you are currently holding and use them in menus/item rewards like `aurora:item_id` ### Improvements - Cache skin URLs extracted from base64 strings - Reworked the command system, so now you have better tab completions and fully translatable messages for everything - More permissions to allow greater control over who can do what ### Bug fixes - Now if you mess up your YAML syntax in config, your files won't be changed/erased by config migration steps - Fixed click handling of menus

- Add support for ExecutableItems

- Fix NPE on plugin disable if block tracker is disabled. - Add `hide-tooltip` option to ItemConfig. - Fix some issues with generic collections in ConfigManager, but this shouldn't really matter for regular users

- Fix leaderboard placeholders not working with null player

- Fix block tracker to properly call RegionBlockBreakEvent every time - Fix block tracker error when mining amethyst and other blocks that require support not to break

- Now player join won't trigger a leaderboard save for no reason. Doesn't matter too much, but it is a slight improvement.

- Fix TypeId for entities - in your collection configs you should now write: `minecraft:entity` instead of `minecraft:ENTITY`

- A ton of optimizations regarding database management both for user/leaderboard data saving. - New command `/aurora dbmigrate`. This will migrate your current data to the other storage provider. For example if you are using yaml right now, it will migrate to MySQL if the credentials are set up correctly in the config. It works in the other direction as well. - Data migration is only supported for user data. Leaderboards will rebuild themselves once the players are joining again after the migration. - If you migrate from one storage to another, everyone will be kicked and nobody can join the server until the migration is finished. Migration uses 5 threads to work in parallel. **After it finished it is strongly advised to check your config again and restart the server**, though you don't have to. - Migration will only migrate data for registered DataHolders, meaning if AuroraLevels is not installed for some reason, but it was before, then levels data won't be migrated.

- **Hotfix Sqlite leaderboard storage** - add support for Eco plugin item resolvers, eg.: `eco:ecoitems:grappling_hook` - new entity resolver APIs - **EXPERIMENTAL** (EcoMobs and MythicMobs are supported) - ItemConfig now supports `slots` key as a number list, so you can add them to multiple inventory slots in menus. This should help creating 3D animated menus

- Fix TypeId parsing to support more complex types. This fixes MMOItems item resolvers.

Properly register leaderboard update prevent permissions into Bukkit. This will autocomplete every permission in LuckPerms commands. This is how permissions works both for OP and non OP players: - **unset**: you will be on the leaderboard and you stats will update on the boards - `aurora.leaderboard.prevent.*` is true: your stats won't update in the leaderboards for every board - `aurora.leaderboard.prevent.board_name` is true: your stats won't update in the leaderboards for the specific board

Update CustomFishing item resolver to 2.2.0 API. Make sure to update CustomFishing in your server if you are using their items in your menus or anywhere else!

- Added leaderboard expansions and APIs

- Fix permission reward loading when permission field is a list

- full folia support - fix money reward default economy detection - added RewardExecutor and ThreadSafetyLevels to rewards - command and permission reward now can execute multiple commands/permissions - level matcher configs now have an optional Item field to easily override default menu items - ItemConfig#merge to merge ItemConfigs easily - item rewards

Initial first release on Modrinth.