Bobstah's Enhanced Equipment, Item, Items Command, Skill, and Skill Type Restrictions 1.5.3

Bobstah · 2015-11-04T06:32:06+0900

Updated 08/03/2016 09:21 PM ET Introduction Allows you to restrict equipment, items, the items battle command, skills, and skill types by actor ID, class ID, stat (hp, mp, tp, mhp, atk, cri, pdr, etc) minimum value, stat maximum value, other weapon equipped, other armor equipped, switch on/off, variable minimum value, variable maximum value, and a custom Eval option. asdf Every set of Restrict tags counts as a group. You can have multiple groups per equipment or item, and the actor only needs to satisfy the conditions of one restriction group to wear the equipment or use the item. Daisy-chaining gear is also accounted for and prevented. Every tag can also be inverted and eval'd for your convenience. Features Restrict equipment and item usage based on a multitude of factors! Restrict some global properties, like Skill Types, using all of the restrictions available to items, skill, weapons, and armor! Set multiple restriction groups on a single item. If one of the groups' restrictions is met, the item can be equipped! Request the opposite of any setting! Instead of equipment being limited to Actor #1, it can be any actor except Actor #1! Just prefix your restriction with an ! Eval any ID, Variable, or Switch value by surrounding it with $()! Use a custom Eval command to check for a true or false result! How to Use Add the plugin in your game and view the help information. It describes the notetags and all the crazy modifiers you can use. See the examples section for more information. Notetags Spoiler Spoiler A group of restrictions is contained between the tags. You can have more than one group of restrictions per equip or item, and the actor only has to meet one set of restrictions. If you want multiple restrictions to be met, use a single group instead. If desired, you can prefix any Restriction with an !. This will cause it to check the opposite of what you specify. If you use it with Actor: 1, for example, anyone but Actor 1 can equip the item. You can also replace anything after : with Javascript code inside of $(), like so: Actor: $(yourFunction() You can even combine the two: !Actor: $(yourFunction() Below are all of the available options: LevelMin: X - Minimum level. LevelMax: X - Maximum level. Class: ID - Actor must be class ID. Actor: ID - Actor must be this ID. State: ID - Actor must have state ID applied. Weapon: ID - Actor must be wearing this weapon. Armor: ID - Actor must be wearing this armor. StatMin(Symbol): X - Stat Symbol must be at least X. StatMax(Symbol): X - Stat Symbol must be at most X. Switch(ID): On/Off - Switch ID must be on/off. VarMin(ID): X - Variable ID must be at least X. VarMax(ID): X - Variable ID must be at most X. Custom: $(codeHere) - Run some Javascript. To restrict a global property, like a Skill Type, add the following to any actor's note field: LevelMin: X - Minimum level. LevelMax: X - Maximum level. Class: ID - Actor must be class ID. Actor: ID - Actor must be this ID. State: ID - Actor must have state ID applied. Weapon: ID - Actor must be wearing this weapon. Armor: ID - Actor must be wearing this armor. StatMin(Symbol): X - Stat Symbol must be at least X. StatMax(Symbol): X - Stat Symbol must be at most X. Switch(ID): On/Off - Switch ID must be on/off. VarMin(ID): X - Variable ID must be at least X. VarMax(ID): X - Variable ID must be at most X. Custom: $(codeHere) - Run some Javascript. You can also restrict the Items battle command by using and any of the above options. For more information on eval, check the plugin's help documentation. Examples Spoiler Let's make an Evil Sword that anyone but our Paladin, Actor#1, can equip: !Actor: 1 Next, let's make a potion that someone can only use at level 5, 6, 7, 8, 9, and 10: LevelMin: 5 LevelMax: 10 Let's build on that and say that only Actor#3 can equip a piece of armor whenever they want, but other actors can only wear it between levels 5 and 10: actor: 3 LevelMin: 5 LevelMax: 10 Building on that even more, let's go all out. The following example will allow any class but class#1 to equip it as long as their atk is at least 5, variable#6 is at least 10, and switch#4 is turned off. Or, they can be actor#3: !Class: 1 StatMin(Atk): 5 VariableMin(6): 10 Switch(4): off Actor: 3 Next, we'll check to see if an actor has state#3 using the eval feature: Custom: ($a._states.indexOf(3) !== -1 What if we want to restrict a skill to actors that have less than 50% HP? StatMax(hp):$(a.mhp * 0.5) What about restricting a skill to actors that have more than 50% HP? StatMin(hp):$(a.mhp * 0.5) You can do the same thing with MP and TP, too. If you want to change the percentages, modify 0.5 (50%) to any other number. For example, 23% is 0.23.<…

● ARCHIVED · READ-ONLY

