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 3 of 5 View original ↗

Bobstah

#41 Nov 11, 2015, 11:22 PM Source

Pharonix said:
Holy crap, this is so much better than the one I've been working on ... I'm a bit jealous
Keep at it, you never know when someone wants something more focused than my omnibus of a plugin. :)

If you need/want any help with yours, feel free to reach out to me and I'll assist however I can. :)
Aluvien

#42 Nov 12, 2015, 08:05 PM Source

This addon looks really great; I'm just running into one issue when I use it. Whenever I try to go to the Equip window, I get the error "Cannot read property 'canEquipEnhanced' of null". This is in a completely new project. I saw what you said earlier about MV loading plugin variables even when they are turned off, so I removed all other plugins from the folder and still got the error. Here's the console info:

Thanks again for making this, I hope this was helpful.
EDIT: I should mention that this is with no notetags used at all. I just turned the plugin on.
snorlord

#43 Nov 13, 2015, 09:37 AM Source

When you put this script in a blank project with Yanfly's Equip Core, it seems to allow you to unequip all 'Non Removable Types' in the plugin parameters (although the Clear option in the equip menu still respects the settings).
Bobstah

#44 Nov 13, 2015, 09:45 AM Source

Aluvien said:
This addon looks really great; I'm just running into one issue when I use it. Whenever I try to go to the Equip window, I get the error "Cannot read property 'canEquipEnhanced' of null". This is in a completely new project. I saw what you said earlier about MV loading plugin variables even when they are turned off, so I removed all other plugins from the folder and still got the error. Here's the console info:

Thanks again for making this, I hope this was helpful.

EDIT: I should mention that this is with no notetags used at all. I just turned the plugin on.
Thank you for the detailed information I will look into this and release a fix as soon as I have it ready. No later than Monday. :)

snorlord said:
When you put this script in a blank project with Yanfly's Equip Core, it seems to allow you to unequip all 'Non Removable Types' in the plugin parameters (although the Clear option in the equip menu still respects the settings).
Thank you for the bug report! I'll release a fix for this as well.
gambitben

#45 Nov 14, 2015, 06:39 PM Source

Thank you so much! I couldn't answer earlier, but it did help me a lot :)

Keep up the AMAZING job you are doing with your awesome plugins BD
Bobstah

#46 Nov 19, 2015, 07:57 PM Source

Version 1.4.2 is now available! Fixed a crash bug that could occur when opening the equipment window. Download

@Aluvien: I believe I've fixed this bug. Sorry for the delay, Fallout 4 happened. :(

@snorlord: This update may have corrected your issue. If it didn't, can you take a picture of your plugin load order and send it to me so I can replicate it and test? Thanks! :)
AlexanderWii

#47 Nov 28, 2015, 03:05 AM Source

You can put the object visible but obviously not be equipped when there is a restriction instead of making it invisible?
Bobstah

#48 Nov 28, 2015, 07:28 AM Source

AlexanderWii said:
You can put the object visible but obviously not be equipped when there is a restriction instead of making it invisible?
Are you asking if I can make restricted items not show up if you cannot equip them?
Seleroan

#49 Dec 1, 2015, 06:12 PM Source

Just wanted to let you know that the "can use multiple restrictions but actor only needs to meet one" thing isn't working. Or at least, I'm not understanding how you meant it to be implemented.

<Restrict>

!Actor= 1

</Restrict>

<Restrict>

Actor= 1

Switch(21)= On

</Restrict>

When I do this, it should make so that anyone but actor 1 can use the item. However, once switch 21 is on, Actor 1 can also use the item.

But in practice, what happens is that only the second set of restrictions will work. So, currently, no one can use the item at all unless the switch is pulled. Then only Actor 1 can use it.

If I reverse the restriction order, anyone can use the item except actor 1 whether the switch is pulled or not.
Bobstah

#50 Dec 1, 2015, 10:01 PM Source

Seleroan said:
Just wanted to let you know that the "can use multiple restrictions but actor only needs to meet one" thing isn't working. Or at least, I'm not understanding how you meant it to be implemented.

<Restrict>

!Actor= 1

</Restrict>

<Restrict>

Actor= 1

Switch(21)= On

</Restrict>

