Wiki Release: 2026.09.5 · UltimateClans: 9.1.4 · Documentation branch: 9 · ClanFarmCoins
ClanFarmCoins troubleshooting#
Use this page when ClanFarmCoins loads but a gameplay/admin workflow does not behave as expected. Start with the narrow symptom rather than changing multiple configuration sections at once.
Fast diagnostic order#
- Confirm the component loaded and its required Core version is compatible.
- Reproduce with a non-OP test account and verify the exact command/role permission.
- Check YAML syntax and the specific feature section involved.
- Verify optional providers (economy, map, hologram, entity, Redis, WorldGuard, etc.) only when that feature depends on them.
- Check persistent storage and cross-server synchronization after configuration/permission checks.
- Read the first component-specific console error produced during startup or reproduction.
Common symptoms#
| Symptom | Likely causes | What to check / fix |
|---|---|---|
| No coins drop | Source not configured, creative mode, disabled world/region, player not in clan, or role permission blocks it | Check the exact source and all filters using a normal player account. |
| Placed blocks can be farmed repeatedly | Placed-block follow/prevention rule is disabled or storage was reset | Enable the intended tracking rule and preserve its data. |
| Coin item drops but cannot be picked up | Pickup permission/filter or custom item identity does not match | Check role pickup permission and item configuration. |
| Rewards are too frequent | Chance/amount/source list is too broad | Reduce one source at a time and retest statistically. |
Configuration validation#
Focus on these configuration areas for this component: Config. Preserve exact YAML indentation and key names.
Storage and restart checks#
- Do not delete live storage as a first troubleshooting step. Make a backup and inspect it first.
- If the issue appears only after restart, compare what is persisted with what is rebuilt in memory at startup.
- If the issue appears only on one server in a network, compare the component version, config, database and sync channel on that server.
- After a failed migration/recovery operation, keep the original data until the failure is understood.
What to include in a support ticket#
Provide the product/core version, component version, Minecraft/server implementation, the exact command/action used, the relevant config section, and the first related console error. Avoid sending passwords, database credentials, webhook secrets or API keys.
Diagnostic workflow#
Use this order before changing multiple settings at once:
- Startup: find the first warning/error mentioning this component; later exceptions are often consequences.
- Version/dependencies: verify the parent plugin version and every required/optional integration actually detected at startup.
- Configuration: validate YAML indentation/types and compare the relevant path with the default documented in this Wiki.
- Access: test both Bukkit permission and UltimateClans role/internal permission using a non-OP player.
- Context: reproduce in an allowed world/region and check claim/PvP/economy hooks if the feature depends on them.
- Persistence: restart and verify state is loaded from the intended YAML/SQLite/MySQL backend.
- Multiserver: reproduce on a single node first, then verify identical configs/storage/sync on all nodes.
- Isolation: disable unrelated integrations one at a time only when the evidence points to a hook conflict.
What to include when requesting support#
- Exact plugin/core/component versions.
- The command/action performed and expected result.
- The first relevant console exception/warning, not only the last line.
- The relevant configuration section with secrets removed.
- Whether the problem reproduces with a non-OP player.
- Server software/version and whether the server is part of a multiserver network.
Files worth checking#
coins.ymlconfig.ymllanguage/Lang_EN.ymlpolymart.yml
FarmCoins-specific diagnostics#
No coin is generated from mining#
Check the block material against the coin's miner list, confirm chance is greater than 0, and verify only_with_clan, disable_creative, world/region filters and the coin's optional permission. The mining listener also checks supported claim/region build permission before calling the reward logic. If block-following is enabled, a block tracked as player-placed is intentionally ignored to reduce farming loops.
Mob kills never reward#
The killed entity type must appear in mobs; the killer must be a player; Creative-mode filtering and clan/world/region/permission rules still apply. Test with a coin temporarily set to a high chance and a single known mob to separate eligibility from probability.
Fishing does not reward#
The fishing event must finish in the caught-fish state and the caught item's material must be in fishing. Test with a common fish and a high chance first.
Player combat rewards do not trigger#
The relation stored in players must match the victim relationship (MEMBER, ALLY, RIVAL, NEUTRAL). The core PvP checks and region PvP integration must both allow the attack; the addon will not reward a combat action that the clan/region rules consider disallowed.
Physical coin drops but cannot be saved/picked up#
Check Config.Farm.allow_pickup, the coin_pickup/coin_save clan-role permissions, and verify the item still carries the FarmCoins NBT/metadata. Plugins that replace dropped items can strip metadata and make the item look correct while no longer being a valid FarmCoin.
Coin definition logs “cannot be loaded”#
Validate type (POINT, MONEYBANK, LEAGUEPOINT), coin (VIRTUAL, PHYSICAL), material names and number types. One malformed definition is skipped while other definitions may continue loading, so identify the exact coin ID reported in console.