itch.io

I updated this plugin's version for the time being, which besides an option to add as you create it, includes a couple of bugs that could potentially crash your testplay.

Didn't see the crash you reported, I'll keep looking for it, but it would help a lot if you sent me a log report, like the one you sent with VisuStella plugins on.

Since we didn't get to a specific solution, I begun to make the simplifier plugin. I'd say I'm nearly 80% done. It would let you run the commands from the other two (and other related if I make them), without having to manage the data manually, other than the actorId you want to create or delete.

I can't help with Visustella scripts, since they are closed code and all. Most of plugins that don't belong to their suite are incompatible with a project with any of their plugins, as far as I know (rpg maker web forums is flooded in people answering that). As for running it without other plugins, did you add ME_CopyActors somewhere above it, or ran it on its own? (It's an extension for CopyActors, it won't work if it's not there).

Also, could you show me the trace error log of running it without Visustella suite?  And just in case, the corescript version (Game > Update Corescript)?

So, what you want to skip is, the green arrow, and the yellow arrow is an optional thing. That limits the plugin, and even more the control you as the developer have over the instances. You may need a party management plugin with such a change, too.

I need to think of how can I tackle this so it won't be just a limiter for simplification purposes.
Besides, doing this properly would require removing some corescript dependencies CopyActor has, and it will require through testing, but that might make it not compatible with a load of other plugins. I'll start the design phase and tell you if it would require a commission, if what I said is what you are looking for!
[Edit] Oh, I can also simply make a "limiter" extension plugin instead. It would take a lot less work (From a few months to a couple of weeks at most). Only, it would limit the actors to the free spots you can set on your game, whereas the original ones can bypass it with shenanigans. Would that be better?

If you want me to show you around the demo for doubts, we can also agree on a time/date to meet on qTox, Skype or Discord, if it helps, too.

I don't entirely understand what are you asking for, that's the issue. In summary what I understand is:
"I want the ability to add the generated actor immediately to party, instead of running a script call or manually checking variables".

If it's just that, you don't need to comission it, I can just make an update, no need to pay, to both plugins to add a parameter.
If what you want is to place the generated actor in one specific spot in party, it might take a bit  more of work which would require a later update or a commission (since it's not visual, I wouldn't ask for so much either!), since I would have to make a not so generic plugin, being your choice if to make it "replace" the actor sitting there, or move the later one spot later.

But I'm not 100% certain if adding the actor directly to party with the plugin command is what you are asking for, I just wanted to make sure, before starting to work in one direction or another!

When I designed the plugin, I had considered it would be way more intuitive for users to track the slots on their own with editor variables, rather than having an abstract array most of non-programmer developers might be confused about how it work. Besides, there's times when you generate a copy or instance at some point, and only add it long after that.

But I can work something out, like adding an optional parameter to the generation commands to immediately add the generated actor, if that covers the need you ask for. Would it work for you?

I generally make my plugins so that behaviour is possible, but it seems as it's one of my earliest plugins, I didn't take that approach.

That doesn't meant it cannot be done, but instead of using the plugin commands, you have to go to the function.

I'll update this now I know, but for the time being, you have to use the script calls instead.

Let's say you want to copy the entire actor you set on variable 3 into the actor you set in variable 7:

$gameActors($gameVariables.value(7)).copyActor($gameVariables.value(3));

You can replace $gameVariables.value(x) for literal numbers if you want to use the literal id instead of the variable.

[Edit]

Alright, updated it, now you can use any string with a number as "use a variable instead", like for example,  variable10, or 10v will both go and check whatever editor variable contains and use it!

So, what do you think?

Should I make a game? Should I make a team? Or is there any volunteering teams brave enough to have me and my kit join?

If I make the team myself, some stuff will be added to the earlier post.

1. Any resources in the game may be included in the kit with the kit's official terms. You will get credits in the kit, should this happen.
2. Not only the head developer will be put to test, but every single member of the team will be scrutinized.
3. Indie teams are unofficially up to 5 members, so will a team I make have.
4. Game will be paid. After publishing  & advertising expenses, all team members will get paid an equal proportion.
5. The game will be good, even if it takes for one more month or two to be released.
6. The game must be advertised while it's under development and for some time after release. I don't have much knowledge on how to do this.

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.

I'm considering a game based of this, so I can put myself better on the needs of the users. This will make me quite more clear my current and future goals, and possible future add-ons for this kit of plugins.

If I do this, I do really need help. No, I don't mean the scripting or pluging making part, but the actual workings of the game, resources level editing... and so on.

I'm considering this so much that I might actually let some team to become an "official team", for this goal, as long as we agree to some terms. I'd be basically their head scripter, but story, characters, plot, and all the rest would be all on their own. The monetization model (even if it's free), would depend on them. I can also help with story and characterization, or properly exporting to mobile, if it was required, but I don't want the proper role.

I consider three options:

- Stay as I am
- Interview volunteer teams to work with
- Make my own team

Honestly, I use most of them, but I only tested it on the 1.0.1 version of MV. The lastest in this site for the plugin.

Still, if instead of launching it from rpg maker I set it on htdocs and play it from there, the console says the same and the game goes alike.

Uncaught SyntaxError: Unexpected token => [PROJECT'S PATH]/js/plugins/FELSKI_TECHTREE.js:4422

Past that crash, for example the demo, works just like vanilla MV with Yanfly's plugins.