Now that's a weird thing...

Depending on where I am, I use 2 PCs for mapping : one with Windows 7 Pro and a laptop with Windows Vista Home which is used only for mapping and testing. Both have the same version of SCM Draft (0.8.0), yet some weird stuff is going on the one with Vista.

I already had figured out SCM Draft wasnt bahaiving the same way. A first main difference without consequences is that when you move triggers / trigger lines up and down, on W7 it forces the view to where the trigger / trigger line last was while you clicked on it. So in a list of 64 actions, if you spam the move up button to bring an action to the top of list, you won't see it going up (unless you click again on the action).
On Vista, it stays centered on the selected action and the view follows the line.

The major issue I had is another story, it made the map crash at the first trigger cycle, and when it didn't, all kind of shit fell upon my testing players due to 13 missing code lines (see bellow).

For some reason, when I edited the map on the WinVista PC (and it does it every time now), SCM Draft replaced this condition :

(Current Player has suffered at least 1 deaths of Terran Marine)
by
Memory at Death Table + 13 is at least 1

And it did it in the whole map.. This made SC crash.
But sometimes the condition (Current Player has suffered at least 1 deaths of Terran Marine) is just gone and just doesn't exist in the map anymore (which fucks triggers up pretty much). When I try to add the missing condition again, either in classic triggers or in Trigger Editor, the Death condition turns to the "Memory" condition as soon as I select the player, and if that player is something else than Player 1 to Player 11 (Current Player, Foes etc).

I don't really understand why this particular condition involving the Terran Marine though..
I have tons of "at least 1 deaths" conditions in my map involving other units and they are all normal.

If I edit the map on the Win7 PC however and save it from there, everything is fine.

I don't use EUDs.

Weird isn't it ?

Post has been edited 1 time(s), last time on Sep 12 2016, 11:27 am by Stranger.

In the classic trigger editor, using current player instead of a single player changes the trigger to the memory table (apparently used to create EUDs). My solution was to manually add it in using text triggers, but apparently that's not working out for you. Make sure you have the latest available version (or settle with the one in the final call thread) and see if this issue persists with other maps, not just the one you're working on now.

Edit all other parameters before editing the player. That will keep it as the normal death condition. Or just use the specific player and not current player.

It's a feature not a bug. Simply avoid it by changing another attribute of the trigger first.

Use ScmDraft 0.7.3 and try if it "repairs" your map. It doesn't have that feature yet.

Thanks for those tips

Yeah, I figured out that changing the other parameters doesn't transform the condition. But then, the last parameter (Player) turned it to a memory condition again as soon as I put Current Player, Foes or All Players. But this seems a bit random, which explains that it only occurs now, knowing that I work like this for weeks or months.

For example, yesterday I did some mapping on the laptop, saved the map and thought : "Yeah, this just means I'll have to edit it with the other PC later, so the death conditions go back to normal and I can start the map." But Death conditions were actually good later when I checked

Yeah, since only Terran Marine death condition seems to be concerned, and depending on how it is going, I might affect the triggers individually to P1-P6 (instead of using Current player for all of them), as a last resort.

As long as all of the things were set before it changes to Memory, it should work correctly as a Death condition even if it is looks different.

Ooh, so that's why it worked without trouble last time, even though I was expecting it not to.

Good to know, thanks for the help