Player Cancels cinematic Transmission

[Marshmalo]

Hi just a quick question,

I have a cinematic transmission that plays at map startup, the problem is when one player presses ESC the transmission cancels for all players.

If I trigger it so the transmission plays individually for each player, then if one player presses ESC it won't cancel for all players? It will just cancel for that individual player?

 

[pOke]

I'm not sure if you can/or it would be a good use of time to try and GetLocalPlayer numerous Cinematics, instead I would recommend you either
Periodically send the proper transmission every .1 seconds in case someone tries to skip. OR Even better... Look here

http://www.hiveworkshop.com/forums/cinematics-268/tips-tricks-cinema-39854/

And see how to disable the skip cinematic button.
(You can re-enable it later)

 

[PurgeandFire]

It will cancel it for all players, so long as someone has received a transmission. In fact, you could even show a cinematic for one player, and some troll who doesn't have the cinematic could spam esc to mess up that guy's cinematic.

The best route is probably to just ignore the esc commands by disabling transmissions in general (see pOke's link). You can trigger your own Esc thing, if you want too. Theoretically, you could use the script in the link and then combine it with a custom esc event that does this:

if GetLocalPlayer() == GetTriggerPlayer() then
    call StopSound(bj_cineSceneLastSound, false, true)
    call EndCinematicScene()
endif

I haven't tested if it causes any issues sync-wise, though. I imagine it wouldn't, since it is just a matter of displaying the transmission.

 

[WaterKnight]

Kill the blizzard.j trigger that does this.

• Custom script: call DestroyTrigger(bj_cineSceneBeingSkipped)

 

[Marshmalo]

Kill the blizzard.j trigger that does this.

• Custom script: call DestroyTrigger(bj_cineSceneBeingSkipped)

o0 I like the look of that, so basicaly they can't press ESC to cancel it?

I will try this thanks!

 

[PurgeandFire]

^It will allow that, but only after you have made a transmission. (TryInitCinematicBehaviorBJ() has to be called first, otherwise it is destroying a null trigger)

So basically, you would make one transmission, put that code afterward, and then it'll disable the esc-skipping feature. (to reenable in that case, you would set bj_cineSceneBeingSkipped = null)

If you want to disable it on map init, see:
http://wc3jass.com/5248/snippet-disable-transmission-skip/msg40200/topicseen/#new

 

[WaterKnight]

I see it tries to reinit the trigger everytime, so it would have to be after every transmission line. Therefore you should set

• Custom script: set bj_cineSceneBeingSkipped = CreateTrigger()

a dummy value, so the initer thinks the trigger would already exist. Or just do what PurgeandFire suggested.

 

[Marshmalo]

Kill the blizzard.j trigger that does this.

• Custom script: call DestroyTrigger(bj_cineSceneBeingSkipped)

I tried this as you instructed and it seems to work great1 Just tested it and I can no longer skip any cinematic transmittions! +rep for you ty

 

[WaterKnight]

Yeah ok, because the initer compares bj_cineSceneBeingSkipped to null. If you destroy the trigger, the variables still point to the destroyed object and not to null.