So glad there's a working version of Quickshop on 1.13, thank you. I have a small request though. One thing this plugin does that the original Quickshop does not is automatically remove existing LWC protections from shop chests. Do you think you could make this configurable?
Ghost_chu updated QuickShop Reremake ※ Merry Christmas and Happy new year with a new update entry: Compatibility Read the rest of this update entry...
wat this mean I bit confused? Code (Text): /qs fetchmessage - Fetch shop message manually from database.
You can make a addon to do that. QS didn't should do that, because i must keep QS's code clean, simple, dependless.Cuz just like that, i can update to new Minecraft version quickly.
I am not a developer, this option would make your plugin usable because for now players can create shops anywhere
Maybe you will like check the Towny Addon, If you using the AreaShop, you can enable AreaShop support in config.yml
I do not use Towny Addon i have other plugin that manages this. Why not make it compatible with the allow-shop flag? This would be a big plus for your plugin.
No WG support!? Dam i'd really like to use this plugin, would u reconsider then instead of dev builds try BETA builds for WorldGuard, the API doesn't change as often. That's what I notice a lot of plugin authors/devs are doing lately when adding WorldGuard compatibility https://dev.bukkit.org/projects/worldguard/files
Try this one https://github.com/Ghost-chu/QuickS...d/v0.1/QSRRWorldGuardAddon-0.0.1-SNAPSHOT.jar flag:qs-shop-create
Try this one https://github.com/Ghost-chu/QuickS...d/v0.1/QSRRWorldGuardAddon-0.0.1-SNAPSHOT.jar flag:qs-shop-create
For me it does not work: https://hastebin.com/wepodaqoco.coffeescript I have WG 7.0.0 snapshot 1763. I also tried with the BETA 3, it does not work either. The plugin does not launch
Sorry, you may need try https://github.com/Ghost-chu/QuickS...d/v0.2/QSRRWorldGuardAddon-0.0.1-SNAPSHOT.jar
Hey, I discovered a weird issue with the logs file. For some reason the plugin is writing empty lines into qs.log several times a minute. They just show up as "{}" with a timestamp before it. Can this be fixed?