RPG Maker MV/MZ: Status Construct
FEATURES:
- State stacking.
- Bleed over states.
- Add state on restrict/resist.
- Add state on state removal.
- Weapon based status effect accumulation.
- Elemental modification.
- Visual State Effects
Top right corner of image shows poison state with three stacks.
Default max stack is used when the note tag for state max stack is not used.
Elemental Configuration allows for adding states based on elemental damage. If target's elemental state modifier goes above or is equal to 100, the add element state from elemental configuration will be added and the remove element state is removed. If it goes below -100, the remove element state will be added instead whilst the add element state is removed.
You can disable the negative element state by disabling it in plugin parameters.
Weapon Configuration is used to add states based on weapon type as stated in the database:
In the plugin parameters, we need to configure each state:
- Name: Does nothing. Used to identify state configuration from list.
- State: The actual state to configure.
- Max Stacks: The maximum number of stacks the state will have.
- Overstack State: State added alternatively when state stack exceeds maximum number of stacks.
- Delete On Overstack: Delete the state stack if overstack state is to be added.
- Removal State: Adds this state when the original "State" is removed.
- State Removal Type: Remove single state stack or all state stacks
- Resist State Add: Add state when the original state is resisted.
- Restrict State Add: Add state when the original state is restricted.
- Code: Execute JavaScript code under stated conditions.
Purchase
In order to download this tool you must purchase it at or above the minimum price of $10 USD. You will get access to the following files:
Download demo
Development log
- v3.7 - Evaluation14 days ago
- v3.6 - Incompatibility Patch16 days ago
- v3.5: State Costs and HELP!!!17 days ago
- v3.4 - More elemental and status effects48 days ago
- v3.3 - Flat Stats62 days ago
- v3.2 - Explanation on Dynamic Evolvable StatesMay 25, 2025
- v3.1 - Fix loading destroyedMay 12, 2025
- 3.0 - Minor Incompatibility CorrectionMay 10, 2025
Comments
Log in with itch.io to leave a comment.
If I target an enemy's weakness, can a state be applied solely for that?
You can modify the state application rate for it so that it applies faster making that particular enemy more vulnerable to that stats effect or elemental effect
Is that a yes? I'm not sure I understand your response.
If I target an enemy's fire weakness, can a state be applied because it is weak to it? I don't need it doing anything else.
If you set an element state, the rate of application will be based on the element rate of the target.
If the target element rate is 0%, no count towards adding the state is applied. If the element rate is 100%, 100% of the count is applied. If the element rate is 500%, 500% or 5x the count towards the element state is added
That's not the answer to the question. I don't care about the elemental rate. I want to know if I use a skill an enemy is weak to, can I make it so the enemy gets a state because of it? Yes or No.
Yes: You can add any elemental state to any enemy based on the rate because it uses a "rate score" system which will determine how fast/easy it is to apply that weakness state. Eg: if an enemy has 1% fire rate, it will apply 100 times slower if using the fire skill skill compared to the default 100%. The default rpg maker elemental system already provides groundwork for multiple elemental effectiveness, weakness and strengths. It does not allow for multi-element skills however so it's a half implementation from the default side.
No: You do not set an enemy as weak towards a specific skill using this plugin nor do elements apply has a boolean weakness (true/false) in this plugin nor does it set a fixed value of weakness based on enemy attack element as such does not natively exist in rpg maker as elements are applied as rates not as boolean type.
Sorry if confusing but what I'm trying to say is that it does not have a yes or no to your specific question. The question implies specific statement in that elements already have a weakness in rpg maker and this is not the case, hence ambiguous answer.
Is this comparible with vs plugin?
If you have any issues with this and Visustella plugins, please let me know!
Those plugins are obfuscated and as such I can only deal with issues as reported
No problem for now, i tried this...first time when the state added it Will be removed at the same time. Like
+Burn
- burn
I place the plugin under the vs plugin, then i try to move it on top of vs plugin, and it work
I bought this but the state stack numbers don't appear
Does the state stack?
i got it working, it was a plugin order issue
i only need the stacks so my common event only triggers if one stack,
i only need the numbers so the player knows how many shadow clones they have
Good stuff👍
i did have to use your older stack plugin too because for some reason it was still detecting it as the first stack even though the 2 was visible
So you're using both?
There seems to be a bug which stops the last stack of the state from being removed if you have the "state removal type" set to "single" in the plugin parameters.
Using either the "remove state" event function or the plugin's script for decreasing states will not remove the last stack. Only the "Recover All" function will remove the final stack. Hoping this can be fixed soon.
I can send a project file with the bug if you have a contact email.