Started by Bobstah Nov 3, 2015, 09:32 PM 85 posts Page 2 of 5 View original ↗

snorlord

#21 Nov 6, 2015, 09:05 PM Source

I noticed that when using two groups with the same state condition type for a skill, it seems like only one group is checked.

<Restrict>State: 11</Restrict><Restrict>State: 12</Restrict>In the enclosed case, only State 12 seems to count as a restriction. When State 11 is applied, the skill remains restricted instead of being active.
Naffington

#22 Nov 6, 2015, 10:14 PM Source

What does "Error:object too deep" mean?

I was making a skill that required state 45 to use.

It gives the the error when the actor got the state and I open the skill menu during battle.

<Restrict>

State: 45

</Restrict>

The only plugin that has to do with skills is Yanfly Skill Core, Instant Cast, and Cooldowns. But I turn them off and still get the error.

Also tried.

<Restrict>

Custom: ($a.states().indexOf(45) !== -1;)

</Restrict>

Gave me the same error.
Bobstah

#23 Nov 6, 2015, 10:31 PM Source

snorlord said:
I noticed that when using two groups with the same state condition type for a skill, it seems like only one group is checked.

Naffington said:
What does "Error:object too deep" mean?

I was making a skill that required state 45 to use.

It gives the the error when the actor got the state and I open the skill menu during battle.
I'm looking into these problems now. Thanks for letting me know!
Bobstah

#24 Nov 6, 2015, 11:24 PM Source

snorlord said:
I noticed that when using two groups with the same state condition type for a skill, it seems like only one group is checked.

<Restrict>State: 11</Restrict><Restrict>State: 12</Restrict>In the enclosed case, only State 12 seems to count as a restriction. When State 11 is applied, the skill remains restricted instead of being active.
I copied your exact setup and was unable to duplicate the problem. Did you determine if another state, weapon, armor, or trait is restricting this skill? My plugin checks the built-in functionality first. If that succeeds, it continues on to the Enhanced Restrictions. If it isn't any of those, I'll PM you a debugging copy of the plugin you can use to help me determine exactly what is happening.

Just to clarify, if one set of restrictions is met, it considers all restrictions good. This is by design to allow you to create restriction groups. Logically, each group is separated by an OR operator, so If Group1 === true OR Group2 === true, etc.

Naffington said:
What does "Error:object too deep" mean?

I was making a skill that required state 45 to use.

It gives the the error when the actor got the state and I open the skill menu during battle.

Gave me the same error.
I could not duplicate this problem either using all of the plugins you have except Yanfly's Instant Cast. Can you tell me if the "Error: Object too deep" error message contains anything about JsonEx if you press F8 on your keyboard and look inside the window that opens up?
HeroicJay

#25 Nov 6, 2015, 11:30 PM Source

When I was looking for a solution to shared costs in my dualtech script, I suggested using something exactly like this to block the skill if the shared cost isn't met (since checking each cost individually, which works fine for individual costs like MP and TP, doesn't work so well when the cost is shared, like inventory items.) I hadn't implemented it, because a. I wanted to focus on other things at the time, and b. I was sure someone must have made one.
Naffington

#26 Nov 6, 2015, 11:35 PM Source

Bobstah said:
I could not duplicate this problem either using all of the plugins you have except Yanfly's Instant Cast. Can you tell me if the "Error: Object too deep" error message contains anything about JsonEx if you press F8 on your keyboard and look inside the window that opens up?

I have located the plug in that's causing the problem. It is Ellye's State Damage

http://forums.rpgmakerweb.com/index.php?/topic/48631-ellyes-state-damage/

It works fine when I have that plug in turned off.

Is it possible to make it compatible?
Bobstah

#27 Nov 7, 2015, 12:46 AM Source

Version 1.3.2 is now available! Fixed an issue with armor restrictions and added Ellye State Damage compatibility! Download

Naffington said:
I have located the plug in that's causing the problem. It is Ellye's State Damage

http://forums.rpgmakerweb.com/index.php?/topic/48631-ellyes-state-damage/

Is it possible to make it compatible?
Yep! :)
Naffington

#28 Nov 7, 2015, 01:35 AM Source

Bobstah said:
Version 1.3.2 is now available! Fixed an issue with armor restrictions and added Ellye State Damage compatibility! Download

Yep! :)
I updated it to 1.3.2 and it still gives me the same Object too deep error with the same JsonEx error. when I turn on Ellye State Damage.

I also tried placing Ellye under this script and then saved and it still didn't work.

Do you think there are other things in Ellye State Damage plug in that's causing this?

Also, the new update made another error if Ellye State Damage is turned off and to only way to make it work is to delete Ellye State Damage entirely from plug in manager.

So I have to choose between TypeError or Object too deep error.
Bobstah

