> For the complete documentation index, see [llms.txt](https://codingguru1968.gitbook.io/inventorystacks-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codingguru1968.gitbook.io/inventorystacks-wiki/troubleshooting-and-faq.md).

# 🛠️ Troubleshooting & FAQ

#### ⚠️ "My items aren't stacking!"

If items aren't stacking as expected, it is almost always due to one of three reasons:

* Different NBT Data: If an item has extra data (like enchantments, custom names, or attributes), Minecraft treats it as a unique object. Even if they are the same type (e.g., two iron swords), if one has a hidden tag and the other does not, they will not stack.
  * *Tip:* Press `F3 + H` in-game to see the "Advanced Tooltips." If you see extra data tags, that is why they aren't stacking.
* Plugin Conflicts: Other plugins that modify inventory logic, storage, or item metadata may conflict with **InventoryStacks**.
  * *Diagnosis:* Try temporarily removing other plugins to see if the issue persists.
* Config Priority: Ensure the item name in your `config.yml` exactly matches the Material name. If the name is misspelled, the plugin will revert to vanilla stacking logic.

#### ⚠️ "Visual Glitches in Chests/Hoppers"

For versions 1.8 – 1.20, there is a known, unsolvable visual glitch where containers (chests, hoppers, etc.) may show items as being at the vanilla limit (e.g., 64) even if they contain more.

* Note: This is a purely visual limitation of the Minecraft client in these versions; the items are actually stored correctly by the server.

#### ⚠️ "I updated, and now my stacks are acting weird!"

If you recently updated Minecraft (e.g., to 1.20.5+) or the plugin, check your `use-legacy-reflection` setting. Modern versions handle `ItemMeta` differently. If you are experiencing instability, try toggling this setting in your `config.yml`.

### 🛠️ Diagnostic Steps 

If you cannot find a solution here, please follow these steps before opening a support ticket:

1. Check the Logs: Open your server’s `latest.log` file. Look for lines containing "Error," "Failed," or "Exception."
2. Verify Versions: Ensure your server software (Paper/Spigot/Purpur) is on a supported version for your specific plugin build.
3. Clean Test: If possible, test the plugin on a server with no other plugins installed to confirm it is not a conflict.
4. Get Support: If you’ve gathered your logs, join our [Discord Support Server](https://discord.gg/Rqmngywv57) and provide your `config.yml` and a copy of the error from your logs.