State change not working from a common event

[Lordkazar]

I tried to make an item that would change the state of a certain part member(prof) using a common event.
However it doesn't seem to be working.

Originally I wanted it to check a variable and assign a state based on that number.
When that didn't work i made the bare bones version pictured below, which still failed.

is this a bug or did i do something wrong?


Also i have noticed that if i use more than 2 common events in an item some times one of the events wont run.




Thanks
 

 

[Andar]

your common event works, but probably not in the way you wanted.


It will always add the state to the actor named "Prof", no matter who the skill user is - common events are called outside the action sequence (that is also the reason why only one of them works per skill) and will always ignore scuh things like user or target.


To make the common event affect the target, you need to identify the target first.


One way to do this is to place an invisible state on the target by the regular effects, and then have the common event check which actor has that state before removing the targeting state and applying whatever else you want.

 

[Lordkazar]

I want it to add a state to only actor "prof" the problem is that it dosn't add the state to him.

 

[Shaz]

Are you sure you're calling the right common event?  

The one in your Common Events screen is called "A Node" - the one in your item effects is called "Node".  That seems to imply that you have two common events set up, and the one it calls is not the one you've shown us.

 

[Lordkazar]

yes just "nodes" was the original more complex try and "A node" is the simple version. I must of grabbed the wrong screen shot. but i just doubled checked both versions just in case neither is working for me. I will try a script call and see it it works that way.

 

[Andar]

Another thing that might have gone wrong: you can only call events that have no trigger. As soon as you set a trigger to a common event, all calls to it will fail.


If that is not the case, please give us the screenshots again - and make them full screenshots of the windows, not cropped like above, to prevent similiar mistakes.


You also might add a show text to the event to identify if the event is called and the state is the problem or if the event isn't successfully called.

 

[Lordkazar]

No trigger set, i will try to see if a custom script works tonight if not i will post screen shots. thanks

 

[mrcopra]

No trigger set, i will try to see if a custom script works tonight if not i will post screen shots. thanks

can you give us state screenshot 

and your original node event

 

[Lordkazar]

I go it to work with scripts.
thanks for the help and info.
I turned it into a single event that called a script that did everything I needed it to.

 

[Ansilvund216]

I go it to work with scripts.
thanks for the help and info.
I turned it into a single event that called a script that did everything I needed it to.

what script did you use?