Plugin Finder has been released

[ggg_kuroda]

We are pleased to announce the release of “Plugin Finder,” a tool designed to search, read, and extract plugins for RPG Maker MV/MZ, accessible directly from your web browser. No installation is required; simply open the link in your browser to start using it.

Plugin Finder

Before introducing the features, we would like to express our sincere gratitude to all the plugin authors.

■ To Plugin Authors
This tool exists solely because of the plugins you have shared. Therefore, we handle them with the utmost care and respect.

• We only list plugins released under the MIT License. Copyright remains with the original authors as always.
• If you do not wish for your plugin to be listed, simply add a single line containing @no-localizeno-localizeno-localizeno-localizeno-localizeno-localizeno-localizeno-localize to your source code. No application or contact is required; the removal will be reflected within approximately 24 hours.
• The author’s name, GitHub links, and the full license text must always be included exactly as provided. Author names are not subject to machine translation.
• Translations are provided as a supplementary aid, with the original text taking precedence. The tool includes instructions to consult the original text for the official and most up-to-date information.
• We guide users to verify issues using the original (untranslated) text to prevent inquiries regarding translation errors from being directed to the plugin authors.

■ Features
This tool aggregates and searches for free plugins published under the MIT License on GitHub, presenting them in a readable format across 12 languages.

The supported languages are: Japanese, English, Simplified Chinese, Traditional Chinese, Korean, German, Spanish, French, Italian, Polish, Portuguese, and Russian.

■ Mechanism and Inclusion Criteria

Inclusion Criteria: Plugins published in public GitHub repositories under the MIT License that include standard RPG Maker plugin descriptions (such as @plugindesc).

Current Catalog: We currently include 89 MV/MZ plugins published under the MIT License, with the catalog automatically updated daily.

Data Acquisition: We do not redistribute the plugin files themselves. The plugins are fetched directly from GitHub or jsDelivr at runtime, and the application only retains the index.

■ How to Use
An operation guide will appear upon the first launch.

Please make use of it.
You can also access the guide at any time via Help > Operation Guide.

■ Precautions
Depending on your environment, downloaded plugins may be blocked by security software. Please check your security software and OS settings.

On Windows, you can unblock the file by right-clicking the file, selecting Properties, going to the General tab, and checking the “Unblock” box under the Security section.

We hope this tool proves helpful to plugin authors and game creators alike.

[DarkPlasma]

@ggg_kuroda

Plugins published in public GitHub repositories under the MIT license, featuring standard RPG Maker description text (such as @plugindesc).

By default, does this tool scan only the default branch (or the main/master branch)?

If a repository is managed such that the default branch is used for development and MIT-licensed plugins are published via a release branch, will the tool be unable to find them?

[ggg_kuroda]

Thank you for your feedback.
We will improve the tool to support the release branch as well.
Please wait a little longer.

Also, thank you for always releasing your plugin.
We would like to take this opportunity to express our gratitude.

[Undermax]

Hi @ggg_kuroda

The idea is good, but I think you should also include developers like me, who offer plugins with other types of licenses, especially who are verified by you and are part of the Official RPG Maker DLC program.

[ggg_kuroda]

Thank you for your patience. Today, we improved the tool and confirmed that it now appears in search results, GitHub links open correctly, and plugins can be downloaded.

We look forward to your continued support.

[ggg_kuroda]

@Undermax Thank you for your suggestion. We also appreciate your ongoing cooperation as an official DLC creator.

Your points are well taken. Plugin Finder currently targets plugins licensed under the MIT license, as the tool’s nature involves downloading and exporting plugin files, which clearly permits redistribution. We also recognize as an issue that excellent plugins outside the MIT license are excluded.

Since we are still in the early stages of distribution, we will make adjustments while listening to users’ feedback.
Thank you very much for your valuable opinion.

We are also glad that you quickly posted a thread introducing the plugin list.
We look forward to your continued support.

[yuwaka]

Hello,

It would be greatly appreciated if you could create a link to Plugin Finder in an easily noticeable place, such as the sidebar.
This would also serve as a good introduction for those who are not yet aware of Plugin Finder.

Since opening Plugin Finder directly might leave users unsure of how to use it (especially those who want to register),

I think linking to this topic would be a better approach.

Thank you for considering this suggestion.

[BishoujoHelper]

Unfortunately, the blind “it has the MIT License file” constraint also can be abused or fail.

For example, when I went looking for a plugin that I did a Github commit for, I only found the plugin’s author listed for 2 of their 57 MV plugins. And that’s because somebody forked them and gave those 2 branches the MIT License, while the original repository has nothing besides a link to a blog with a pretty standard “non-commercial or commercial games is fine with credit, commercial I want credit and notification” kind of “Terms of Use”.

So, great idea, but it only works in a perfect world where everyone follows the rules and stays on top of their Github forever.

[ggg_kuroda]

Thank you for your continued support and for your wonderful proposal.

I believe we can improve the usage instructions by referencing this thread and the tutorial shown during the app’s first launch.

Regarding the visibility of the linking method, I would like to explore whether we can provide an alternative that is easier to access than a direct link.

Thank you as always for sharing your work.
I would like to take this opportunity to express my sincere gratitude.

[panda]

This is my first post here. Thank you for your kind attention.

I have a question and a request regarding the relationship between the language settings in Plugin Finder and the language specification in documentation.

In plugin help comments, it is possible to provide help in multiple languages by appending a language code, such as /*:ja. My plugins are basically documented in three languages: English (no language specification), Japanese (ja), and Korean (ko).

However, when I search for my own plugin in Plugin Finder, even though the application language is set to Japanese, the plugindesc content displayed in the search results appears to be in English (no language specification).

If this is the current behavior, it would be greatly appreciated if the search results could prioritize displaying documentation that corresponds to the application’s language settings.

Even for plugins that support multiple languages, only the English description is shown in the search results. As a result, users may mistakenly believe that the plugin only has English documentation available.

On the other hand, regarding the translation function, it seems to correctly retrieve help content matching the set language. However, when Japanese is translated into Japanese, it results in nonsensical text.

I hope that, similar to the translation function, the search results will also display the plugindesc corresponding to the application’s language settings.

[ggg_kuroda]

Hello, Panda. Thank you for your report.

As you pointed out, the current search results are designed to display the “plugindesc” block with no language specified (or the English block). This is because the Plugin Finder catalog stores only one description per plugin, which is retrieved from the “no language specified (or :en)” block during catalog generation.

Even if the app’s display language is set to Japanese, this description will still appear in English. As you correctly noted, this makes it seem as though multi-language plugins only have English available, which is an issue that needs improvement.

On the other hand, the translation function fetches the plugin itself again and parses the block corresponding to the set language, so it correctly retrieves the Japanese help content. The issue of “translating Japanese into Japanese” occurs because both the automatic detection of the source text and the default value for the translation target are set to Japanese; we plan to review this as well.

As a solution, we are considering storing the plugindesc for each language in the catalog and prioritizing the description matching the app’s settings in search results (falling back to English, then Japanese, if unavailable). Since this requires an update to the catalog system, it will take some time to implement. We will announce it as soon as it is ready. Thank you very much for your valuable feedback.