Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(3 edits)

The advantages for such said team, would be:

1. Trying the kit while it's on development.

2. Each member gets one individual key for it, for the full version of the kit on release of the kit or the game

3. If the game works well, the chances to work together again in another project, making them capable of building some saga.

4. They will also have direct contact with me while in development, so I'll get their feedback and customizations to the kit and some open source or higher codes.

5. I'll also be able to make some custom plugins for the team, besides the kit itself.


Now, as for the difficulties of having me in the team:

1. RPG Maker games are extremely underrated, because all things are quite "defaultish", so I won't accept "just another" rpg maker game, I must consider there will be real quality, and that it keeps growing properly through the development. I don't care if it takes for a long time.

2. The level designer or head developer, will have to show me they do know their way around RPG Maker MZ, by showing me some stuff they made, even if it was on previous PC iterations of RPG Maker.

3. My most important benefit from the agreement, would be advertising. The kit must be important in the game. If it's not a free game, I'll ask for a bit of economic compensation in proportion to sales, but, the main requisite is to have, not only me, but rather the kit, announced in the credits. Yes, this implies there must be a credits scene. I can make it if you need.

4. I cannot read nor modify closed source code, I can veto such plugins from the project.

5. I'm not good with visual plugins, too much redundancy in the code to make them run properly, these will take for long to be done.