Uncaught SyntaxError: Unexpected identifier
[Deprecation] GainNode.gain.value setter smoothing is deprecated and will be removed in M64, around January 2018. Please use setTargetAtTime() instead if smoothing is needed. See https://www.chromestatus.com/features/5287995770929152 for more details.
WebAudio._createMasterGainNode @ rpg_core.js:6605
[Deprecation] AudioParam value setter will become equivalent to AudioParam.setValueAtTime() in M65, around March 2018 See https://webaudio.github.io/web-audio-api/#dom-audioparam-value for more details.
And thanks for the reply.
Edit: I found out the Error "Uncaught SyntaxError: Unexpected identifier". You can ignore it. But didin't solve my problem.
I've got an item that's blank but has notetags to recover cparams (<RECOVER CPARAM: 0 2>). Works fine, but if you use it in battle no damage numbers come up to indicate what's being healed.
I've set the affected cparams as Default Valid and Main cparams in the plugin, but no change.
The item actually recovers three different cparams at once, so I can't just set HP damage and put in <DAMAGE TYPE: CParam>.
I've set it so damage type is one of the cparams for standard attack. In theory all attacks should be affecting that cparam, but no damage numbers appear at all. I've also set the potion item to recover all three cparams. Maybe I've set up the plug-in wrong, I'm not sure.
Hi @ICF-Soft !
First of all, thank you for this amazing plugin. It has allowed me to begin building the custom damage and status effect mechanics I want for my game
I believe I have found a bug to report. Using v1.09, I found that my CUSTOM NPARAM BASE notetags were not working for my custom NParams beyond the first 30. Looking through your code, I found that obj.customNParam (line 2932) appears to be set to an array containing 30 ''. I added 70 more '' to the array, which appears to have resolved the problem so that the notetags now work for all 100 possible custom NParams. Based on the structure of the surrounding lines, 2930-2933, I suspect there is a similar bug and fix for other NParam and CParam notetags I have not yet tested.
I saw the bug but the solution is a bit different. This bug only affects obj.customNParam and obj.customCParam because I forget a step that allow the use of higher indexes.
I'll prepare version 1.09c.
I'm not sure what can it be. My plugin also covers XParams like YEP_ExtraParamFormula does so these functions are overwritten.
I wanted to use your plugin only to add one or two params, and I wanted to keep the Yanfly one because I use YEP_X_Classbaseparam and it depends on Yep_BaseParamControl.
But I guess your plugin can do the same thing as YEP_X_Classbaseparam in which case I don't need Yanfly's plugin.
I'll take this opportunity to find out what the @Spoofuss issue is about. Question:
Is there a way to have the new stats link to other stats say, who have a strength stat and for every 2 points in it, it will add 1 point to attack
And say for vitality for every 1 point it add 2 maxhp and per 2 points it adds 1 point to defense etc. etc.?