When I do this, it should make so that anyone but actor 1 can use the item. However, once switch 21 is on, Actor 1 can also use the item.

But in practice, what happens is that only the second set of restrictions will work. So, currently, no one can use the item at all unless the switch is pulled. Then only Actor 1 can use it.

If I reverse the restriction order, anyone can use the item except actor 1 whether the switch is pulled or not.
Thank you for the bug report. I'll take a look at this and (hopefully) find the problem and correct. :)
Bobstah

#51 Dec 11, 2015, 12:19 AM Source

Version 1.5 is now available! Added the ability to restrict the items battle command. Download

This was a simple update released by request.

@Seleroan: I will have your bug fixed in a day or two. I am very sorry for the delay.
Radis3D

#52 Dec 11, 2015, 01:17 AM Source

what's the news?

the change log still 1.4.2...

:3

Edit:

Ah sorry, i didn't see the last post for the change logs..

D:
Bobstah

#53 Dec 11, 2015, 02:05 AM Source

@Radis3D: Thanks for pointing that out. I updated the original post's changelog. :)
Radis3D

#54 Dec 11, 2015, 10:20 AM Source

Bobstah said:
@Radis3D: Thanks for pointing that out. I updated the original post's changelog. :)
you are welcome... :3

i really2 didn't know if you write it on your last post... :3
Bobstah

#55 Dec 11, 2015, 11:17 AM Source

Version 1.5.1 is now available! Corrected a restriction logic issue and base RPGMV functionality. Download

Seleroan said:
Just wanted to let you know that the "can use multiple restrictions but actor only needs to meet one" thing isn't working. Or at least, I'm not understanding how you meant it to be implemented.

<Restrict>

!Actor= 1

</Restrict>

<Restrict>

Actor= 1

Switch(21)= On

</Restrict>

When I do this, it should make so that anyone but actor 1 can use the item. However, once switch 21 is on, Actor 1 can also use the item.

But in practice, what happens is that only the second set of restrictions will work. So, currently, no one can use the item at all unless the switch is pulled. Then only Actor 1 can use it.

If I reverse the restriction order, anyone can use the item except actor 1 whether the switch is pulled or not.
I tested this and figured out the problem, which was two-fold.

Firstly, there was a logic issue with the way I was testing restrictions. I corrected this, but unfortunately it didn't solve the problem.

Secondly, RPGMV only tests if the entire party can use the item. If one party member can use it, it assumes everyone can use it. I changed that functionality to also check to see if the current actor could use the item. It now works as expected. :)

(Also, make sure you are using a colon ( :) instead of equals (=) in your notetags. I assumed you typed that out freehand, but I just want to make sure. :) )
Sprist

#56 Dec 18, 2015, 08:59 PM Source

It is possible to place a class of items (eg shields ) and it will add the restriction to all shields , or I have to put each of the shells individually?
Bobstah

#57 Dec 19, 2015, 12:04 AM Source

Sprist said:
It is possible to place a class of items (eg shields ) and it will add the restriction to all shields , or I have to put each of the shells individually?
Expanding the global restrictions is something I am definitely doing in future updates, and I was having a PM conversation with someone where I thought this would be perfect. :p
kodysun17

#58 Dec 22, 2015, 02:27 PM Source

Is there any way to make a skill avaliable only if the enemy is under a certain state?

For example: My hero own a skill called "Dark Strike" that can only be used if the target is under the "Cursed" state?

So, in order to use "Dark Strike", I need to aply the "Cursed" state to the enemy before.

Sorry, bad english! Hope you understand.

I really like your plugin! Thank you.
Bobstah

#59 Dec 22, 2015, 03:39 PM Source

@kodysun17: No. I can look at this, but I'm not sure off the top of my head if it even checks to see if an enemy is a valid target. I think it defines scopes and that's it. I might be able to do something with this, though. :)
Sprist

#60 Dec 23, 2015, 04:04 PM Source

I have a problem : I'm trying to do a skill that can only be used when equipped with shield , however, when i place the note :

< Restrict >

Armor: 1

</ Restrict >

to restrict the ability, it blocks even with the shield equiped ( I checked and Shield ID is correct ) . I would like to understand if I'm doing something wrong or if it some kind of bug.