Support#

We want you to succeed without writing to us, which is why every problem has a code, a fix and a page. When that is not enough, we help.

What we help with#

• Bugs in the template: something the template does wrong, in Unity 6000.6, in the template's own code, content or tools.
• Documented questions: anything this manual, Errors.md or the feature READMEs cover, when the steps do not work for you or are unclear.
• Build errors the Build Error Explainer does not recognise: they become new rules and entries for everyone.

What we do not cover#

• Custom features and changes to the code. New systems, tabs or mechanics need C#; they are your own code. Add your own tab and Code architecture are the documented starting points.
• Changes made by an AI assistant or another asset, and conflicts with other Asset Store packages.
• Other Unity versions than 6000.6.
• Third-party services themselves: accounts, dashboards, payouts and policies of Google Play, the App Store, Unity Gaming Services, LevelPlay, AdMob or Firebase (we help with how the template uses them).
• Store review decisions, and legal or tax advice.

Before you write#

Do it with AI (skill explain-code, set up once): ask your agent "Explain this error and how to fix it:" and paste the red Console lines, plus the Build Error Explainer's yellow line (Tools > Idle RPG > Build Errors). Most answers are one prompt away.

1. Search FAQ and troubleshooting, the known issues and the code's entry in Errors.md.
2. Hub > Release > Check for Android / iOS: many problems have a Fix.
3. Tools > Idle RPG > Validate Content: content problems with the asset to click.
4. Make sure you are on Unity 6000.6 and the latest template version (Changelog and updating).

Send the diagnostic report#

Hub > Help > Copy diagnostic report copies a plain-text report: Unity and template versions, operating system, platform, whether Make it yours ran, the features that are on, each service's mode and package version, the scripting defines, the last Pre-flight codes and the last explained build errors.

It leaves out your keys, e-mail addresses, web addresses with logins and most of your bundle id, so it is safe to paste. Read it before you send it anyway.

For a build error also copy the red lines from the Console (or Tools > Idle RPG > Build Errors > Copy diagnostic).

The support page#

https://idle.nextapplab.eu/support** (Hub > Help > **Support). Send:

• Your Asset Store invoice number. Support requires it (it is in your purchase e-mail and in your Asset Store order history).
• The diagnostic report.
• What you did, what you expected and what happened; a screenshot if it shows the problem.

One problem per message gets the fastest answer.

Known issues#

Problems that are not the template's and that we cannot fix from here. Each one is harmless.