#29 Nov 7, 2015, 12:06 PM Source

Version 1.3.3 is now available! Fixed a crash bug that would occur if Ellye's State Damage was disabled in the Plugin Manager. Download

Naffington said:
I updated it to 1.3.2 and it still gives me the same Object too deep error with the same JsonEx error. when I turn on Ellye State Damage.

I also tried placing Ellye under this script and then saved and it still didn't work.

Also, the new update made another error if Ellye State Damage is turned off and to only way to make it work is to delete Ellye State Damage entirely from plug in manager.
I was able to fix the issue where if Ellye's State Damage is turned off, the game would crash. Apparently RPG Maker MV still loads plugin variables even if a plugin is disabled. That's fun.

As to your other problem, I was unable to replicate it in an entirely new project containing only my Enhanced Restrictions and Ellye's State Damage. I tried both with Ellye's first and Enhanced Restrictions first.

Maybe try downloading the latest version of Enhanced Restrictions and also Ellye's Damaging States to see if it helps.
Bobstah

#30 Nov 7, 2015, 02:33 PM Source

Version 1.3.3a is available! Fixed another bug related to Ellye's State Damage. Download

I found another bug that would cause my patch to not restore Ellye's functionality. That has now been corrected.

(As an aside, I had a state with Ellye's damage tags on it and when I went to unequip some armor for another plugin I am testing, the game crashed. This happens in the base equipment scene, so there isn't any way I can fix this via this plugin. )
Naffington

#31 Nov 8, 2015, 01:05 AM Source

Thank you, too deep error seems to be gone and is now working after 1.3.3a!
Bobstah

#32 Nov 8, 2015, 05:28 AM Source

Naffington said:
Thank you, too deep error seems to be gone and is now working after 1.3.3a!
Glad to hear it. If you have any other issues, please let me know!
Bobstah

#33 Nov 9, 2015, 06:59 PM Source

Version 1.4 is now available! The first global restriction, SType, has been added! Download

This was made as requested by user DadaKen in my Battle Command List thread. You can now place this notetag inside of any actor to globally restrict skill types:

<Restrict SType: 1>

StatMin(tp): 100

</Restrict>

This will prevent someone from using Skill Type 1 unless the actor/enemy has 100 TP.
gambitben

#34 Nov 10, 2015, 01:48 PM Source

How could I restric a skill for actor 1 if actor 3 has X state?

Also, amazing plugin ^^
Bobstah

#35 Nov 10, 2015, 01:57 PM Source

gambitben said:
How could I restric a skill for actor 1 if actor 3 has X state?

Also, amazing plugin ^^
If this skill is only for Actor 1 and they can only use this if Actor 3 has state X:

<Restrict>

Actor:1

Custom: $($gameActors.actor(3)._states.indexOf(X) !== -1)

</Restrict>

If this skill can be used by any actor as long as Actor 3 has state X:

<Restrict>

Custom: $($gameActors.actor(3)._states.indexOf(X) !== -1)

</Restrict>

If this skill is only for Actor 1 and they can only use this if Actor 3 does not have state X:

<Restrict>

Actor:1

Custom: $($gameActors.actor(3)._states.indexOf(X) === -1)

</Restrict>

If this skill can be used by any actor as long as Actor 3 does not have state X:

<Restrict>

Custom: $($gameActors.actor(3)._states.indexOf(X) === -1)

</Restrict>

If this skill can be used by other actors without this limitation, only Actor one is limited:

<Restrict>

Actor: 1

Custom: $($gameActors.actor(3)._states.indexOf(X) !== -1)

</Restrict>

<Restrict>

!Actor: 1

</Restrict>

Does this answer your question?
Radis3D

#36 Nov 11, 2015, 08:23 AM Source

help me please.. what happen? :'(

before use this update, it's work well.. :'(
Bobstah

#37 Nov 11, 2015, 09:38 AM Source

Radis3D said:
help me please.. what happen? :'(

before use this update, it's work well.. :'(
Looks like a skill type of 0 is somehow making it through to the method where I check to see if a battler can use a skill type.

I'll have a fix out for this later this morning. Thanks for your patience! :)
Bobstah

#38 Nov 11, 2015, 12:58 PM Source

Version 1.4.1 is now available! Fixed a crash bug that would occur if you did not restrict any skill types. Download

Radis3D said:
help me please.. what happen? :'(

before use this update, it's work well.. :'(
I've fixed this bug. Thank you for reporting it!
Radis3D

#39 Nov 11, 2015, 04:26 PM Source

thank you for answering (replying)

i'll update my script later.. :)
an thank you for fixing :3
Pharonix

#40 Nov 11, 2015, 05:09 PM Source

Holy crap, this is so much better than the one I've been working on ... I'm a bit jealous