Show Parameters

● ARCHIVED · READ-ONLY
Started by DreamX 20 posts View original ↗
  1. show param equip core.png


    Current Features


    Define the parameters shown on the Yanfly's menu plugins. You can use custom parameters from Quasi Param Plus, too.


    Future Updates


    1. Be able to define the parameters shown individually for each equipment (optional).


    2. Be able to show only parameters that are effected by the equipment (optional)


    3. Integrate with Yanfly's Status Core so that you can define the parameters shown there too.


    4. Integrate with Yanfly Shop Menu Core


    5. Integrate with the default status menu


    Script

    Code:
     * ============================================================================
     * How To Use
     * ============================================================================
     * When defining parameters, you can either use the parameter number or
     * parameter abbreviation. Use lowercase. If you are using Quasi Params Plus, 
     * you can use the abbreviations from that plugin as well. 
     *
     * 0 - mhp
     * 1 - mmp
     * 2 - atk
     * 3 - def
     * 4 - mat
     * 5 - mdf
     * 6 - agi
     * 7 - luk
     *
     * For Parameter "General Parameters", use lo or hi after each parameter to
     * designate whether is displayed with a long box or a short one.
     * ============================================================================
     * Terms Of Use
     * ============================================================================
     * Free to use and modify for commercial and noncommercial games, with credit.
     * Credit Quasi for their parameter plugin.
     * ============================================================================
     * Credits
     * ============================================================================
     * DreamX
     * Thanks to Yanfly for their plugins.
  2. I sure did mean attack! Thanks for catching that.


    At first I couldn't figure out why it wasn't working, but it turns out one of the plugins I was using was taking over the status menu (Not sure which, as none of them should). However, when I try the above in a new game with no plugins, it works like a champ! Now I start the process of making the change in all the other menus, and figuring out which plugin held it. 


    And by reading your code, I learned something, which is even better. Thanks a ton for your help DreamX! I'll keep an eye out on your plugin, and make sure you get credit if I ever actually release!
  3. Is there an option to hide certain stats, when leveling up with yanflys aftermath plugins?
  4. v0.2


    Updated a lot, unless I missed something I've enabled the showing/hiding of any battler parameter in Item Core, Equip Core, Status Core and Victory Aftermath Level Up

    Goldschuss said:
    Is there an option to hide certain stats, when leveling up with yanflys aftermath plugins?

    In the newest update!
  5. ICF-Soft said:
    Can you use params from ICF-Soft Params Core?

    I haven't tested your plugin in particular but any custom stats that are integrated with the Game_BattlerBase.prototype.param function would probably work.
  6. DreamX said:
    I haven't tested your plugin in particular but any custom stats that are integrated with the Game_BattlerBase.prototype.param function would probably work.

    I'll check when finished.


    It uses new Game_BattlerBase.prototype.NParam and Game_BattlerBase.prototype.PParam types but I'm thinking about adding even more types.
  7. I'm kinda confuse about how i should display my parameters.
    So far i aways get this erro when i try to display a ex-param or sp-param


    TypeError: Cannot read property '1' of undefined
        at Game_Actor.paramBase (rpg_objects.js:3832)
        at Game_Actor.paramBase (/D:/Drive/The%20Last%20Princess/js/plugins/YEP_CoreEngine.js:1145)
        at Game_Actor.Game_BattlerBase.param (rpg_objects.js:2441)
        at Game_Actor.Game_BattlerBase.param (/D:/Drive/The%20Last%20Princess/js/plugins/DreamX_ShowParam.js:317)
        at Window_StatCompare.drawCurrentParam (/D:/Drive/The%20Last%20Princess/js/plugins/YEP_EquipCore.js:824)
        at Window_StatCompare.drawCurrentParam (/D:/Drive/The%20Last%20Princess/js/plugins/VE_DualWield.js:1331)
        at Window_StatCompare.drawItem (/D:/Drive/The%20Last%20Princess/js/plugins/YEP_EquipCore.js:800)
        at Window_StatCompare.refresh (/D:/Drive/The%20Last%20Princess/js/plugins/DreamX_ShowParam.js:537)
        at Window_StatCompare.setActor (/D:/Drive/The%20Last%20Princess/js/plugins/YEP_EquipCore.js:780)
        at Scene_Equip.refreshActor (/D:/Drive/The%20Last%20Princess/js/plugins/YEP_EquipCore.js:957)
  8. Can you show me the parameter setting you were using?
  9. it happened when i wrote this in the Equip Param


    0 1 2 3 5 cnt

    i've tried to add the lo and hi/ sh and the error persisted
     
  10. kovak said:
    it happened when i wrote this in the Equip Param


    0 1 2 3 5 cnt
     

    I tried this in the equip scene with equip core. Works for me. Try turning plugins off to narrow it down.
  11. EDIT: issue is with VE Dual Wield

    Maybe it's cuz it changes how right and left hand damage is displayed in the equip scene.
    I had to figure out that the def slot displays the off hand damage.


    I've noticed that i can't use other things like elementRate(1) as well.
  12. kovak said:
    EDIT: issue is with VE Dual Wield

    Maybe it's cuz it changes how right and left hand damage is displayed in the equip scene.
    I had to figure out that the def slot displays the off hand damage.


    I've noticed that i can't use other things like elementRate(1) as well.

    Okay, I'll work on it.


    Element rate isn't really a parameter. I'll think about adding the option, though.
  13. Forget the element resistance, though it would be nice to have it compatible with AP block instead.
     
  14. 0.3


    Fixes for showing xparam, sparams and custom parameters from Quasi Params Plus
    Compatibility with Yanfly Shop Menu Core
    Please use the latest version of Quasi Params Plus for custom parameters

    kovak said:
    Forget the element resistance, though it would be nice to have it compatible with AP block instead.
     

    Try asking Alistair if they could use Object.defineProperties so I can more easily make it compatible.
  15. So i can't use Quasis's Param Plus to display Alistar's AP Block, right?



    I'm still gettin an error when i try to add the Counter Rate, but i think it's a different error now.
     
  16. kovak said:
    So i can't use Quasis's Param Plus to display Alistar's AP Block, right?

    No, it's handled differently.

    kovak said:
    TypeError: Cannot read property '10' of undefined


        at Game_Actor.paramBase (rpg_objects.js:3832)
        at Game_Actor.paramBase (/D:/Drive/The%20Last%20Princess/js/plugins/YEP_CoreEngine.js:1145)
        at Game_Actor.Game_BattlerBase.param (rpg_objects.js:2441)
        at Game_Actor.Game_BattlerBase.param (/D:/Drive/The%20Last%20Princess/js/plugins/DreamX_ShowParam.js:313)
        at Window_StatCompare.drawCurrentParam (/D:/Drive/The%20Last%20Princess/js/plugins/DreamX_ShowParam.js:718)
        at Window_StatCompare.drawItem (/D:/Drive/The%20Last%20Princess/js/plugins/YEP_EquipCore.js:800)
        at Window_StatCompare.refresh (/D:/Drive/The%20Last%20Princess/js/plugins/DreamX_ShowParam.js:710)
        at Window_StatCompare.setActor (/D:/Drive/The%20Last%20Princess/js/plugins/YEP_EquipCore.js:780)
        at Scene_Equip.refreshActor (/D:/Drive/The%20Last%20Princess/js/plugins/YEP_EquipCore.js:957)
        at Scene_Equip.create (/D:/Drive/The%20Last%20Princess/js/plugins/YEP_EquipCore.js:877)

    I am not getting this error. Can you tell me the steps to recreate this error in as few steps as possible? Or you can prepare a small demo.
  17. Let me guess, you've updated it to RMMV 1.3, right?

    I haven't updated mine cuz my project uses plugins that are old and may break my game if i update.
  18. kovak said:
    Let me guess, you've updated it to RMMV 1.3, right?

    I haven't updated mine cuz my project uses plugins that are old and may break my game if i update.

    Yes, I did update.
  19. Um... where to place this plugin in relation to Yanfly's and Quasi's Plugins?