̶H̶i̶,̶
̶T̶h̶e̶r̶e̶ ̶i̶s̶ ̶a̶ ̶c̶r̶i̶t̶i̶c̶a̶l̶ ̶p̶r̶o̶b̶l̶e̶m̶.̶ ̶A̶n̶y̶ ̶e̶v̶e̶n̶t̶s̶ ̶t̶h̶a̶t̶ ̶c̶o̶n̶t̶a̶i̶n̶ '̶E̶r̶a̶s̶e̶ ̶E̶v̶e̶n̶t̶'̶ c̶o̶m̶m̶a̶n̶d̶ w̶i̶l̶l̶ ̶c̶r̶a̶s̶h̶ ̶t̶h̶e̶ ̶p̶l̶u̶g̶i̶n̶.̶
̶1̶.̶ ̶C̶r̶e̶a̶t̶e̶ ̶n̶e̶w̶ ̶p̶r̶o̶j̶e̶c̶t̶
2̶.̶ ̶C̶r̶e̶a̶t̶e̶ ̶n̶e̶w̶ ̶e̶v̶e̶n̶t̶>̶S̶e̶t̶ ̶t̶o̶ ̶p̶a̶r̶a̶l̶l̶e̶l̶>̶P̶l̶a̶y̶ ̶B̶G̶M̶ ̶(̶a̶n̶y̶)̶>̶E̶r̶a̶s̶e̶ ̶E̶v̶e̶n̶t̶ ̶r̶i̶g̶h̶t̶ ̶a̶f̶t̶e̶r̶.̶
̶3̶.̶ ̶L̶a̶u̶n̶c̶h̶ ̶ ̶p̶r̶o̶j̶e̶c̶t̶ ̶>̶ ̶S̶h̶o̶u̶l̶d̶ ̶c̶r̶a̶s̶h̶.̶
Fixed in 1.0.21
Hi noname1848,
Thank you for reporting this issue and providing clear steps to reproduce it.
We take bug reports seriously, especially those that could affect game stability.
We’ll investigate the interaction between the CT Quest System and RPG Maker MZ’s Erase Event command using the steps you’ve provided.
If we can reproduce the issue, we’ll work on a fix and release an update as soon as possible.
We appreciate you bringing this to our attention and helping us improve the plugin.
— Cynthia Tools
Hi noname1848,
Great news! 😁
We’ve identified and fixed the crash involving RPG Maker MZ’s Erase Event command.
The issue was caused by how CT Quest System handled erased or inactive events when checking for NPC quest markers.
We’ve released CT Quest System v1.0.21, which includes:
✅ Version 1.0.21 is now available for download!
Please download the latest version and let us know if everything works correctly on your end.
A special thank-you for taking the time to report this issue and providing such clear steps to reproduce it. Your feedback genuinely helped us improve the plugin for everyone!
We really appreciate your support! ❤️
— Cynthia Tools
Hi,
First, thanks for the quick fix.
Plugin seems clean perfomance wise (important), tested on 100+ events environment map. Which was my primary concern.
Fixed in 1.0.23
I didn't have time to dig deep in the visual editor yet, but here few observations:
1. There is no simple plugin command to show/hide the tracker window.
For exemple, there is no way you want the game to show the tracker window at game start for exemple, or when when there is some cut-scene in the background.
Right now, unless mistaken, you may need to script call something like this:
const w = SceneManager._scene._ctqsTrackerWindow;
if (w) w.visible = false/true;
And more if you want it persistant between map transfert. Not really a good solution, a simple plugin command to show/hide tracker should solve this.
2. Right now the tracker windows 'capture' click and block map click by an override, which translate by the player not moving when clicking in the tracker window area. Making the whole tracker window a "dead weight" on the screen. If any events that need a click from the player is beyond the tracker window, you are stuck there forever. This is quite critical.
Hi noname1848,
Thank you again for your detailed feedback and for taking the time to test CT Quest System on a map with over 100 events!
We’re glad to hear that the plugin is performing well so far. Performance and stability are important priorities for us.
Both of your observations are excellent points, and we agree that these areas could be improved.
We agree! Developers should be able to control tracker visibility through simple plugin commands, especially during cutscenes, introductions, and other scripted events.
We’re planning to introduce Show, Hide, and Toggle Tracker commands, with visibility preserved across map transfers.
This is an important usability issue. We’ll investigate the current input handling and work on allowing map interactions behind noninteractive tracker areas while preserving the tracker’s own functionality.
Both improvements have been approved and will be implemented in our upcoming CT Quest System v1.0.22 update.
We really appreciate the time you’ve spent testing the plugin and sharing constructive suggestions.
We will start working on patch v1.0.22 by today.
Feedback like yours helps us make CT Quest System more reliable and developer-friendly.
Thank you for supporting Cynthia Tools! ❤️
— Cynthia Tools
Hi noname1848,
Great news! 😁
We’re happy to announce that CT Quest System v1.0.23 has officially been released!
Thank you again for your valuable feedback. We’ve implemented all three of your suggestions across our recent updates!
✅ 1. Show / Hide Quest Tracker
We’ve added Show, Hide, and Toggle Tracker Plugin Commands, allowing developers to control tracker visibility during cutscenes, introductions, and gameplay.
Visibility preferences also persist across map transfers and save/load.
✅ 2. Quest Tracker Map Click-Through
We’ve improved the tracker’s mouse interaction handling so noninteractive areas no longer unnecessarily block map clicks.
We’ve also removed the behaviour where clicking a quest title automatically opens the Quest Journal, preventing accidental menu interruptions.
✅ 3. Automatically Hide Empty Tracker
The tracker now automatically disappears when no active quests are being tracked and reappears when appropriate.
This feature is enabled by default and can be configured through Plugin Manager.
🎨 Additional Improvements in v1.0.23
We’ve also introduced customizable NPC ! and ? quest marker colours, a new Plugin Command for switching the tracker between the left and right sides, and a dynamic keyboard shortcut hint beside the Quest Tracker title.
These improvements were implemented while preserving existing quest data and save compatibility.
📦 CT Quest System v1.0.23 is available now:
https://cynthiatool.itch.io/rpg-maker-mz-plugin-ct-quest-system
We sincerely appreciate the time you’ve spent testing our plugin, especially your performance testing on maps containing over 100 events.
Your feedback has directly contributed to making CT Quest System better for everyone.
If you have the opportunity to try v1.0.23, we’d love to hear how it performs in your project!
Thank you once again for supporting Cynthia Tools and helping us improve our products! ❤️
— Cynthia Tools
Awesome! I tested quickly and everything looks quite nice! From a design perspective, I don't have anything meaningful more to say. I need to test more in-depth the quests mechanics, but it will take me quite some time (prototype I work on isn't that much advanced yet, but so far didn't found any conflicts over my 50+ plugins).
Thanks again for your patience and diligence.
