Double trouble

[Avator]

[Solved] Double trouble

In my map I made a few nice cinematics. However sometimes (completely random i think) the cinematic repeats itself after s few seconds. This means that you have a command, then the next command and then the next one, and a few seconds after the first command, it repeats that command and all commands following. This is very annoying, because it ruins everything I made to make it a special good looking cinematic.

It is noticeable that this (when it happens) happens at a certain moment in the same cinematic. There is nothing in the trigger that could cause the stuff to happen again. What can it be?

 

[HappyTauren]

Turn off the trigger at the moment it is started.

• Events
• whatever events
• Conditions
• whatever conditions
• Actions
• Trigger - Turn Off (This trigger)

 

[Avator]

Now the trigger doesn't activate at all. I placed the Turn Off command halfway the cinematic trigger (at the point where the problem starts) and it shuts down the entire trigger.

It should activate when the life of a unit get below 40, but I hit this unit with another unit, the life of the Event unit becomes 20 (less then 40), and nothing happens.


EDIT: This cannot be happening...
Ever since I placed that Action the entire trigger doesn't activate anymore, even after I removed the command!

 

[Zinive]

This sounds so odd, can you write down the trigger please maybe then we find something out.

 

[Avator]

I think my whole map is corrupted or something. I have this problem, my custom models won't show, my imported files all have 0 KB size if I close and open the Import Manager and I just discovered that when I make a custom script to destroy my variables, I get a error when I want to test or save my map! It could also just be a big coincidence. I'll attach the complete map, then you can see all triggers used and maybe discover stuff of those other problems.

 

[Zinive]

Ok i finally found a way to make this work.

create a new trigger

• Palmasis check
  • Unit - Palmasis life < 40
• condition
• (none needed)
• Action
  • Trigger - Run Palmasis killed (ignoring conditions)
  • Trigger - Turn off (This Trigger)

Then delete all those destroy variables functions i thing their causing also trouble.

It should work now.

Not to offend you but your triggers are "messy".
You are using a lot of useless triggers like wait directly behind a unit transmission (this trigger contains already a wait).
You are using by far too much variables their is no reason to give a region to a variable.
Also those Path blockers in the woods i don't see any reason for them.

But i kinda like that map the fight is fun and the story sounds promising.
Don't stop making this campaing

 

[Avator]

I know my triggers are pretty messy. I just use common sense to make them work and test it over and over again to perfectionate the timing.

I thought locations cause leaking too, but right now I'm going to delete all Destroy Variable commands, make the map and at the end ask for someone to make the map leak-proof. It's too annoying for me and I defently don't have enough knowledge about it.

The path blockers at the edge of the forest is to prevent spoilers of the church cinematic (after killing Palmasis) as soon as I've messed with settings enough to find out how to make the map and minimap entirely black, so you can't see the trees, church, graveyard and other stuff that you don't see when it comes within sight. The pathing blockers between the trees that 'mark the road', that is just to be 100% sure that people dont go between trees and get stuck or something. That would pretty much be unfair especially with Palmasis' Flame Strike skill and you have nowhere to go

Thanks
All info about this project can be found on the link in my signature. I hope you'll enjoy the campaign when it's finished. Just keep an eye out on that link and you'll be up-to-date with the entire campaign.


EDIT: It helped me get the trigger working again, so I'm able to test it for the modification I'm going to do on that trigger to prevent those bugs and stuff. Problem solved!