Quasi Params Plus

Quxios · 2015-11-01T12:28:00+0900

[Quasi] Params Plus Version 1.07 MV by Quasi What it does: Params Plus allows you to add a fixed param value to states and equipment. With this you can create states that will add a constant value to a parameter. Or create a poison / regeneration state that ticks a fixed number. Params Plus also includes a few new parameters and lets you create new parameters that you can use and modify! Params Note Tag Spoiler Param: Value Where param can be: MHP, MMP, ATK, DEF, MAT, MDF, AGI, LUK, any of the new Parameters included or any of the new Parameters that you create. Value can be any number or even a formula. Can use a and v[] but not b! (This can be placed inside, Actors, Classes, Enemies, Weapons, Armors and State notetags) HRT, MRT, TRT are new params that work like HRG, MRG, TGR but instead of increasing/decreasing by a percentage, they tick a fixed value. New Params Spoiler (HRT) Hp Regeneration tick - Works like Hp Regeneration (Ex-Parameter) (MRT) Mp Regeneration tick - Works like Mp Regeneration (Ex-Parameter) (TRT) Tp Regeneration tick - Works like Tp Regeneration (Ex-Parameter) (MCC) Mp Cost Constant - Works like Mp Cost Rate (Sp-Parameter) (TCC) Tp Charge Constant - Works like Tp Charge Rate (Sp-Parameter) (PDC) Physical Damage Constant - Works like Physical Damage (Sp-Parameter) (MDC) Magical Damage Constant - Works like Magical Damage (Sp-Parameter) (FDC) Floor Damage Constant - Works like Floor Damage (Sp-Parameter) (EXC) Experience Constant - Works like Expericence (Sp-Parameter) Creating new Parameters Spoiler To use custom parameters, you first have to enabled "Use Custom Parameters" in the plugin settings. Next you need to create a json file inside the data folder called "Parameters.json". If you do not know how to create a .json file download my sample * https://gist.github.com/quasixi/3b928832bf42d4471560 JSON template [ {"abr": "abbreviation 1", "name": "param 1 name", "default": value}, {"abr": "abbreviation 2", "name": "param 2 name", "default": value} ] (See the Example json file above for a better example!) Set abbreviation to the abbreviation you want to use for the new param. * Do not use any existing abbreviations ( Example: mhp, mmp, atk, ect..) Set param name to the full name of the parameter. Set default value to an number ( Can not use formulas here! ) ** Everything should be inside quotes except the value for default! ** Be careful with comma placement! Place a comma after every closing bracket } but not on the last one! If you need helping setting these up, let me know or give me a list of the abbreviations, full name and default values, and I'll create it for you. Using new Parameters Spoiler After you have created the new parameters you can use them the same way as you use existing parameters. For example, lets say the abbreviation of a parameter I made was "qpp" If I want to get the value of qpp for my player I would use: $gameParty.members()[member ID].qpp Or if you want to use these parameters inside a formula you would do: a.qpp or b.qpp These new parameters can be used inside the fixed params note tag! To Change a custom Parameter use Code: $gameParty.members()[member ID].addCParam(CParamId, value) CParamId is the id of the custom parameter. which is based on the order the custom param was made. So in my example since param qpp was made first that would have an id of 0, while qpt has an id of 1. Value can be a negative number. To Set a custom Parameter use $gameParty.members()[member ID].setCParam(CParamId, value) CParamId is the id of the custom parameter. which is based on the order the custom param was made. So in my example since param qpp was made first that would have an id of 0, while qpt has an id of 1. Value is the number you want to set the parameter too. Getting data from the new custom parameters QuasiParams.customAbr(ID)QuasiParams.customName(ID)QuasiParams.customMin(ID)QuasiParams.customMax(ID) * Set ID to the id of the custom parameter. Converting Stats to Ex-Parameters or Sp-Parameters Spoiler You can now convert X amount of points from a stat to a % of an Ex-Parameter! NoteTag: X STAT to XPARAM Set X to the number, make X negative for a negative gain in the rate. STAT should be the abbreviations for any of the normal parameters + new parameters + custom parameters. My example I used agi. XPARAM should be the abbreviation for an xparam or sparam Abbreviations for xparams: hit, eva, cri, cev, mev, mrf, cnt, hrg, mrg, trg Abbreviations for sparams: trg, grd, rec, pha, mcr, tcr, pdr, mdr, fdr, exr Example of this in the Examples spoiler. Using a formula instead Note Tag: XPARAM: value Set XPARAM to the abbreviation for a xparam or sparam Value can be any number or even a formula. Can use a and v[] but not b! Examples Spoiler Example 1: MHP: 100ATK: 20 Would result in that state adding 100 to max hp and 20 to attack. Example 2: MHP: -100…

