> For the complete documentation index, see [llms.txt](https://star-generator.gitbook.io/star-generator-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://star-generator.gitbook.io/star-generator-docs/troubleshooting/common-issues.md). # common issues ## Starter Items Do Not Load Check that one supported item provider is installed: * ItemsAdder * Nexo * Oraxen Then check whether the starter resources were generated in the provider folder. If the files were generated while the server was already running, reload the provider: ``` /iareload /nexo reload /oraxen reload ``` Use the command that matches the provider installed on your server. ## Recipes Say Items Are Missing Common causes: * The player has a visually similar item, but the metadata is different. * The ingredient should use a provider item path instead of a plain Minecraft material. * The item provider has not loaded its custom item registry yet. * The recipe uses a saved item that was changed after the last `/sg reload`. Fix steps: 1. Confirm the ingredient `type` in the recipe YAML. 2. Confirm the provider item can be obtained directly from the provider command. 3. Run `/sg reload`. 4. If the item is a one-off custom server item, save it with `/sg saveitem ` and use that saved path. ## GUI Buttons Can Be Moved This usually means that a button slot overlaps with a real input/output slot or an old config still uses a legacy slot. Check these slots: * `recipe-gui.recipeSlot` * `recipe-gui.openButton.slot` * `recipe-list-gui.open-slot` * `recipe-list-gui.openButton.slot` * `recipe-detail-gui.select-slot` * `reward-gui.openButton.slot` * `reward-gui.output` * `gui.craftingSlot` * `gui.progress_slot` * `energySetting.energySlot` * `energySetting.energy_progress_slot` Do not reuse the same slot for a GUI button and a real item slot. ## A Slot Is Outside The GUI Size If a button, background item, or progress item is configured outside the GUI size, StarGenerator skips that visual item instead of breaking the table load. Fix the slot in the WebUI GUI Layout editor or increase the GUI size to include the slot. ## Energy Bar Does Not Change Check: * `energySetting.useEnergy` is `true`. * `energySetting.maxEnergy` is above `0`. * `energySetting.energy_progress_slot` points to a valid main GUI slot. * `energySetting.energy_progress` contains valid item paths. * The table has received energy or has a valid fuel item. * The table is not already full when using `FULLY`. Example valid progress map: ```yaml energy_progress: 0: "itemsadder:starter_icecream:ui_energy_progress_0" 25: "itemsadder:starter_icecream:ui_energy_progress_25" 50: "itemsadder:starter_icecream:ui_energy_progress_50" 75: "itemsadder:starter_icecream:ui_energy_progress_75" 100: "itemsadder:starter_icecream:ui_energy_progress_100" ``` ## ModelEngine Table Has Missing Texture Or Was Renamed If the ModelEngine model id in table YAML no longer exists, the visual model can fail to attach. StarGenerator keeps the runtime table cache and can use fallback interaction so known placed tables can still be opened or broken. Check: * `table-entity.fallback-interaction.enabled` is `true`. * The table still exists in `plugins/StarGenerator/cache/models.yml`. * The table YAML still exists. * The `model` value in the table YAML matches the ModelEngine model id you want to use. After fixing the model id, run `/sg reload`. ## ModelEngine Tables Duplicate After Reload StarGenerator tries to relink existing table entities by UUID, tags, active model, and location. It also cleans duplicate table entities around the same anchor using `table-entity.duplicate-cleanup-radius`. Check: * Only one ModelEngine jar is installed. * `table-entity.duplicate-cleanup-radius` is small, such as `0.75`. * The table model id in the table YAML matches the intended ModelEngine model. ## Placed Tables Reappear After Breaking StarGenerator records intentional table deletion tombstones in: ``` plugins/StarGenerator/cache/deleted-tables.yml ``` Keep this enabled: ```yaml runtime-cache: deleted-table-tombstones: true ``` If old backups reference deleted table templates, keep this enabled too: ```yaml runtime-cache: purge-deleted-table-templates: true ``` ## Placed Tables Are Missing After Update StarGenerator stores placed tables in runtime cache and keeps timestamped backups. If a cache load looks suspicious, it tries older backups and copies bad files into: ``` plugins/StarGenerator/cache/bad/ ``` Do not delete cache files while the server is running. Stop the server before manual recovery and inspect: ``` plugins/StarGenerator/cache/models.yml plugins/StarGenerator/cache/backups/ plugins/StarGenerator/cache/bad/ ``` ## WebUI Editor Does Not Open Check: * The player has `sg.craftweb`. * The URL token has not expired. * The browser can reach the configured bind and port. * `web-editor.bind` is `127.0.0.1` unless remote access is intentionally enabled. * Another process is not already using the configured port. If needed, run: ``` /sg starteditor ``` again to refresh the token and print a new link. ## WebUI State Loads Slowly The item catalog is cached asynchronously. If it is rebuilding, the UI may show placeholders or stale catalog data briefly. Avoid enabling verbose debug logs on live servers: ```yaml debug: recipe-loading: false ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://star-generator.gitbook.io/star-generator-docs/troubleshooting/common-issues.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.