Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't create short item name for mud #521

Open
4 tasks done
FITFC opened this issue Jun 22, 2022 · 6 comments
Open
4 tasks done

Can't create short item name for mud #521

FITFC opened this issue Jun 22, 2022 · 6 comments

Comments

@FITFC
Copy link

FITFC commented Jun 22, 2022

What is happening?

Can't create itemaliases for "minecraft:mud"

What did you expect to happen?

He can use ItemAliases for minecraft:mud, only this one has a problem :P

Plugin Version

3.12.1

Plugin Config

config
# Should the plugin log some messages that are useful for debugging?
DEBUG: false

# Do you want to turn off the automatic updates of ChestShop?
TURN_OFF_UPDATES: true
# Do you want to turn off the automatic notifications for new development builds?
TURN_OFF_DEV_UPDATE_NOTIFIER: true
# Do you want to include some values of this config in the metrics? (This will not leak sensitive data but help in the development process)
INCLUDE_SETTINGS_IN_METRICS: false

# How large should the internal caches be?
CACHE_SIZE: 1000

# The default language when the client's language can't be found.
DEFAULT_LANGUAGE: "en"
# Should the plugin try to use a language file that matches the client's locale setting?
USE_CLIENT_LOCALE: true

# What containers are allowed to hold a shop? (Only blocks with inventories work!)
SHOP_CONTAINERS: 
- "CHEST"
- "BARREL"
- "TRAPPED_CHEST"
- "SHULKER_BOX"
- "WHITE_SHULKER_BOX"
- "ORANGE_SHULKER_BOX"
- "MAGENTA_SHULKER_BOX"
- "LIGHT_BLUE_SHULKER_BOX"
- "YELLOW_SHULKER_BOX"
- "LIME_SHULKER_BOX"
- "PINK_SHULKER_BOX"
- "GRAY_SHULKER_BOX"
- "LIGHT_GRAY_SHULKER_BOX"
- "CYAN_SHULKER_BOX"
- "PURPLE_SHULKER_BOX"
- "BLUE_SHULKER_BOX"
- "BROWN_SHULKER_BOX"
- "GREEN_SHULKER_BOX"
- "RED_SHULKER_BOX"
- "BLACK_SHULKER_BOX"

# (In 1/1000th of a second) How often can a player use the shop sign?
SHOP_INTERACTION_INTERVAL: 350
# Do you want to allow using shops to people in creative mode?
IGNORE_CREATIVE_MODE: true
# Do you want to allow using shops to people who have access to it due to their permissions? (owners are always ignored)
IGNORE_ACCESS_PERMS: true
# If true, people will buy with left-click and sell with right-click.
REVERSE_BUTTONS: false
# If true, people will be able to buy/sell in 64 stacks while holding the crouch button.
SHIFT_SELLS_IN_STACKS: true
# If true, people will be able to sell/buy everything available of the same type.
SHIFT_SELLS_EVERYTHING: false
# What can you do by clicking shift with SHIFT_SELLS_IN_STACKS turned on? (ALL/BUY/SELL)
SHIFT_ALLOWS: "ALL"
# Can shop's chest be opened by owner with right-clicking a shop's sign?
ALLOW_SIGN_CHEST_OPEN: true
# If true, when you left-click your own shop sign you won't open chest's inventory, but instead you will start destroying the sign.
ALLOW_LEFT_CLICK_DESTROYING: true

# If true, if the shop is empty, the sign is destroyed and put into the chest, so the shop isn't usable anymore.
REMOVE_EMPTY_SHOPS: false
# If true, if the REMOVE_EMPTY_SHOPS option is turned on, the chest is also destroyed.
REMOVE_EMPTY_CHESTS: false
# A list of worlds in which to remove empty shops with the previous config. Case sensitive. An empty list means all worlds.
REMOVE_EMPTY_WORLDS: 
- "world1"
- "world2"

# First line of your Admin Shop's sign should look like this:
ADMIN_SHOP_NAME: "Exchange ÐC"
# The name of the economy account which Admin Shops should use and to which all taxes will go
SERVER_ECONOMY_ACCOUNT: ""
# The uuid of the economy account for the Admin Shop. Useful for fake accounts as normally only accounts of players work
SERVER_ECONOMY_ACCOUNT_UUID: c5ae76bc-1809-3783-b987-426b9b3ec062
# Percent of the price that should go to the server's account. (100 = 100 percent)
TAX_AMOUNT: 1
# Percent of the price that should go to the server's account when buying from an Admin Shop.
SERVER_TAX_AMOUNT: 0
# Amount of money player must pay to create a shop
SHOP_CREATION_PRICE: 0
# How much money do you get back when destroying a sign?
SHOP_REFUND_PRICE: 0
# How many decimal places are allowed at a maximum for prices?
PRICE_PRECISION: 2

