Ok, so it seems to be very trivial and basic feature of most RPG maps that are being made, but I struggle with it and somehow I didn't encounter any tutorials about this one.

I have about 35 different locations in my map (areas between which the player can move only through certain locations/caves on cliffs and so on) and I want him to transit between them having displayed a message about the place he's entering at given moment and not going back to the previous area if he haven't went a bunch of meters forward. What am I doing wrong and why is it not working?

Trig 1:
'Transition Blocade' is Cleared.
'Player is in Edge Station' is Set.
Player 1 brings at least 1 Terran Ghost to 'Transition - Edge Station to Border Hills'.
- - -
Set 'Player is in Border Hills'.
Clear 'Player is in Edge Station'.
Set 'Transition Blocade'.
Move All Terran Ghost for Player 1 at 'Transition - Edge Station to Border Hills' to 'Transition - Border Hills to Edge Station'.
Preserve trigger.

Trig 2:
'Transition Blocade' is Set.
Player 1 brings exactly 0 Terran Ghost to 'Transition - Edge Station to Border Hills".
- - -
Clear 'Transition Blocade'.

Two identical triggers are made the other way around. Why is this not working? The Ghost just stays at the second location and is unable to get the triggers running the other direction. Thank you in advance!

The logic is sound (if the 2nd trigger is preserved) so it's likely a small mishap or something else interfering, so it would be useful if you posted the actual triggers (text trigs) or the entire map.

I can't really check the text triggers in SCMdraft, because the tree is buggy (just as it says), it doesn't load any triggers from the tree.
Ok, so preserving the second trigger was indeed an issue, but it doesn't work yet.





I tried to change the order of triggers, but it didn't do much. Now the ghost keeps switching between the locations, while I want him to not execute the entering trigger if he hasen't walked out of it first.

Waits like to cause a lot of problems and probably aren't necessary here. Also the second "clear transition blockade" has the same location as the first one. Was that a mistake in pasting the triggers here, or is it actually "Transition - Edge Station to Border Hills" and not "Transition - Border Hills to Edge Station" ?

Ok, I deleted waits. Also this was only a mistake while pasting the triggers, in my map it's done the right direction. Still, the ghost keeps just switching between both positions into infinity.

Ah, I think I figured it out. If the ghost isn't somehow in both locations at the same time, the switch gets cleared. Instead, combine the triggers to:


Or alternatively, you could keep them separate (as it would be easier to expand to the 35 or whatever transition areas you said you have) by using the switches:





EDIT: Sorry, I think I got the switches reversed. It should be fixed now.

Post has been edited 1 time(s), last time on May 20 2017, 5:37 pm by FaRTy1billion.

