Showing a Trail Through Common Events

[SkarX5]

Hi, Skar here.

I need some help. In my game their will be a feature I named "Void Vision". What it does is make a trail of black visible when the ability is used. However, I want it to make the user can only use for a short time then have to wait before doing it again, so you don't have it on 24/7. I tried doing this via Common Events (Setting it to parellel process) but when I try to make it where you can only use the ability for 2 seconds and then have a 10 second cool down, it makes it to where the player can't move until the cool down is over.

 

[Andar]

Place screenshots of your events.

If the player cannot move, chances are good that you either used an autorun (instead of parallel process), called a parallel process CE by event command (instead of controlling the switch for that parallel common event), or placed a loop/wait inside the parallel process.

 

[SkarX5]

Heres the screen shot of the common event.



It's not still set on Parellel process. I set it to none and activate it with a skill, but it still makes the character stop moving.

 

[Celianna]

It's because if you call a common event, it will run through all of the commands and freeze the player, disregarding the fact it's set to parallel process. You are calling the common event when you are using the skill.


To circumvent this, you need two common events. One common event is the one the skill will call, and all it does is turn on the switch that will activate the second common event. Your second common event will deal with all your void vision stuff, and will run based on the switch you turned on in the previous common event (don't forget to set it to parallel process).


To sum it up:


Make void skill call common event 1.


Common event 1 turns on Switch 1.


Common event 2 is a parallel process that runs on Switch 1, and will deal with the void vision and wait commands. At the end of the event, turn off Switch 1.

 

[SkarX5]

It's because if you call a common event, it will run through all of the commands and freeze the player, disregarding the fact it's set to parallel process. You are calling the common event when you are using the skill.

To circumvent this, you need two common events. One common event is the one the skill will call, and all it does is turn on the switch that will activate the second common event. Your second common event will deal with all your void vision stuff, and will run based on the switch you turned on in the previous common event (don't forget to set it to parallel process).

To sum it up:

Make void skill call common event 1.

Common event 1 turns on Switch 1.

Common event 2 is a parallel process that runs on Switch 1, and will deal with the void vision and wait commands. At the end of the event, turn off Switch 1.

This worked! Thank you so much. This problem was solved.

 

[Shaz]

This thread is being closed, due to being solved. If for some reason you would like this thread re-opened, please report this post and leave a message why. Thank you.