Bug Reports & Support¶
Contact¶
| Method | Contact |
|---|---|
| Technical Support | support@orvit-ent.com |
| nilotoon@gmail.com | |
| Discord | kuronekoshaderlab (+friend request / group & server invitations) |
| Slack | kuronekoshaderlab@gmail.com (workspace invitation) |
| Other | QQ/WeChat ID available |
Please include information that identifies you as a customer (e.g., buyer name / invoice number / email).
Bug Report Guidelines¶
When filing a bug report, please include the following information if possible:
| Item | Example |
|---|---|
| Unity version | Unity 2022.3.62f2 |
| NiloToon version | NiloToon 0.17.11 |
| Bug description | A red error message appears. The error message is ______ |
| Reproduction steps | Enable the ___ toggle and build the game, then the error message appears |
| (Optional) Minimal reproduction project zip | Bug reports with reproducible files are given highest priority |
Communication Languages¶
Text-based communication is available (no voice calls):
- English
- Chinese
- Other languages (via AI translation, e.g., Japanese, Korean)
NiloToon File Access Permissions¶
The following table shows who can access NiloToon files. This is very similar to Unity Asset Store's single entity and multi-entity licenses.
'Can Access' means: A person who can view or use NiloToon files for your or your company's projects.
License Types¶
| License | Description |
|---|---|
| Personal License | For yourself only |
| Single-Entity License | For one company only -- includes employees and internal interns |
| Multi-Entity License | Includes affiliates, subsidiaries, and external contractors |
Access Permission Chart¶
| Role/Relationship | Needs NiloToon Access? | Personal | Single-Entity | Multi-Entity | Separate License Required? |
|---|---|---|---|---|---|
| Full-time employee | Yes | No | Yes | Yes | No |
| Part-time employee | Yes | No | Yes | Yes | No |
| Internal intern | Yes | No | Yes | Yes | No |
| External intern | Yes | No | No | Yes | No (when applicable) |
| Freelancer/Contractor | Yes | No | No | Yes | No (when applicable) |
| Affiliate/Subsidiary employee | Yes | No | No | Yes | No (when applicable) |
| Client (no NiloToon file access) | No | Yes | Yes | Yes | No |
| Client (needs NiloToon file access) | Yes | No | No | No (contact for special permission) | Yes |
| End user/Consumer | No | Yes | Yes | Yes | No |
Core Principle
Including NiloToon in your final product is fine. There is no issue as long as the recipient/user cannot access NiloToon's source files.
Providing Source Files to Clients
Clients who receive a Unity project containing NiloToon source files must purchase their own NiloToon license if they need to access NiloToon.