FAQ - Minecraft-Maxmc/KingdomsX-ChineseTranslation GitHub Wiki

Can I get the plugin for free?

Please refer to this section.

Support for 1.8 and lower versions

Please DO NOT ask me to support 1.8 ever. This version is extremely outdated, it's click here old.
Almost 40% of the plugin features will stop working on this version and it's incredibly hard to maintain.
The only reason 1.9 and versions above are supported is because they're just easier to maintain. I always recommend using the latest Spigot version. The plugin doesn't guarantee that the old versions will always be supported.

If your reason for not using 1.9+ is the PvP mechanics, use OldCombatMechanics.
Another excuse I usually get is that, "1.8 is more stable". 1.12 is better than 1.8-1.11 in both performance and stability aspects. The only reason it uses a little more resource is because of the newly added features which is completely normal.

Why players can't pickup turret and structure items?

They're probably in creative mode. Players cannot do that because they'll be able to duplicate the item in creative and use it everywhere. If you like an admin to bypass this, give them kingdoms.creative.pickup permission.

Why aren't my turrets shooting?

Make sure your turrets have enough ammo. You can buy ammo for your turret by right-clicking them and pressing the ammo button.

Duplicated Chat

If you want to use another chat plugin other than kingdom's built-in system, you have to go to chat.yml -> global-channel -> format -> false
Another thing you can do is to parse kingdom chat formats as placeholders to use in other chat plugins (if they support the use of normal chat channel AsyncPlayerChatEvent) by going to chat.yml -> parse-as-placeholder -> true
Most people use another plugin because the support hovering on messages. Kingdoms also support that too if you want to use it.

When breaking the block underneath turrets, they still work.

This is not a bug. The block is not required for the turret to continue working. It's just a practice to encourage players to put their turrets on specific blocks. You cannot force the turrets to stop working after the block is broken, because it can lead to server lag when used excessively. This is a planned feature for future updates.

Cannot translate placeholders for null player

Related errors: /k disband and clicking on a turret
This is a 1.15/1.16 Spigot bug and I can't fix it, Spigot is supposed to do it which they already did. This happens to any GUI that has a hopper (and a few other special types) inventory. You'll have to update your server either by running BuildTools (Spigot) or getting a direct download from Paper. Please avoid any other websites (even your host's provided Jars) or forks. They're mostly outdated as well and won't fix the issue.

Players are getting kicked because of turrets

Only Inferno turrets can cause this. Unfortunately, due to these turrets using a beam, BungeeCord networks can't handle this, so this only happens if you're using BungeeCord. To fix this, simply go to the inferno turret's config and change the turret mechanic type to something else. You can delete the turret entirely, however if you do, all the placed inferno turrets will be bugged.
This issue currently has no proper fix yet as it's something between a BungeeCord bug and an advanced code that isn't used directly from the Spigot API.

Bank services are currently unavailable

This means you either don't have Vault or an economy plugin installed.
You can use any plugin if it supports Vault. Plugins like EssentialsX or CMI (CMI provides their own Vault version) support Vault.

What links can I use for Dynmap flag?

You need to use a link that points directly to an image file. This can be a png, jpg and etc. By a direct link, it means that when you open the link in your browser, it must only open an image and nothing else. They all end with the image's file extension. Here are some examples:
Direct Links

Invalid

Changing relation attributes has no effects

If you've changed the default relation attributes in relations.yml, the previously created kingdoms will not inherit the new settings by default. They'll keep their old settings. To prevent this, you could disable custom-attributes option in relations.yml config, and maybe even remove the relation attributes from nexus settings GUI entirely.

If you've changed the settings for your own kingdom in nexus settings, it'll only take effect once both kingdoms have the same attribute enabled for the same relation. You can change this by disabling agreements option in relations.yml, but it's definitely not recommended. For example, if kingdom A has ceasefire attribute enabled, but kingdom B doesn't have that enabled, then both kingdom A and B will be able to fight each other, however this is not the case when you change the agreements option.