Official plugins – terms of use?

RPG Maker Questions
1

I asked this on the RPGMakerWeb forums, but I never got a satisfactory response.

What are the terms of service for the official Kadokawa plugins bundled with MV and MZ?

  • Is it okay to make changes and distribute the changed versions? If so:
    • Can the changed version be distributed alone, or only as part of a game?
    • Is it okay to change the name of the plugin to differentiate it more from the original version?
  • Is it okay to port a plugin bundled with MV to MZ?
  • Is it okay to backport a plugin bundled with MZ to MV?
  • If the above are all okay, are there any conditions that need to be satisfied?

If they aren’t all under the same terms, that would be good to know too.

To be clear, this refers to all these plugins for MV:

Official MV Plugins

AltMenuScreen.js
AltSaveScreen.js
Community_Basic.js
EnemyBook.js
ItemBook.js
MadeWithMv.js
SimpleMsgSideView.js
TitleCommandPosition.js
WeaponSkill.js

AltMenuScreen2.js
AltMenuScreen3.js
BattlebackScroll.js
BattleResultsPopup.js
BattleVoice.js
ChangeWeaponOnBattle.js
ConfigureRootElement.js
DeadOrAliveItem.js
EscapeDungeon.js
EventSelector.js
ExtraEquipType.js
FixedBattleMembers.js
Foreground.js
HPConsumeSkill.js
KeyItemAlone.js
KeyItemNumber.js
LastSubjectActor.js
LastUsedItem.js
MenuSubMember.js
NewItemScene.js
NovelMessage.js
NumbState.js
OuterSelfSwitch.js
OverpassTile.js
PictureWipe.js
PlayMsgWndCharSE.js
SVActorPosition.js
SwitchOnLoad.js
TextDecoration.js
TinyGetInfoWnd.js
WindowChange.js

Gacha.js
GachaBook.js
NovelMessage.js
SlotMachine.js
TouchUI.js

Official MZ Plugins

AltMenuScreen.js
AltSaveScreen.js
ButtonPicture.js
TextPicture.js

AddAutoToActorCommand.js
AdjustPictureGraphical.js
AltMenuScreen2MZ.js
AnimationMv.js
BattleVoiceMZ.js
ChangeEquipOnBattleMZ.js
ChangeSelectItemWindowMZ.js
CommonMoveRouteMZ.js
DevToolsManage.js
EffekseerForRPGMakerMZ_Ex.js
EventEffects.js
EventMovableLimitation.js
EventReSpawn.js
Foreground.js
HPConsumeSkill.js
ItemCombinationMZ.js
ItemCombineScene.js
ItemNameMsg.js
Levelupstate.js
MenuSubMembersMZ.js
MessageWindowPopup.js
Minimum_encount.js
NoGameover.js
NoGameover2.js
Nostepacting.js
NovelMessageMZ.js
NumbState.js
OverpassTileEventAttach.js
OverpassTileVehicleAttach.js
PictureAnimation.js
PlayMsgWndCharSeMZ.js
PluginBaseFunction.js
ScreenZoom.js
SetFieldSkillIdMZ.js
ShakeOnDamage.js
ShakingChange.js
SimpleMsgSideViewMZ.js
SimplePassiveSkillMZ.js
SmartAutoBattle.js
SmoothTouchMove.js
StartTPBactorcommand.js
StartUpFullScreen.js
StateAutoBattle.js
SubMembersAttendBattle.js
SVActorPositionMZ.js
TemplateEvent.js
TinyGetInfoWndMZ.js
TouchMoveForSymbolEncount.js
wasdKeyMZ.js
WeatherOnBattle.js
Yami_8DirEx.js

TextScriptBase.js
CustomLogo.js
EventCommandByCode.js
ExtraImage.js
ExtraWindow.js
MaterialBase.js
OverpassTile.js
PluginCommonBase.js
RegionBase.js
UniqueDataLoader.js

Note that I’m explicitly excluding the additional RPGMakerWeb plugins distributed in the dlc folder for MV, as those mostly have clear terms in the file.

I found the official terms, but I can’t see anything there that answers the question. I might just be missing it, though.

2

Each plug-in does generally have its own terms.

However, the truly official ones (those developed by GGG) are all operated on the same license agreement governing RPG Maker itself unless otherwise specifically mentioned.

Just remember that not all DLC plug-ins for RPG Maker are made by GGG, so you do need to check who the developer is and what terms they have.

4 Likes
3

So, based on those terms, what would be the answers to my specific questions? Is it the same as resources (so posting edits is fine, and using MV plugins in MZ or vice versa with edits is fine too)? Or is it different?

I took a quick look at some of the plugins I listed, and it looks like some of them are by Triacontane and specify MIT license at the top of the file, and many others specify MIT license at the bottom of the help comment (I wish it was always at the top of the file), so clearly not all of them are under the default license agreement. Here’s a list of ones that don’t specify any license:

Official MV Plugins

In NewData/js/plugins
AltMenuScreen.js
AltSaveScreen.js
Community_Basic.js
EnemyBook.js
ItemBook.js
MadeWithMv.js
SimpleMsgSideView.js
TitleCommandPosition.js
WeaponSkill.js

In dlc/KadokawaPlugins
AltMenuScreen2.js
AltMenuScreen3.js
BattlebackScroll.js
BattleResultsPopup.js
BattleVoice.js
ChangeWeaponOnBattle.js
ConfigureRootElement.js
DeadOrAliveItem.js
EscapeDungeon.js
EventSelector.js
ExtraEquipType.js
FixedBattleMembers.js
HPConsumeSkill.js
KeyItemAlone.js
KeyItemNumber.js
LastSubjectActor.js
LastUsedItem.js
NewItemScene.js
NovelMessage.js
NumbState.js
OuterSelfSwitch.js
OverpassTile.js
PictureWipe.js
PlayMsgWndCharSE.js
SVActorPosition.js
SwitchOnLoad.js
TextDecoration.js
WindowChange.js

In dlc/KadokawaPlugins_New/js/plugins
Gacha.js
GachaBook.js
NovelMessage.js
SlotMachine.js
TouchUI.js

Official MZ Plugins

In newdata/js/plugins
AltMenuScreen.js
AltSaveScreen.js
ButtonPicture.js
TextPicture.js

In dlc/BasicResources/launch
Levelupstate.js
NoGameover.js
NoGameover2.js
Nostepacting.js
ShakingChange.js
StateAutoBattle.js

In dlc/BasicResources/official
TextScriptBase.js
CustomLogo.js
EventCommandByCode.js
ExtraImage.js
ExtraWindow.js
MaterialBase.js
OverpassTile.js
PluginCommonBase.js
RegionBase.js
UniqueDataLoader.js

I’m assuming all of those are governed by the RPGMaker license. Does that mean the answer to all my “is it okay” questions is “yes” for these plugins?

4

Thank you for your question, and I apologize if my previous answer left specific details unclear.

First, as a general principle, the license notice for each individual plugin takes precedence.
If a license is stated within a file, that license applies and takes priority.
Although some might assume they are “default” licenses, MIT-licensed files are actually mixed in (for example, those by Triacontane).
If a file is MIT-licensed, you are free to modify, rename, distribute it separately, or port it between MV and MZ. The condition is that you must retain the MIT copyright notice and the full license text as is.

The Terms of Use for RPG Maker apply only to files that do not have their own license. This refers to the “Add-on Usage Terms” in the Supplementary Provisions of the GGG Product Usage Terms.
“Add-on” refers to plugins, and those bundled by our company are considered “Official Add-ons.”

[Supplementary Provisions] Add-on Terms and Conditions

Based on the above, I will answer each of your questions regarding plugins without license notices, in accordance with the Add-on Usage Terms.

・Can I modify it and distribute the modified version?
Modification is permitted (Add-on Usage Terms, Article 1(B): Official Add-ons may be modified solely for the purpose of use in games). Distribution is also permitted, but only in the following bundled format.

・Can it be distributed standalone, or only as part of a game?
It can only be distributed as part of a game. Article 1(C) permits distribution “only when distributed together with games created using our products,” and Article 3 stipulates that both Official Add-ons and modified versions “must not be distributed independently.”
This is the only point where the treatment differs from assets. Images, audio, and other assets can be distributed on your own website or portfolio for free to other legitimate users (Asset Usage Terms). Plugins do not have this privilege. Official plugins without license notices, whether modified or not, can only be distributed “bundled with a game” and cannot be provided as standalone downloads. (In practice, this rarely causes issues, as anyone with the engine already possesses these files from the start. This restriction is primarily intended to prevent distributing engine-bundled code to those who do not own the engine.)

・Can I rename it to distinguish it from the original?
There is no problem. Renaming is merely a form of modification already permitted, so it is acceptable.
There are two points to note: the rule above regarding “distribution only when bundled with a game” still applies, and you should avoid presenting it in a way that implies it was created or recommended by our company (GGG).

・Is it possible to port from MV to MZ, or backport from MZ to MV?
Both are permitted. The conditions are that you must legitimately own the relevant products (you must own the source engine to use the add-on, and you also need the destination engine to create a game into which the add-on is integrated), and the same “distribution only when bundled with a game” rule applies to the result.

2 Likes
5

Thanks for the clarification, both on the details and on the fact that “add-on” in your terms document refers to plugins.

One last question. Does a demo project (essentially, a non-deployed game that includes the project file but does not include the nwjs runtime) count as a “game” for the purpose of these terms? Or is distributing modified versions in that way not permitted?

1 Like
6

Thank you for your question.

Demo projects are also included in the definition of “games.”

The Add-on Usage Terms require that you distribute the plugin “alongside user games created with RPG Maker” and that you do not distribute it “on its own.”
Furthermore, “user games (user software)” are not required to be “deployed/packaged games.”
Therefore, including and distributing modified official plugins within a demo project does not constitute “distribution on its own” and is not a problem.

However, there are two points to keep in mind.

  1. It must be a substantive project.
    If the “demo project” is essentially an empty project containing only the modified plugin, it would be considered a standalone distribution disguised under a different name, violating the condition that it must not be “distributed on its own.”
    As long as the project actually demonstrates the plugin’s functionality, it is fine.

  2. Be cautious about included assets.
    While including the plugin itself is fine, please adhere to the rules of the assets included in the project. (Depending on the DLC, we have seen cases that require additional credits or encryption.)

Improving plugins or creating demos to showcase their features and sharing them are wonderful activities that help other developers make the most of RPG Maker.
We certainly do not wish to suppress such efforts.
Therefore, we ask that you be careful to ensure that you do not violate the rules mentioned above.

1 Like
7

Thank you for the clarification! My demo certainly showcases my plugin’s functionality, so it should be fine on point 1; and it only contains RTP sounds and graphics, no paid DLCs, so it should be fine on point 2.

1 Like