Conditional Branch+

● ARCHIVED · READ-ONLY
Started by mjshi 99 posts Page 5 of 5 View original ↗
  1. Thanks.
    mjshi said:
    Yep! So in that example you'd want to see if the player has more than 5 of items 1, 2, 3, and 4.
    Thanks Tested myself before you replied but got my crafting quest system working with this script.
  2. Would I be able to compare one variable's value with other two?

    I.e. If Variable A >= Variable B and Variable A >= Variable C
    Show Text: "Your variable A is greater than both B and C"
  3. Alkaline said:
    Would I be able to compare one variable's value with other two?

    I.e. If Variable A >= Variable B and Variable A >= Variable C
    Show Text: "Your variable A is greater than both B and C"

    JavaScript:
    Check.each_greater([A, $gameVariables.value(B)], [A, $gameVariables.value(C)]);
    //or
    ($gameVariables.value(A) >= $gameVariables.value(B) && $gameVariables.value(A) >= $gameVariables.value(C));
  4. Check.equipped(1, "armor", 1) does not seem to work, but Check.equipped(1, "weapon", 1) works, I don’t understand :rtear:
  5. Is there an MZ version of this plug-in available?
  6. @Taraque probably not, if it doesn't work in MZ, try to use FOSSIL and it might work.
  7. ShadowDragon said:
    @Taraque probably not, if it doesn't work in MZ, try to use FOSSIL and it might work.
    It works on MZ. But I was hoping if there's an MZ version available, I would rather use that one for better compitibility.
  8. there is no MZ version so far I know it, if it works without FOSSIL, you are mostly
    good to go, if you use FOSSIL, you probably need it to let it port it over if it's allowed
    by the author of this plugin :)
  9. Is there a patch for RPG Maker MV 1.6.3? The plugin stopped working.
  10. @RenatoDias it works in 1.6.1 and so far I know, 1.6.2 and 1.6.3 has no changes to the core.
    so it should work.

    make sure it is activated and you got no typo's in order to make it correctly.
  11. ShadowDragon said:
    @RenatoDias it works in 1.6.1 and so far I know, 1.6.2 and 1.6.3 has no changes to the core.
    so it should work.

    make sure it is activated and you got no typo's in order to make it correctly.
    What would be the order for this plugin?
    Update: I've checked for typo's, and everything is according to the plugin's manual, but doesn't work.
    Update #2: Seems like it's the Check.in_range feature.
  12. RenatoDias said:
    What would be the order for this plugin?
    Update: I've checked for typo's, and everything is according to the plugin's manual, but doesn't work.
    Update #2: Seems like it's the Check.in_range feature.
    No one can help you just from saying "it doesn't work" and "it's this function."

    You need to paste screenshots of your event where you're using it, describe what's happening instead, and press F8 during the playtest; go to the Console tab, see if there are any errors to post screenshots of.

    As ShadowDragon said, the code did not change from 1.6.1 on (and it would affect your project even if it had, unless you manually copied in new core scripts).
  13. 1719718422767.png
    It's a time-based screen tinting function. It's supposed to check variable 43(which is hour of day) and tint the screen accordingly. But I've tried these and Check.in_range, none work for this specifically. Plugin in in the top of the list.
    Also, the browser-like debug doesn't help so much.
  14. while you calls are correct, how is this event running?

    common event? parallel on map? because when I test that, it seems to work,
    even when I separate the else if conditions, no problem here on 1.6.1 and 1.6.2.

    so it's hard to tell what you miss and if your console log does print.

    try to run the console log into your console alone and set this scriptcall directly.

    Check.lesser(43,5)

    see what it prints, if it prints a value or boolean, it means it does work, but your event does not.
  15. ShadowDragon said:
    while you calls are correct, how is this event running?

    common event? parallel on map? because when I test that, it seems to work,
    even when I separate the else if conditions, no problem here on 1.6.1 and 1.6.2.

    so it's hard to tell what you miss and if your console log does print.

    try to run the console log into your console alone and set this scriptcall directly.

    Check.lesser(43,5)

    see what it prints, if it prints a value or boolean, it means it does work, but your event does not.
    It's a parallel process common event. Used to work before MV 1.6.3.
  16. like I said before, version 1.6.1 to 1.6.2 and 1.6.3 has no core change, so that it
    stops working is weird.

    can you try in a clean project to confirm it does work or not?
  17. Tried in my project, but it doesn't even print on the console. Only error that prints is my MoneyLimit.js, which I made to change the money limit for the game.
  18. RenatoDias said:
    View attachment 309942
    It's a time-based screen tinting function. It's supposed to check variable 43(which is hour of day) and tint the screen accordingly. But I've tried these and Check.in_range, none work for this specifically. Plugin in in the top of the list.
    Also, the browser-like debug doesn't help so much.
    Edit: I realize OP may be trying to use this specific script call - I am mainly checking the traditional approach to checking variable values to see if it works and found that there may have been an issue with the logic.

    Unless I made a mistake somewhere, your first if script needs to be: greater(43,5) && lesser(43,18)
    You might as well use any_inrange(43,5,18).

    Currently, I think if the value of variable 43 is less than 5 or greater than 20, the first and last if-statements are true, causing an issue with the tint.

    You can try the old script call approach to see if it is a scripting issue or a plugin issue:
    JavaScript:
    ◆If:Script:$gameVariables.value(43) > 5 && $gameVariables.value(43) < 18
      ◆Tint Screen:(0,0,0,0), 60 frames (Wait)
      ◆
    :Else
      ◆If:Script:$gameVariables.value(43) >= 18 && $gameVariables.value(43) <= 19
        ◆Tint Screen:(68,-34,-34,0), 60 frames (Wait)
        ◆
      :Else
        ◆If:Script:$gameVariables.value(43) < 5 || $gameVariables.value(43) > 20
          ◆Tint Screen:(-68,-68,0,68), 60 frames (Wait)
          ◆
        :End
        ◆
      :End
      ◆
    :End
    This works on my end. Hopefully it isn't an issue of a parallel event, or something that is changing the value of variable 43.
  19. The old scripting method worked for me. Coloring is working now.
    About variable 43's value, only the time control manipulates it, going from 0 to 23.