Help & Support¶
Where to get help, report a bug or send feedback.
Get help¶
Stuck on something, or does the tool not behave the way this manual says? Two ways to reach us:
- Discord: the fastest way to get an answer. Ask a question, share a screenshot or post a repro and we'll take a look. Other users are there too.
- Email: write to support@creativespore.com and we'll get back to you.
The Join our Discord and Contact Support buttons in the welcome window (SuperTilemapEditor > Welcome) open the same two links, and the email one starts a message with the subject already filled in.
Before you write, check Troubleshooting and the FAQ. The most common report, painting that does nothing, is almost always the Move, Rotate or Scale tool being active in the scene view. Painting needs the Rect tool (T) or no tool. The demo scenes are a useful test as well: if something fails in your project but works in one of the Sample Scenes, the difference between the two is usually the answer.
The manual ships with the package
A PDF of this manual is at Assets/CreativeSpore/SuperTilemapEditor - Extra/Documentation/SuperTilemapEditor Manual.pdf. It has the same content, works offline, and matches the version you imported rather than whatever is newest on the site.
What support covers¶
Covered: setup and configuration questions, reproducible bugs, and anything this manual gets wrong or does not explain well.
Not covered: writing game-specific features, debugging third-party assets or your own code, and general game design.
If you are not sure whether a question fits, ask anyway.
Report a bug¶
Discord is the best place for it, and email works just as well. A report with these four things can usually be reproduced straight away.
Your Unity version. It is in Help > About Unity and in the title bar of the editor window. Name the render pipeline too (built-in or URP), since materials and parallax depend on it.
Your Super Tilemap Editor version. Open SuperTilemapEditor > Welcome. The version is in the bottom right corner of the window. You can also read it from the first line of Assets/CreativeSpore/SuperTilemapEditor/changelog.txt.
The console output. Copy the full text of any error or warning, including the stack trace below it. In the Console window, select the message and the trace appears in the lower pane. If the editor crashed or froze, send the editor log instead. The Console window's menu has Open Editor Log, or find the file here:
| System | Editor log |
|---|---|
| Windows | %LOCALAPPDATA%\Unity\Editor\Editor.log |
| macOS | ~/Library/Logs/Unity/Editor.log |
| Linux | ~/.config/unity3d/Editor.log |
Steps to reproduce. Numbered steps from a known starting point, ideally a new scene or one of the demo scenes. Say what you expected and what happened instead. A screenshot or a short screen recording helps with anything visual, like seams between tiles or a collider in the wrong place.
If the problem only shows up with your own tileset, a small project or a .unitypackage with the tileset, its atlas texture and a scene that shows the problem makes it much faster to track down.
Leave a review¶
If Super Tilemap Editor saved you time, a rating on the Asset Store helps a small studio more than anything else you can do. Thank you.
Links¶
| Discord | https://discord.gg/hS9qyDXZdw |
| Support email | support@creativespore.com |
| Asset Store page | u3d.as/ouJ |
| Video tutorials | YouTube playlist |
| Online manual | https://www.creativespore.com/docs/super-tilemap-editor/ |
| Website | https://www.creativespore.com |