Engine - Plugin System Upgrade
● The plugin system now includes version management. When a plugin is published, a new version will be created along with snapshots of the engine version and template versions at the time of release. This resolves compatibility issues caused by template updates (e.g., architectural changes).
Users can later install the corresponding version (provided the plugin author does not voluntarily remove older versions).
● The plugin panel now includes a search function to easily find installed plugins.
● The plugin panel now includes a "System" category. In the future, identical modules across different template editors may be implemented as system plugins for unified update management.
● The plugin panel now displays plugin versions. A clear prompt appears when a plugin is not the latest version. However, upgrading a plugin version may not be compatible with the current project. Please review the update notes and back up your project.
● The plugin panel now includes "My Releases", providing quick access to "Plugin Management" (plugins I have published) on the cloud platform.
● After downloading and installing a plugin, its commands will now be placed in a separate section named after the plugin, rather than all under the "Plugins" section. (The command panel width has been slightly adjusted.)
Notes:
More plugins are not necessarily better. Plugins may affect project performance or cause errors in existing functionality. Choose based on your needs. When issues arise, prioritize checking if they are caused by plugins (e.g., create a plugin-free project to compare).
Different plugins may conflict or be partially incompatible. Testing is required.
After installing a plugin, right-click to view its installation data and understand what it adds.
If prompted to overwrite an installed plugin, the original plugin will be uninstalled first, which may clear its data. Please back up your project first (so you can duplicate the plugin's module data in a separate instance).
Engine
● The "About" menu now displays the current template version number (e.g., v1.3).
● The "Template Update" menu now displays the target version number (previously only the target version ID), along with an added reminder.
(This feature is intended for professional developers. If you have never used version control software such as git or svn, please do not use it to avoid errors after updating.)
● Template publishing now supports .gitignore files. Future template projects will include a .gitignore file for the convenience of git users.
● Fixed a bug where parameter passing errors in certain situations caused crashes
● Other minor adjustments.
Cloud Platform
● Optimized query efficiency of the Plugin Store.
● Plugin Store search now only starts when Enter is pressed or when the input field loses focus.
● The popularity ranking in the Plugin Store is now sorted by the number of favorites.
● The Plugin Store now features a "Chaos Zone" where plugins from unverified developers are displayed. When a plugin receives >= 10 favorites, it will be upgraded to an official plugin.
After a certain number of plugins from an author have been upgraded to official status, the author will automatically become a verified plugin author. Future plugins they publish will automatically enter the official zone (violations may still lead to demotion or bans).
Based on the current plugin ecosystem, some plugin authors will directly become verified plugin authors.
● Plugin category filtering now includes "Include Selected Categories" (default) and "Exclude Selected Categories" (e.g., selecting to exclude material plugins will hide them from view).
● Template filtering now includes "Template Specific" (default) and "Template Compatible". When filtering plugins by selecting a specific template, you will no longer see a large number of compatible plugins.
When publishing a plugin that is universally compatible, you no longer need to select multiple templates. For example, for RPG plugins, just select "Feather of Cyan"; for ACT plugins, select "Jump of Sky"; or simply select "Universal".
● User Center - Plugin Management: Added version management for plugins. Generally, historical versions should not be removed so users can find and install the appropriate version. However, if a clearly erroneous version is published, it can be removed/deleted.
● Fixed an error where announcements on the cloud drive project page still popped up after deletion.
● Fixed an error where accepted respondents did not receive rewards after completing a bounty (caused by a previous update; data from that period will be corrected one by one soon).
● Other minor adjustments.