# Should we block shops that sell things for more than they buy? (This prevents newbies from creating shops that would be exploited)
BLOCK_SHOPS_WITH_SELL_PRICE_HIGHER_THAN_BUY_PRICE: true

# Maximum amount of items that can be bought/sold at a shop. Default 3456 is a double chest of 64 stacks.
MAX_SHOP_AMOUNT: 3456

# Do you want to allow other players to build a shop on a block where there's one already?
ALLOW_MULTIPLE_SHOPS_AT_ONE_BLOCK: false
# Can shops be used even when the buyer/seller doesn't have enough items, space or money? (The price will be scaled adequately to the item amount)
ALLOW_PARTIAL_TRANSACTIONS: true
# Can '?' be put in place of item name in order for the sign to be auto-filled?
ALLOW_AUTO_ITEM_FILL: true

# Enable this if you use BungeeCord and want players to receive shop notifications on other servers
BUNGEECORD_MESSAGES: false

# Do you want to show "Out of stock" messages?
SHOW_MESSAGE_OUT_OF_STOCK: true
# Do you want to show "Full shop" messages?
SHOW_MESSAGE_FULL_SHOP: true
# How many seconds do you want to wait before showing notifications for the same shop to the owner again?
NOTIFICATION_MESSAGE_COOLDOWN: 15

# Can players hide the "Out of stock" messages with /cstoggle?
CSTOGGLE_TOGGLES_OUT_OF_STOCK: false
# Can players hide the "Full shop" messages with /cstoggle?
CSTOGGLE_TOGGLES_FULL_SHOP: false
# Do you want to show "You bought/sold... " messages?
SHOW_TRANSACTION_INFORMATION_CLIENT: true
# Do you want to show "Somebody bought/sold... " messages?
SHOW_TRANSACTION_INFORMATION_OWNER: true

# If true, plugin will log transactions in its own file
LOG_TO_FILE: true
# Do you want ChestShop's messages to show up in console?
LOG_TO_CONSOLE: true
# Should all shop removals be logged to the console?
LOG_ALL_SHOP_REMOVALS: true

# Do you want to stack all items up to 64 item stacks?
STACK_TO_64: false
# Do you want to use built-in protection against chest destruction?
USE_BUILT_IN_PROTECTION: false
# Do you want to have shop signs "stick" to chests?
STICK_SIGNS_TO_CHESTS: false
# EXPERIMENTAL: Do you want to turn off the default protection when another plugin is protecting the block? (Will leave the chest visually open - CraftBukkit bug!)
TURN_OFF_DEFAULT_PROTECTION_WHEN_PROTECTED_EXTERNALLY: true
# Do you want to turn off the default sign protection? Warning! Other players will be able to destroy other people's shops!
TURN_OFF_SIGN_PROTECTION: true
# Do you want to disable the hopper protection, which prevents Hopper-Minecarts from taking items out of shops?
TURN_OFF_HOPPER_PROTECTION: false
# Only allow users to buy/sell that have access to the sign's protection? (E.g. LWC protection)
CHECK_ACCESS_FOR_SHOP_USE: false
# Do you want to protect shop chests with LWC?
PROTECT_CHEST_WITH_LWC: false
# Of which type should the container protection be? Possible type: public, private, donate and on some LWC versions display
LWC_CHEST_PROTECTION_TYPE: "PRIVATE"
# Do you want to protect shop signs with LWC?
PROTECT_SIGN_WITH_LWC: false
# Of which type should the sign protection be? Possible type: public, private, donate and on some LWC versions display
LWC_SIGN_PROTECTION_TYPE: "PRIVATE"
# Should the chest's LWC protection be removed once the shop sign is destroyed? 
REMOVE_LWC_PROTECTION_AUTOMATICALLY: true
# Should LWC limits block shop creations?
LWC_LIMITS_BLOCK_CREATION: true

# Do you want to only let people build inside WorldGuard regions?
WORLDGUARD_INTEGRATION: false
# Do you want to only let people build inside region flagged by doing /region regionName flag allow-shop allow?
WORLDGUARD_USE_FLAG: false
# Do you want ChestShop to respect WorldGuard's chest protection?
WORLDGUARD_USE_PROTECTION: false