● ARCHIVED · READ-ONLY

Started by Quxios Nov 1, 2015, 03:28 AM 173 posts Page 7 of 9 View original ↗

Emperor DragonBreath

#121 Mar 5, 2016, 04:27 AM Source

I push F8 while playtesting, still no console, but a screenshot shall arrive!
Emperor DragonBreath

#122 Mar 5, 2016, 04:29 AM Source

What programs make it easy to take screenshots?
Emperor DragonBreath

#123 Mar 5, 2016, 04:46 AM Source

This is my screenshot!
Emperor DragonBreath

#124 Mar 5, 2016, 05:05 AM Source

You know anything about this?
Emperor DragonBreath

#125 Mar 5, 2016, 05:44 AM Source

This is the full console!
Emperor DragonBreath

#126 Mar 5, 2016, 07:04 PM Source

Is there any way to make the custom parameters increase as an actor levels up?
Quxios

#127 Mar 5, 2016, 07:35 PM Source

You can use formulas in the <params></params> in the actor notes or in the classes. So you can probably do something like (untested) :

<params>
qpp: a.level * 5
</params>

( not sure if that a.level is correct, can't remember )

This would increase my "qpp" stat by 5 every level.
Emperor DragonBreath

#128 Mar 5, 2016, 08:02 PM Source

Quasi said:
You can use formulas in the <params></params> in the actor notes or in the classes. So you can probably do something like (untested) :

<params>
qpp: a.level * 5
</params>

( not sure if that a.level is correct, can't remember )

This would increase my "qpp" stat by 5 every level.

I think I might have already figured it out!
SuperMasterSword

#129 Mar 5, 2016, 09:33 PM Source

@Quasi Can Tsukihime's Parameter Tables plugin be used to edit custom parameters created through here?

http://himeworks.com/2016/01/parameter-tables-mv/
Quxios

#130 Mar 5, 2016, 09:46 PM Source

Looked at the code, and I'm pretty sure it doesn't because I did not add a parameter base function for the custom parameters.
Emperor DragonBreath

#131 Mar 7, 2016, 01:38 AM Source

Can this plug in be used to create a hit count kind of like in the original Final Fantasy or even Bravely Default, where the total damage from multiple hits is combined into one huge number?
Quxios

#132 Mar 7, 2016, 02:37 AM Source

I have no idea what you mean, but probably not. This plugin only deals with parameters. It adds a few new parameters and lets you create as many custom parameters as you'd like. As well as modifying parameters inside the database. This doesn't make changes to how damage is handled, shown or formula is calculated
Emperor DragonBreath

#133 Mar 7, 2016, 05:18 AM Source

This is the FF1 example of what I mean!
Quxios

#134 Mar 8, 2016, 05:16 AM Source

I don't think so. Cause again, this doesn't change how your damage is shown or anything.
Roguedeus

#135 Mar 17, 2016, 09:16 AM Source

@Quasi Are custom parameters supposed to be integer values only?

I recently found myself adding 'rate' type parameters and all the values are being rounded to the nearest integer. Checking the code verifies you're assuming that all custom parameters will be clamped into integer values.

However, I can't find anywhere in the instructions pointing this out. (Sorry if someone already asked about this)

If you intend to keep this integer only, I'll write myself a addition. :)

Edit:

Also, I am really curious why you add and subtract 9 from the cParamId. Could I ask you to explain that? :D

I'm sure there is a simple reason I'm missing from a lack of experience.
Quxios

#136 Mar 17, 2016, 06:06 PM Source

Oh yeah I see. You can remove that Math.round, didn't notice I left that lol I'll remove it myself though, that wasn't intentional. The clamping is just to make sure it's inside the min / max range which looks like I forgot to mention in the json description.

As for subtracting / adding 9 to the Id is so your custom parameter can start at 0. It uses the qParam() function which is shared with the 9 built in custom parameters (hrt, mrt, trt, ect. ) and inside the function it calls functions that use the default 8 parameters, so we add 8 to the id.

So a better visual:

We want to call a custom parameter of Id 0.

Inside cParam() the Id is 0

Inside qParam() the Id is 9, because the 1st 8 are the built in params

inside stateParamPlus(), equipParamPlus(), and getCharaParamPlus() the Id is 17 because we added another 8, since 1st 8 in those functions are the default parameters.

Edit: Github file edited to remove the round:
https://github.com/quasixi/RPG-Maker-MV/blob/master/Database/QuasiParamsPlus.js
Roguedeus

#137 Mar 18, 2016, 01:49 AM Source

Thanks for taking the time to explain that. :)

I am using this plugin as a foundation for a few custom stats. Two stats used for Yanfly's Armor Scaling, a magic attack HIT rate (called Cast) and an Energy system. (Think of Stardew Valley, only less restrictive)
Quxios

#138 Mar 18, 2016, 02:01 AM Source

Cool, well feel free to ask me questions any time.
Roguedeus

#139 Mar 28, 2016, 03:25 PM Source

@Quasi I seem to have run into a recursion issue with ParamsPlus...

When a state applies a parameter change to an actor, and that actors parameter is then accessed, this error occurs.

(Edit: This happens to be a state example, but it happens any time the effected actors base param is used in the formula. They all use evalParamFormula() )

(Edit2: Seems the issue is only when the parameter being referenced is the one being adjusted... Thanks for Hime pointing it out... I missed it.)

rpg_managers.js:1618 RangeError: Maximum call stack size exceeded
at Game_Actor.Game_BattlerBase.evalParamFormula (file:///X:/SkyDrive/_RMMV%20Projects/Projects/Clean%20-%20QuasiParams/js/plugins/QuasiParamsPlus.js:467:17)
at Game_Actor.Game_BattlerBase.stateParamPlus (file:///X:/SkyDrive/_RMMV%20Projects/Projects/Clean%20-%20QuasiParams/js/plugins/QuasiParamsPlus.js:476:23)
at Game_Actor.Game_BattlerBase.param (file:///X:/SkyDrive/_RMMV%20Projects/Projects/Clean%20-%20QuasiParams/js/plugins/QuasiParamsPlus.js:440:19)
at Game_Actor.Object.defineProperties.luk.get (file:///X:/SkyDrive/_RMMV%20Projects/Projects/Clean%20-%20QuasiParams/js/rpg_objects.js:2136:42)
at Game_Actor.eval (eval at <anonymous> (file:///X:/SkyDrive/_RMMV%20Projects/Projects/Clean%20-%20QuasiParams/js/plugins/QuasiParamsPlus.js:467:17), <anonymous>:1:3)
at Game_Actor.Game_BattlerBase.evalParamFormula (file:///X:/SkyDrive/_RMMV%20Projects/Projects/Clean%20-%20QuasiParams/js/plugins/QuasiParamsPlus.js:467:12)
at Game_Actor.Game_BattlerBase.stateParamPlus (file:///X:/SkyDrive/_RMMV%20Projects/Projects/Clean%20-%20QuasiParams/js/plugins/QuasiParamsPlus.js:476:23)
at Game_Actor.Game_BattlerBase.param (file:///X:/SkyDrive/_RMMV%20Projects/Projects/Clean%20-%20QuasiParams/js/plugins/QuasiParamsPlus.js:440:19)
at Game_Actor.Object.defineProperties.luk.get (file:///X:/SkyDrive/_RMMV%20Projects/Projects/Clean%20-%20QuasiParams/js/rpg_objects.js:2136:42)
at Game_Actor.eval (eval at <anonymous> (file:///X:/SkyDrive/_RMMV%20Projects/Projects/Clean%20-%20QuasiParams/js/plugins/QuasiParamsPlus.js:467:17), <anonymous>:1:3)

I have been using states (passive states) to adjust custom parameters for some time and found no issue. Which is why its taken so long to notice this.

I began swapping out trait parameter rates with formula rates using this plugin... and things broke. :)

I am actually kind of surprised no one else has notice this... :unsure:

But then, I don't think many people would try to replace what already works fine with trait based rates.
Tsukihime

#140 Mar 28, 2016, 03:29 PM Source

@Roguedeus

What happens if you use something like

ATK: a.luk * 0.25

Instead of luck based on luck?