RPG MAKER 2003/ HOW WOULD I DO THIS IN MY GAME?

Huh? You don't even need the Parallel Process (or for that matter, a switch). Just make it part of the event in question, like this:

If Possesses Item
(ThisEvent, away from hero)
Else
If Actor Knows Strength
(ThisEvent, away from hero)
Else
(Blank)
End
End

Put this in the event, and make it Hero Touch instead of Action Key.

author=bulmabriefs144
Huh? You don't even need the Parallel Process (or for that matter, a switch). Just make it part of the event in question, like this:

If Possesses Item
(ThisEvent, away from hero)
Else
If Actor Knows Strength
(ThisEvent, away from hero)
Else
(Blank)
End
End

Put this in the event, and make it Hero Touch instead of Action Key.

Look up the DRY method; a common event running as a PP satisfies the conditions of DRY programming, which is pretty much how you should be trying to do as much code as possible. Saves you having to go back and fix every single related event if you decide to change the conditions under which you can push that rock and reduces the amount of overhead.

Also a note, should probably toss a Wait 0.0 before or after the conditional statement I put up earlier - it'll ease the burden of the process on the engine.

author=Travio

author=bulmabriefs144
Huh? You don't even need the Parallel Process (or for that matter, a switch). Just make it part of the event in question, like this:

If Possesses Item
(ThisEvent, away from hero)
Else
If Actor Knows Strength
(ThisEvent, away from hero)
Else
(Blank)
End
End

Put this in the event, and make it Hero Touch instead of Action Key.

Look up the DRY method; a common event running as a PP satisfies the conditions of DRY programming, which is pretty much how you should be trying to do as much code as possible. Saves you having to go back and fix every single related event if you decide to change the conditions under which you can push that rock and reduces the amount of overhead.

Also a note, should probably toss a Wait 0.0 before or after the conditional statement I put up earlier - it'll ease the burden of the process on the engine.

You are totally right about the dry coding bit, however I would do it somewhat differently to avoid lag issues. I would advice to call a common event, so you are able to change the code if there is an bug in it, but still avoid lag issues due a constantly looping parallel event (yes a 0,0 wait would also work, unless you have dozens of these running at the same time (I would probably stack all those parrallels together, but w/e :p).

So my advice:


Create an event:
Give it the boulder graphic.
Make it hero touch.
In the code you put this:

<>call common event (boulder push)

Now go to your database.
Go to the common event tab.
Place this code in the common event slot you created earlier:

<>If Possesses Item
<><>
<>Else
<><>If Actor Knows Strength
<><><>
<><>Else
<><><>Jump to label 1
<><>end
<>End
<>If Hero faces up
<><>Move event up
<>end
<>If Hero faces right
<><>Move event right
<>end
<>If Hero faces left
<><>Move event left
<>end
<>If Hero faces down
<><>Move event down
<>end
<>Label 1

Btw, Bulmabriefs, why leave an empty else case if you don't do anything with it? As in how you put an else case after checking if the skill is aviable or not. People commenting about my two empty else cases: it would take an extra label if I wouldn't do it this way.