Is there a way to minimize choices in events?

Discussion in 'RPG Maker VX Ace' started by ElOtario, Feb 28, 2019.

  1. ElOtario

    ElOtario Villager Member

    Messages:
    25
    Likes Received:
    1
    First Language:
    Pretuguês
    Primarily Uses:
    RMVXA
    So I just made an event, which has a lot of choices. It becomes a nightmare to navigate, so is there a way to minimize choice commands so it's more practical to use the event window?
     
    #1
  2. Engr. Adiktuzmiko

    Engr. Adiktuzmiko Chemical Engineer, Game Developer, Using BlinkBoy' Veteran

    Messages:
    14,407
    Likes Received:
    2,822
    Location:
    Philippines
    First Language:
    Tagalog
    Nope afaik you cant "minimize" any block inside the event editor of Ace.
     
    #2
  3. ElOtario

    ElOtario Villager Member

    Messages:
    25
    Likes Received:
    1
    First Language:
    Pretuguês
    Primarily Uses:
    RMVXA
    dayum, that's unfortunate. Oh well, guess I'll have to improve my eventing methods.
     
    #3
  4. standardplayer

    standardplayer Keeper of Kitties Veteran

    Messages:
    203
    Likes Received:
    683
    First Language:
    English
    Primarily Uses:
    N/A
    Get creative and use common events with dispatch variables. I put big, branching choice blocks mostly in a few different common events. I use variables I set aside to store values according to choices/number input. The variables let the different common events work together.

    I know that's vague, and sometimes it really does come down to big code blocks.

    I just did something like this earlier, let me know if you'd like a better, more detailed example. I can provide code/event snaps
     
    Last edited: Feb 28, 2019
    #4
  5. gstv87

    gstv87 Veteran Veteran

    Messages:
    1,674
    Likes Received:
    694
    First Language:
    Spanish
    Primarily Uses:
    RMVXA
    Code:
    choice start
    -option A
    --go to label, L1
    --label: return L1
    -option B
    --go to label, L2
    --label: return L2
    -option C
    --go to label, L3
    --label: return L3
    choice end
    exit event.
    label: L1
    -instruction
    -instruction
    -instruction
    ...
    -go to label, return L1
    exit event.
    label: L2
    -instruction
    -instruction
    -go to label, return L2
    exit event.
    
    etc
    
    choice block at the top, gosub/goto structure, return at the end of each sub block.
    year 1980 structure.... this was used back in the days of BASIC and LOGO.
     
    #5
  6. Heirukichi

    Heirukichi Veteran Veteran

    Messages:
    1,049
    Likes Received:
    383
    Location:
    Italy
    First Language:
    Italian
    Primarily Uses:
    RMVXA
    One way to reduce your event length and make it easier to navigate is using script calls instead of normal event commands. This applies to each and every event since each event containing conditional branches since each conditional branch appears like this by default:

    > if Condition
    > > Instruction 1
    > > Instruction 2
    > > etc.
    > > Empty line you can click to add extra commands
    > Else
    > > Instructions here
    > > Empty line
    > end

    As you can easily imagine if you have very few instruction for each choice it means having a lot of empty lines and your event becomes incredibly big.

    If you use script calls instead of normal event commands it looks like this:
    Code:
    if condition
      instruction_block
    else
      instruction_block2
    end
    As you can see there are no empty lines in this case. This reduces your event length a lot making it easier to navigate. However if your options are very similar to each other you might be able to use a different approach to achieve what you need. If you give us more details about yout event we might be able to help you in more efficient way.
     
    #6

Share This Page