Skip to main content

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

Dualtechs for RPG Maker MV and MZ

Let your actors combine their skills in RPG Maker MV and MZ · By HeroicJay

Feature Request: Ignore Skills from Trait (RMMZ)

A topic by Puppet Knight created May 03, 2023 Views: 161 Replies: 4
Viewing posts 1 to 2
(2 edits)

Hey Jay!

Loving this plugin SO much right now. I wanted to see how hard it would be to implement  an additional plugin parameter. 

In my project Actors master skills through use. The skills are assigned to specific equipment as traits and the Actors can only use the skills while they have those items equipped until they have permanently learned the skill. 

As such, if any member of a dual tech has actually learned the dual tech skill, they are able use it in battle even if all members of the tech haven't yet mastered the skill, but do have the a traited equipment. 


Would it be possible to add true/false boolean as a plugin parameter along the lines of:

Skills must be learned to be counted for Dual Tech?

with the default being false for common users //actor.hasSkill() //, 

and true making it so that skills added from traits don't allow dual tech use? so Skill must be learned by the Actor //actor.isLearnedSkill()

Developer

I was mulling this one over for the last day, as I'm not sure how many people would use this feature. Eh, I can easily do it, but I think the best way would be a developer-definable symbol in front of the skill. Let's say it's an exclamation point. For example: if the skill has actor 1 use Slice and actor 2 use Dice, and you want the dualtech to only work if the skills have been permanently learned, you'd write <Dual:1,!Slice,2,!Dice>. (And you can change that symbol to something else in case you're actually using exclamation points at the beginning of skill names.) Thoughts?

I actually love this. It's even more flexible than my original request which is perfect for other users and saves you building out plugin parameters. Win-Win.

If this isn't difficult to implement, I'd say go for it. To confirm, the idea would be that this should also work with skillIds, right?

So  <Dual:1,!99,2,!100>

Would also be valid with this feature?

Developer

That's the plan.

Developer (1 edit)

And done. Like I said, wasn't hard. As I say in the Devlog, once you update, please open the Permanent Skill Prefix parameter and press "OK" once, even if an exclamation point is fine, or the system might have trouble with the new parameter.