View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000146 | RPG Architect | Feature Request | public | 2024-03-20 01:48 | 2024-10-14 18:19 |
Reporter | Mondune | Assigned To | Locke | ||
Priority | low | Severity | feature | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | Early Access | ||||
Target Version | 1.0 | ||||
Summary | 0000146: Showing that local Data and Scripts in use | ||||
Description | I'm approaching this idea from the point of a new user, and looking at sample projects and trying to reverse engineer them. I ran into a moment recently when I was trying to advance the logic for the battle system to test animations, and the last detail I picked up on was that you had setup scripts to execute some of the battle logic. There was not a highlight or a marking that told me you were using some of the predetermined script options. I would be more likely to click on things when discovering the editor if they have markings and highlights to make them stand out and tell me this piece of the workflow is in use. I don't have a good idea of how to mark these right now, but I still think the idea will be important for new user experience. Edit* Idea 1, I mentioned using Icons in the buttons to help define them more, what if there were 2 versions of those icons, a grey scale and a colored version, not in use and in use? | ||||
Tags | Editor | ||||
Attached Files | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2024-03-20 01:48 | Mondune | New Issue | |
2024-03-20 01:48 | Mondune | Tag Attached: Editor | |
2024-03-20 01:48 | Mondune | File Added: support.rpg-architect.png | |
2024-03-20 01:48 | Mondune | File Added: support.rpg-architect-2.png | |
2024-03-21 20:47 | Locke | Target Version | => 1.0 |
2024-10-11 16:47 | Locke | Assigned To | => Locke |
2024-10-11 16:47 | Locke | Status | new => assigned |
2024-10-14 18:19 | Locke | Status | assigned => closed |
2024-10-14 18:19 | Locke | Resolution | open => fixed |