Item Suite

ATT_Turan · 2025-12-24T11:01:20+0900

I know I'm a couple of days early, but I'm going to be too busy on the actual holiday to post this, so...here you go! One of the fairly frequent requests I've seen that - as far as I know - has never really been addressed is the ability to easily manipulate items in MZ. Because the engine doesn't support this by default, everything in this plugin requires the Independent Items plugin by @Dungeonmind. I'm aware that various options exist to port Yanfly's Item Core into MZ, but as that is not a native solution, this plugin is not compatible with it. So, without further ado, I present: Item Suite 1.7 ATT_Turan Introduction This plugin has a number of features to give the dev/player new ways to work with and manipulate items in their game. All of the functionality has been designed to be modular, so it should be easy to pick and choose which features you want to integrate into your project. I have tested the basic functionality, please let me know if you encounter any errors. I will consider making compatibility patches if the other plugin is free to use and unobfuscated. Otherwise, other authors are free to modify this code to make it compatible with theirs so long as I am still credited. Features Due to the number of features, they've been broken down into their own sections: Spoiler: Parameter Randomizing Enabling this will cause weapons and armors to have their parameter bonuses randomized when they're created, so that - for example - three longswords will have different stats from each other. The plugin parameters control how much the parameters can vary and whether to make that variance be a numeric range or a percentage of the values defined in the database entries. Spoiler: Item Slots This allows you to have slots in your weapon and armor which you can place other items into, upgrading their parameters or traits. I've not tested it, but the slotted items are considered to be equipped so they should also work with VisuStella passive states. A variety of plugin parameters and notetags are provided to customize how slots are generated on items, what can be placed into them, and whether they can be removed or replaced. All upgrades to be placed into slots are defined as Armor in the database. One important point is that slots are "generic" unless manually defined otherwise. A generic slot can have any kind of upgrade slotted into it unless notetags are used to say otherwise. Notetags can be used to make slots that are not generic but rather of a specific type, which then can only have upgrades of the appropriate type placed into them. Spoiler: Notetags Weapon and Armor notetags: Code: This prevents the item from having any of the generic slots as defined in the Armor Slots or Weapon Slots plugin parameter. Code: This will force the item to always have this number of generic slots. This is in addition to any defined in the Armor Slots or Weapon Slots plugin parameters, unless you also use the notetag. Example: Code: This adds a slot which can only be filled with a slottable item that has a matching slot type notetag. You may have multiple tags of these on an item, with the same or different types. Example: Armor notetags: Code: Denotes this item as one that can be put into slots. You usually want this to have an item type that can't be equipped by any characters. Code: Used in combination with , this prevents the item from being placed into generic slots. This means it must use the slot type notetag to be usable. Code: Used in combination with , this allows the item to be placed into slots also labeled with that type. Note that it can also be placed into any generic slots unless it has the notetag. Example: Spoiler: Durability Weapons and armor with durability will wear out as they're used. Every time a non-magic skill with the type Physical Hit does damage, the weapon will lose a point of durability (if the actor is dual-wielding, both weapons will lose it). Similarly, each time an actor is damaged by a non-magic skill of type Physical Hit, all of their equipped armor will lose a point of durability. Plugin parameters determine what happens when durability runs out, whether it destroys the item or removes it to inventory so it can still be repaired. An interface has been added to the Shop menu for spending gold to repair weapons and armor. Spoiler: Notetags Weapon and Armor notetags: Code: This will force the item to spawn with the specified durability. It bypasses* any durability and variance specified in the plugin parameters. Note that a durability of 0 makes the item indestructible. Example: Spoiler: Script Calls Code: actor.loseDurability("type", value) actor.loseDurability(slot number, value) This causes the referenced actor to lose the value amount of durability from all eq…

● ARCHIVED · READ-ONLY

Started by ATT_Turan Dec 24, 2025, 02:01 AM 28 posts Page 2 of 2 View original ↗

SorenKyojin

#21 Mar 1, 2026, 08:25 PM Source

One question: What code can I put inside "On Gain Eval" ?
Is it JavaScript code or like Damage Formula code ?
ATT_Turan

#22 Mar 2, 2026, 03:02 AM Source

SorenKyojin said:
Is it JavaScript code or like Damage Formula code ?
The damage formula is JavaScript so...yes?

Let me know if you have a more specific question.
dewolf

#23 Mar 29, 2026, 11:09 PM Source

Hey @ATT_Turan! First, phenomenal suite. Infinite gratitude on creating this.

I wanted to flag a potential bug I may have found? Since I'm only using slots for a materia-like system, I got around it easy enough by just depending on the universal typing and avoiding the "slot type" notetags all together. But I noticed using the "slot type" notetags causes any object to be slottable, even if the "slottable" tag isn't used on the object. Tried it with all plugins disabled save yours and Dungeon's, as well, to be sure. OR if I misread the documentation and am misusing the notetags, feel free to bonk me. lol

Screenshots
ATT_Turan

#24 Mar 29, 2026, 11:22 PM Source

dewolf said:
I noticed using the "slot type" notetags causes any object to be slottable, even if the "slottable" tag isn't used on the object.
Thanks, I've uploaded version 1.6 which corrects the bug - I had a parenthesis in the wrong place.
dewolf

#25 Mar 29, 2026, 11:30 PM Source

ATT_Turan said:
Thanks, I've uploaded version 1.6 which corrects the bug - I had a parenthesis in the wrong place.
You're the best! :kaoluv:
DarkFenix

#26 Apr 2, 2026, 07:14 PM Source

I receive this error: "TypeError TUR.OpenDisassemble is not a function" when calling the disassembly screen.
ShadowDragon

#27 Apr 2, 2026, 07:40 PM Source
DarkFenix said:
I receive this error: "TypeError TUR.OpenDisassemble is not a function" when calling the disassembly screen.
I think there is an mismatch and should probably be readed like:
JavaScript:
PluginManager.registerCommand("TUR_ItemSuite", "OpenDisassemble", () => { TUR.OpenDisassemble(); });
because the functions has no args, so it can't be used like that.

change line 435 and replace like above, and see if it fix your issue.

otherwise, ATT_Turan can enlighten you or correct me if I'm wrong.
ATT_Turan

#28 Apr 3, 2026, 01:50 AM Source

ShadowDragon said:
I think there is an mismatch and should probably be readed like...because the functions has no args, so it can't be used like that.
No, that's not correct. Functions always have an argument list - it may be empty and unused by parameters in the function, but it still exists. That also wouldn't have anything to do with the reported error.

@DarkFenix I had a typo on one line - thanks for reporting the error, a corrected version has been uploaded.