More Conditions

[Shaz]

I'm creating a script that lets you add many more conditions to an event page than what's currently allowed. I'd like feedback on what sort of conditions would be most useful.

Things like:

- more than 2 switches

- switches turned OFF

- more than 1 variable

- variable equal to something

- variable less than something

- if party has a certain number of a certain item

- if party has a certain amount of gold

- if a particular person is in the party

- if party has a certain weapon or armor item (or a specific quantity)

What other things would you LOVE to see in the condition list on event tabs, but have had to resort to event commands for conditional processing or script calls?

 

[Tsukihime]

lol how about "the ability for me to make a script call"

 

[Shaz]

That'll be there

 

[Espon]

Whether or not a certain button is pressed.

 

[Tsukihime]

I'm curious how you are implementing the conditions. I've written a script for the same idea because the default page conditions are just too limited, but my implementation puts restrictions on how you can write your events.

Info here: http://www.rpgmakervxace.net/topic/4174-event-extend-script-conditions/

 

[Shaz]

What I'm really after is a list of the things you wish for most often - what are the common things that you're always using in conditional branches or script calls because they're not available in that list? This list will allow me to add shorthand versions so you're not typing everything out in full for the more frequently used conditions.

@Tsukihime, I'm using comments and abbreviating terms (using \s instead of $game_switches, for example). You add your conditions to a multi-line comment (can use two or more comments if one isn't enough). It puts them all together, converts the shorthand to the correct terms, then eval's the combination. So it's building its own script call, or you can put in your own script call.

And it can be used instead of, OR in addition to, the existing conditions that are already provided on the event tabs.

You'll be able to do something like:

$game_actors[1].hp > $game_actors[2].hp

if you wanted to, even if I don't specifically set up shorthand codes for it.

 

[Espon]

What I'm really after is a list of the things you wish for most often - what are the common things that you're always using in conditional branches or script calls because they're not available in that list? This list will allow me to add shorthand versions so you're not typing everything out in full for the more frequently used conditions.

Button presses are one of those things. I can think of useful examples like holding shift when pressing against or hitting the action button to move a block, having a common event trigger when a key is pressed, or cracked floors that cave in depending on whether or not the player is holding Shift and dashing...otherwise I gotta stick it all in a conditional or have parallel processes run that constantly checks if a button is being pressed (which I use for L and R to activate things like the map and quick items).

 

[Shaz]

Everything you can do in the Conditional Branch or set as a condition via a Call Script event, you will be able to do. So you can set Input.press?(x) as a condition to check for a button being pressed.

 

[Bird Eater]

Oh haha, I actually made this exact thing a month ago, but it's a little ****ty and custom so I didn't release it

I'd suggest a multiple self-switch requirement. Goes great with a 'more-self-switches' script!

 

[Victor Sant]

I did something similar, but i only used script calls, in the end they can resume any other functions.

 

[Lunarea]

The only one I can think of right now is a conditional branch for the party leader. Currently, the conditional branch allows you to check if a character is in the party, but not if they're the leader. It's doable via variable manipulation (and I'm sure there's a script input equivalent), but an easy shortcut would probably be nice.

 

[Shaz]

Maybe not on the button down question. I've been testing, and $game_map needs to be refreshed for these conditions to be tested. Holding a button down doesn't force a refresh. I'll keep looking though.