# Shop Issues

* If you encounter a Nitrado Internal Server Error with the message "Target path does not exist", this means that you must rename your cfgeffectarea.json file to cfg**E**ffect**A**rea.json (case-sensitive)

<figure><img src="/files/WR5Jhf5z2aK3ZYxMMbwv" alt=""><figcaption><p>Example, how the Nitrado Internal Server is displayed when the cfgEffectArea.json file is not in camel-case</p></figcaption></figure>

* Corrupted files ("cfgEffectArea.json" for normal items, "events.xml" and/or "cfgeventspawns.xml" for subscription items)
* If normal items don't spawn, check if the entries got added to the cfgEffectArea.json file, and if it's the case, it means it was either a unsuited location or a game server error that is not bot related
* If subscription items don't spawn, check if the entries got added to the events.xml & cfgeventspawns.xml file. If it's the case, you most likely have to adjust the event code as the bot does nothing other than create unique event entries which behave the same as any other event; therefore, you should have good knowledge of how events work and how to configure them before trying to use them with the bot
* If normal items keep respawning after each restart, check if the entries are still present in the cfgEffectArea.json file, and if it's the case, you have to remove them manually. If they are not present but still respawn, it is a game server-related issue that can't get fixed by the bot. If the entries were present after a restart (which they shouldn't) and kept respawning, it was either caused by the file being corrupted or a Nitrado API Error (for example, if the bot lost connection to the account, ...)


---

# Agent Instructions: 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://docs.killfeed.xyz/troubleshooting/shop-issues.md?ask=<question>
```

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.