Thanks, now it works perfectly fine (after upgrading the triggers a little bit - for reasons unknown I need to use the action "center view" twice in one trigger for it to center the location perfectly on the transition-locations, but it won't be much of a problem.
Will that be okay to use this thread as a thread for all future questions about the triggers in the map I'm making, or will I have to make a new thread every time? I am almost sure there'll be plenty of those.

Thanks, now it works perfectly fine (after upgrading the triggers a little bit - for reasons unknown I need to use the action "center view" twice in one trigger for it to center the location perfectly on the transition-locations, but it won't be much of a problem.
Will that be okay to use this thread as a thread for all future questions about the triggers in the map I'm making, or will I have to make a new thread every time? I am almost sure there'll be plenty of those.

EDIT:
Well, unfortunately making next triggers for the other transition-locations it happens again - ghost keeps switching between Border Hills and Edge Station. The equivalents of triggers 2 and 4 for the other transitions are the cause of it.

Sorry for multiposting, I hope someone can delete my previous messages.
So I've done these triggers, which in theory should work well and I they did when I got only those four, but as I made more such triggers for other transitions between different locations, those do not function anymore. This pattern of 4 triggers was made for any other transition in the other locations, but ghost just enters the Border Hills, and then immediately goes back to Edge Hills, where he stays (which means the trigger somehow works fine only in one direction), and after walking out of the transition location and walking into it again, he does the same thing. Those four triggers on their own work perfectly, but they stop doing so when identical triggers for other locations are made, but I don't understand why, since the conditions are so specific and it's impossible for switches of the other triggers to be triggered all on their own by anything. Help?









Post has been edited 5 time(s), last time on May 24 2017, 7:41 pm by Ghoster.

This is entirely fine if you come back a few days later with new information.

This is very confusing. Somehow the "Player is in Edge Station" switch is not being cleared when entering Border Hills. No other triggers in the game are interacting with those switches. Maybe someone is able to create such triggers, which will allow to transition between locations this way? I'd be very glad (and, of course, I'd be ahead with my map, which I'd like to share with the community once it's done.

You need to figure out which trigger isn't running to fix this. I would recommend posting the map and/or the text triggers.

Ok, so this is the map file.
Obviously all the triggers are running, because the ghost does change his position.

Frankly, I don't know why it's not working. It looks like it should work, but your process is so convoluted with switches that it's just not working.

This works though:



You're making this so much harder on yourself by using switches and trying to lock the player down to a location.

Also, consider instead of using locations, try using a burrowed/cloaked unit. Ion cannons can actually be completely cloaked, take up little space, and they'll never move. Their hitbox is also exactly the placement size, so it's a bit easier to place. Otherwise you can use a burrowed defiler at the location too.

Well, the problem is, that I need Player to activate those switches "Player in X", because player entering those locations activates and disactivates many different events. Above that I tried to use the "3 trigger option" that was mentioned above, and it worked fine until I realised that there can be only 16 condition in a trigger. This is crucial, because there's about 30 locations on the map, so if I'll run out of place, making second similar trigger for the blocade release start to interfere with the first one switching the blocade to clear, just because player isn't in one of the second 15 locations.

Post has been edited 1 time(s), last time on May 26 2017, 6:51 pm by Ghoster.

Switches are just an amalgamation of conditions.

For example, if you set A = B and B = C, A = C.

Let's say you have 2 triggers:
If player 1 brings 1 ghost to location 1
then set switch 1

If switch 1 is set
then do action

So why can't you do this?
If player 1 brings 1 ghost to location 1
then do action

My third recommendation was to remove the locations entirely and use a burrowed/cloaked unit to set/clear the blockade. This is simpler in the long run and is quite expandable without the need to make any additional trigger changes. This is the most logical method and the simplest to trigger. It's obviously not the most optimal, especially if you have detection, however there are ways to get detection of a a player without giving vision and without using a detector (though some units may flicker) so long as you don't use blind.

Additionally, switches are just bits. They're somewhat useful, but infinitely inferior to Deaths of unused units. They can be bits, but they can store additional data, organized into matrices via players, and they can be exclusive (each location is assigned a number rather than a bit, which means that it's impossible to mess up and be in 2 locations at once) which makes troubleshooting easier.

For example, what if you use Deaths of cantina to keep track of where the player is (if you don't want to use that giant location and a bring ghost condition) and deaths of cave to keep track of where the player was? Note that I'm writing these triggers manually, you may need to edit them to fix them.



Originally I was thinking that figuring out where you were would be useful, and indeed it can be. You can store the blockade switch in that by adding 101 or 102 to the previous location and removing 100 when you're no longer on the location. Travel should only be possible if you're under 100 deaths. Additionally, switches are global, whereas with deaths, you can use "current player" and have each player store their own switches.

There's also a third option for clearing the blockade using a single location: center a location on the unit when the unit is NOT in the location, meaning it's moved, and clear the blockade switch. I would recommend migrating to a death counter blockade though, so you can have varying levels of a blockade: 1= normal blockade. 2= super blockade that can't be removed until you defeat a boss/complete a quest. 0=no blockade.

Hopefully this all makes sense. Let me know if you have any questions.

I cannot stress enough how much better the death counters are for data manipulation compared to switches. Like rockz said, you don't need to adjust the trigger to account for used-up switches since 'current player' death counter specifically saves data for just that one player.