Counter

Well, I think that the only fix that doesn't require coding is to use a complex set of triggers that center around a RoundRobin instead. Let me see if I can explain this:

You have the two triggers that should open the mover. Give them different tags and set them both to the OtherTriggerToggles state. Each trigger has the event name of a dispatcher, which first turns that trigger off and then triggers a RoundRobin. The RoundRobin has bLoop set to True and has a blank event in the first OutEvents blank. The second OutEvent blank triggers a third dispatcher with the following events: (1 and 2) turn the original triggers back on, and (3) triggers the mover.

I suggest you copy that to a text file and try to work with it from there.

Oh, as for the question about the movement of the mover, I have to say that I think it's just the way a mover works. Sorry.

Maybe I can try to do this graphically. Check out what I whipped up with MS Paint real quick.

In this image, the 0's, 1's, and 2's indicate blanks for actors with multiple event values.

Yes, at the tail of each arrow, you have an actor with a certain Event name. In the case of Dispatchers and RoundRobins, you put this in the marked OutEvents label. At the head of each arrow, you have an actor whose Tag matches the Event at the tail.

So, to answer your question, you fill in the tags of the actors that you want the Dispatcher or RoundRobin to trigger.

Now, to clarify things, I'll give quick explanations of Dispatchers and RoundRobins.

A Dispatcher is a single actor that is used to trigger many things all in one action. You can also put time delays to make it wait a short time before triggering the next Event in its list, but you don't need to do that here. So, one of these Dispatchers will instantly trigger ALL of its events when something triggers it.

A RoundRobin has a set of events like a Dispatcher, but it works more like a switch. The first time you trigger a RoundRobin, it will trigger whatever OutEvents[0] matches. The second time, it will trigger OutEvents[1], and so on, until it gets to the end of its list. At that point, it will go back to the first event if bLoop=True, or it will shut down if bLoop=False.

So, here's an in-depth description of what this complex trigger machine does:

The player shoots either one of the Triggers, and it triggers a Dispatcher. That Dispatcher does two things: it triggers the RoundRobin, and it turns off the Trigger that was shot. This is so that the player can't just shoot the same Trigger twice to make the Mover work.

What does the RoundRobin do? Nothing, since we intentially left OutEvents[0] blank.

Then the player shoots the other Trigger, and something similar happens. That Trigger's Dispatcher triggers the RoundRobin and turns off the shot Trigger.

Now what does the RoundRobin do? Well, we made OutEvents[1] the tag of that last Dispatcher, so that's what becomes triggered next. That Dispatcher turns both original Triggers back on again, and then it triggers the Mover.

Click to expand...

I hope I'm not bombarding you with too much information. I really am trying to be helpful.

Okay, I think I know the problem. It looks like you actually have to trigger something with the OutEvents[0] blank.

So here's what you do. For that blank, fill in the Event of "MakeNaliFriendly", and then put a MakeNaliFriendly actor (a type of Keypoint) in your level somewhere. That way, the RoundRobin actually triggers something with the first blank. I assume there are no Nali in your level, right?

Cool! I'll have to remember that one, because I was devising that little plan as I went.