Repository navigation
Troubleshooting and Unsupported Errors
If you see a Java error, ask the following before submitting a ticket:
- Is your version of Vault supported?
- Does the plugin have the correct SQL credentials?
- Have you done anything that creates an unsupported error?
The sections below contain a list of things that you should never do while using EtherMarket. If you disregard this page and do these anyway, I will do my best to help you, but you may create a problem that is difficult to fix. I've provided known fixes to these problems here as well.
EtherMarket is built to perform checks on signs that have the shop header, so if you bypass all the destruction checks with WorldEdit, you can have the shop exist in the database, but not in the physical world. If a shop is ever created in this location again, you can run in to the problem of having two shops in the same location; if this happens, see the generic fix section below.
Changing the sign-header will cause all of the existing shop signs to become unrecognizable, while still leaving them in the database. If a shop is ever created in these locations again, you can run in to the problem of having two shops in the same location; if this happens, see the generic fix section below.
Everything in the database is put there to be converted from a string of characters to different objects; if you tamper with these, you can cause the plugin to not be able to read the item, which will cause an error. You can also accidentally create an entry for a location where there is no shop block; if this happens, see the generic fix section below.
If you are experiencing problems, you likely have two entries in your database for the same block location. EtherMarket looks up shops by their location, so having duplicate entries can cause unexpected results. To fix this, you simply need to remove all the shop entries for that location from the database, then make the shop again. The below image shows two conflicting entries:
