1
0
mirror of https://github.com/Zrips/Jobs.git synced 2024-06-24 13:44:49 +02:00

Updated Legacy config support (markdown)

montlikadani 2021-04-09 18:37:31 +02:00
parent e526a2775b
commit f8fdcb160b
2 changed files with 19 additions and 19 deletions

19
Common-issues.md Normal file

@ -0,0 +1,19 @@
1. `Job woodcutter has an invalid break type property: (wheat)! Material must be a block! Use /jobs blockinfo on a target block`
- Materials inside of jobs must be blocks, not items when placing.
2. Materials, entities, and other elements appear repeatedly in the GUI.
- This usually happens on legacy (1.12 and below) versions. To fix this, change those materials to the appropriate one. You can use legacy websites that support these item IDs.
3. Some materials or entities do not work properly on versions 1.15 and higher.
- This can generally cause that you use IDs (numbers) that are considered obsolete since 1.12. To avoid this, use the full name of that material.
4. Some blocks when placed and broken do not give pay when you are given a job.
- `PlaceAndBreakProtection` can cause this, as if it is enabled it can delay payments and even cancel them for 14 days or less depending on the setting. To avoid this, disable it in generalConfig or modify in the restrictedBlocks file that contains these blocks.
5. Players are not paid, only operators.
- There are several reasons why the plugin does not pay:
- The first is that the Vault is not installed properly. If you do, make sure you use CMI as a essential plugin if you install the Vault developed by the CMI developer and enable its integration into the CMI configuration.
- With vault and all other installations, `jobs.use` and `jobs.world.worldName` (worldName is the world the the plugin should pay for players) permissions are required, which give players permission to ever get paid. For permissions assignments, we recommend [_LuckPerms_](https://www.spigotmc.org/resources/28140/) as a provider.
6. People can make infinite money by breaking and placing the same blocks over and over
- If you want to prevent this infinite money "exploit", make certain blocks have a negative value to place, and positive value to break. This will cause people who break/place the same block over and over again to lose money, or gain money very slowly (depending on what values you choose).
- For some blocks (such as wheat crops), you can check against the data values as well, and only payout when breaking fully grown crops, and optionally deducting experience and money when breaking ungrown crops.
**Other measures and corrections**
1. Make sure that you using the latest or development version of Jobs
2. Try to remove the `Translatable_Words` file and let it re-generate a new one by reloading the plugin with `/jobs reload` command.

@ -1,19 +0,0 @@
### **Material errors in the console when loading the plugin and can't fix it?**
```
Job woodcutter has an invalid break type property: (wheat)! Material must be a block! Use /jobs blockinfo on a target block
```
If you get this console warning, from this you can know that the material you specified (or default) does not exist in your current version, so it needs to be corrected or deleted.
**Don't know how to fix it?**<br>
We can recommend that you learn how to handle console errors without consulting a developer before building a minecraft server.
### What should I do when repeat the names of materials/entities and other elements in the GUI or chat?
**This has already been fixed in the latest versions.**
Related Issues: [#459](https://github.com/Zrips/Jobs/issues/459), [#348](https://github.com/Zrips/Jobs/issues/348), [#296](https://github.com/Zrips/Jobs/issues/296), [#282](https://github.com/Zrips/Jobs/issues/282), [#288](https://github.com/Zrips/Jobs/issues/288)
**What to do?**
1. First, make sure that you using the latest or DEV version of JobsReborn.
2. Make sure you use the **full name of the materials**, **not** the ID.
3. The following is not feasible, that when Minecraft release new materials/entities etc. in a new version, unfortunately it does not have an official **Internal ID** released. This is because we use a custom enum system to support fallback versions and we need official Internal ID to work that item.
4. Try to remove the Translatable_Words file (with your language) and let it re-generate a new one. ([#367-comment](https://github.com/Zrips/Jobs/issues/367#issuecomment-495986511))