# Do you want to only let people build inside GriefPrevention claims?
GRIEFPREVENTION_INTEGRATION: true

# Do you want to only let people build inside RedProtect regions?
REDPROTECT_INTEGRATION: false

# Do you want to deny shop access to unlogged users?
AUTHME_HOOK: false
# Do you want to allow shop access to unregistered users? (Example: registration is optional)
AUTHME_ALLOW_UNREGISTERED: true

# How much Heroes exp should people get for creating a ChestShop?
HEROES_EXP: 100.0

# Add icons and make item names hoverable in transaction messages when ShowItem is installed?
SHOWITEM_MESSAGE: true

# Make all admin shops be unlimited even if they have a shop container at the sign
FORCE_UNLIMITED_ADMIN_SHOP: true
# This makes sure that the UUIDs of player shop accounts match the server's online-mode setting. Disabling this might lead to issues with offline players and is therefore unsupported!
ENSURE_CORRECT_PLAYERID: false
# This regexp validates the name of the player. If the name doesn't match, the player will neither be able to create a valid shop sign, nor buy/sell from a shop.
# Note for Bedrock support: If you have Floodgate on your server, you should set this regexp to ^\\*?\\w+$ and ENSURE_CORRECT_PLAYERID to false
# If your Floodgate prefix is not *, change the first * in the regexp (the one before the question mark) to whatever your prefix is.
VALID_PLAYERNAME_REGEXP: "^\\*?\\w+$"

# Add stock counter to quantity line?
USE_STOCK_COUNTER: false

# If true and in 1.14+, the owner of a chest shop can click with a dye / ink sac to dye the sign.
SIGN_DYING: true

Server Version

Current: git-Purpur-1669 (MC: 1.19)* Previous: git-Purpur-1663 (MC: 1.19)

Server Log

https://mclo.gs/XOHX5U0

What other plugins are you running?

[01:13:40 INFO]: [PlugMan] Plugins (53): AppleCoreSpigot, BetterConcrete, Brewery, Celeste, CharacterCards, ChatBot, ChatManager, ChestShop, ChestShopNotifier, Cigarette, DeathMessages, DecentHolograms, EditableStands, Elevator, Essentials, FastAsyncWorldEdit, GDHooks, Geyser-Spigot, GriefDefender, GSit, IllegalStack, JoinCommands, LuckPerms, mcMMO, MiniMOTD, Mobcash, MyCommand, nLogin, NoChatLagServer, NoChunkLag, Orebfuscator, PaperMoney, PingKick, Pl-Hide-Pro, PlaceholderAPI, PlugManX, ProtocolLib, RandomSpawn, RealEstate, RealisticSeasons, RealScoreboard, RHLeafDecay, RoseStacker, SearchChestshop, Shopkeepers, ShopkeepersAddon, SkinsRestorer, sleep-most, TAB, Trademarker, Vault, VillagerTradeLimiter, VotingPlugin

Agreements

Additional context

No response

@Phoenix616
Copy link
Member

Please test with the latest development build... that option is there so that you actually acknowledge that, not to blindly press the check box.

Also please provide your alias config file.

@FITFC
Copy link
Author

FITFC commented Jun 23, 2022

https://mclo.gs/GLWp951

My ItemAliases doesn't even have minecraft:mud and it still has this problem, it seems to come from the plugin itself

@Phoenix616
Copy link
Member

Well I'm not sure why you named the issue like that then if it's not about an alias... also please provide the log/error when using the latest dev build if it still occurs with that.

@Phoenix616 Phoenix616 changed the title ItemAlises problem Can't create short item name for mud Jun 23, 2022
@Phoenix616
Copy link
Member

Actually I think I found your issue, you specified an alias in your itemAliases.yml that matched with "mud": https://mclo.gs/GLWp951#L299 Adding mud itself to the config should solve that or obviously removing those entries.

@FITFC
Copy link
Author

FITFC commented Jun 24, 2022

This is the translation for my language, and it's not just "mud" it's "muda"

@Phoenix616
Copy link
Member

Well yes but aliases have a priority over normal string name and additionally there is logic that only matches partial names. It's possible that if you add mud: mud to the config that it starts to work.

Of course that is not ideal and I will definitely look into improving that part. (Hopefully soon)

Phoenix616 added a commit that referenced this issue Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants