VisuStella MZ Terms of Use Article 7 - Revision history

Yanfly at 00:46, 21 March 2022

2022-03-21T00:46:13Z

Yanfly at 11:22, 6 October 2020

2020-10-06T11:22:12Z

Yanfly: Created page with "{| style="width: 800px;" cellspacing="0" cellpadding="0" | style="width: 100%; vertical-align: top;" | {{VisuStella MZ Terms of Use}}
Listed above are Visustella|V..."

2020-10-06T11:13:57Z

Created page with "{| style="width: 800px;" cellspacing="0" cellpadding="0" | style="width: 100%; vertical-align: top;" | {{VisuStella MZ Terms of Use}} <hr> Listed above are Visustella|V..."

New page

{| style="width: 800px;" cellspacing="0" cellpadding="0"
| style="width: 100%; vertical-align: top;" |

{{VisuStella MZ Terms of Use}}

<hr>

Listed above are [[Visustella|VisuStella]]'s Terms of Use.

Let us explain about the requirement for all team members to own a copy of the plugin is required for Article 7.

Let's also address the concerns for it.

<hr>

In case it's not clear, redistributing plugins to team members who do not own the plugins themselves is a direct violation of article 4, which states that you may NOT redistribute these plugins nor take code from this plugin to use as your own.

Team members are not excluded from this article.

<hr>

So why is there no exclusion clause for this?

Because if there is an exclusion clause for this, then that's all it takes for one loop hole to be made for everybody in a small community to suddenly become owners. All that would need to be done is for one small community, or even the RPG Maker community, to "work" on one game together for the rights to be redistributed and exploit our terms of use.

Furthermore, this is a standard in any kind of industry using a particular software. In a work company, any business license requires each and every individual work computer for thta company to own a unique copy of said license if they want to use a specific software.

<hr>

There are concerns about these plugins becoming too expensive if there are multiple members on the team.

We're sorry to hear that, especially if it's outside of your budget.

However, if you are assembling a team for the development of your game, we strongly recommend that you recruit a dedicated programmer as a team member and have the programmer develop the features you need. Considering that this is the field of game dev you're in, forming a game dev team without a dedicated programmer is nearly unheard of.

If you can neither afford paying for each team member or a dedicated programmer, there are also free plugins out there provided by various members of the RPG Maker community. The VisuStella MZ library is not the only option available.

If there are no free plugins of the features you want available, try commissions. Commission a programmer with terms that match and allow for your team members to own the rights to use their work while having the features you need.

There are always options available.

<hr>

|}

← Older revision		Revision as of 00:46, 21 March 2022
Line 34:		Line 34:
	Because if there is an exclusion clause for this, then that's all it takes for one loop hole to be made for everybody in a small community to suddenly become owners. All that would need to be done is for one small community, or even the RPG Maker community, to "work" on one game together for the rights to be redistributed and exploit our terms of use.		Because if there is an exclusion clause for this, then that's all it takes for one loop hole to be made for everybody in a small community to suddenly become owners. All that would need to be done is for one small community, or even the RPG Maker community, to "work" on one game together for the rights to be redistributed and exploit our terms of use.

−	Furthermore, this is a standard in any kind of industry using a particular software. In a work company, any business license requires each and every individual work computer for ~~thta~~ company to own a unique copy of said license if they want to use a specific software.	+	Furthermore, this is a standard in any kind of industry using a particular software. In a work company, any business license requires each and every individual work computer for that company to own a unique copy of said license if they want to use a specific software.

@@ Line 13: / Line 13: @@
 Let's also address the concerns for it.
 <hr>
 In case it's not clear, redistributing plugins to team members who do not own the plugins themselves is a direct violation of article 4, which states that you may NOT redistribute these plugins nor take code from this plugin to use as your own.
 Team members are not excluded from this article.
 <hr>
 So why is there no exclusion clause for this?
@@ Line 27: / Line 35: @@
 Furthermore, this is a standard in any kind of industry using a particular software. In a work company, any business license requires each and every individual work computer for thta company to own a unique copy of said license if they want to use a specific software.
 <hr>
 There are concerns about these plugins becoming too expensive if there are multiple members on the team.
@@ Line 41: / Line 53: @@
 There are always options available.
 <hr>
 |}

VisuStella MZ Terms of Use Article 7 - Revision history

Yanfly at 00:46, 21 March 2022

Yanfly at 11:22, 6 October 2020

Yanfly: Created page with "{| style="width: 800px;" cellspacing="0" cellpadding="0" | style="width: 100%; vertical-align: top;" | {{VisuStella MZ Terms of Use}} Listed above are Visustella|V..."

Yanfly: Created page with "{| style="width: 800px;" cellspacing="0" cellpadding="0" | style="width: 100%; vertical-align: top;" | {{VisuStella MZ Terms of Use}}
Listed above are Visustella|V..."