Help & Support¶
Where to get help, report a bug or send feedback.
Get help¶
Stuck, or does the tool not behave the way this manual says? You can reach us here:
- Discord is the fastest way to get an answer. Ask a question, share a screenshot or post the steps that break. Other users are there too.
- Contact page lists every way to reach us.
- Email support@creativespore.com and we'll get back to you.
- Unity forum thread, where the asset has been discussed since 2014. Years of questions and answers are there if you want to search.
The Join our Discord and Contact Support buttons in the welcome window (Tools > RpgMapEditor > Welcome) open Discord and the contact page.
Before you write, look through Troubleshooting and the FAQ. A lot of reports turn out to be one of a few things: Edit not pressed in the Paint tab, changes that were never committed, or Save Changes After Playing left on. The demo scenes are a good 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/RpgMapEditor/Documentation/RPG Map Editor Manual.pdf, and Open PDF Manual in the welcome window opens it. It works offline and matches the version you imported.
What support covers¶
Covered: setup and configuration questions, bugs you can reproduce, and anything this manual gets wrong or leaves out.
Not covered: writing game features for you, debugging other assets or your own code, and general game design.
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 the following can usually be reproduced straight away.
Your Unity version. It is in Help > About Unity and in the title bar of the editor window. Say which render pipeline the project uses too.
Your RPG Map Editor version. Open Tools > RpgMapEditor > Welcome and read the bottom right corner. It is also the first line of Assets/CreativeSpore/RpgMapEditor/changelog.txt.
The console output. Copy the full text of any error or warning, with 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. For anything visual, like autotiles that do not join or collision in the wrong place, a screenshot or a short recording helps a lot.
If the problem only shows up with your own tileset, send a small project or a .unitypackage with the tileset, its sheets, the Map Data asset and a scene that shows it.
Leave a review¶
If RPG Map 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.com/invite/hS9qyDXZdw |
| Contact page | https://www.creativespore.com/contact/ |
| Support email | support@creativespore.com |
| Unity forum thread | https://forum.unity.com/threads/soon-rpg-map-editor.278604/ |
| Asset Store page | https://u3d.as/anj |
| Online manual | https://www.creativespore.com/docs/rpg-map-editor/ |
| Website | https://www.creativespore.com |