7 replies to this topic

[Twilight Knight]

Hey all

One thing which has always bothered me about cutscenes is that Link can slash his sword, or worse, drop a super bomb during a cutscene.

 

What would be the recommended away to prevent this?

 

I know it's possible to disable items on certain Dmaps, but that changes the item the player has selected when those items are enabled again.

 

Then there is also the possibility to freeze Link and enemies with the Screen Freeze (Except FFCs) combo type. But if that is enabled, the string won't play.

 

I can think of a way to make that work. Have a ffc script Waitframes() for a couple of frames, enough to let the string play, and then freeze the screen long enough for the timed warp to kick in. It should work since I have the "Messages Freeze All Action" quest option enabled.
 

 

But I was wondering: do you guys have any suggestions regarding this matter?

Edited by Twilight Knight, 11 December 2020 - 04:59 AM.

[Emily]

With a script, `Link->SwordJinx` and `Link->ItemJinx` - or just directly prevent the keypresses every frame.

[Deedee]

NoAction(); every frame, from std.zh, or WaitNoAction(); which combined NoAction with a Waitframe.

[Avaro]

https://www.purezc.n...=scripts&id=261

[Twilight Knight]

Awesome, thank you everyone!

That script of yours should do the trick Avaro, thank you!

[Timelord]

Oh lordy... 
 
There are a lot of ways to disable the change of the selected item. To be frank, if you absolutely want to disable a lot of stuff, you can use Game->Suspend[] to halt execution of game code, instead of doing these obtuse things, if you are on 2.55. 
 

screen script suspendstuff
{
	void run()
	{
		Game->Suspend[susptLWEAPONS] = true;
		Game->Suspend[susptLINK] = true;
		Game->Suspend[susptCOLLISIONS] = true;
		for ( int q = susptNPCSCRIPTS; q < susptFFCSCRIPTS; ++q )
		{
			Game->Suspend[q] = true;
		}
	}
}

screen script un_suspendstuff
{
	void run()
	{
		Game->Suspend[susptLWEAPONS] = false;
		Game->Suspend[susptLINK] = false;
		Game->Suspend[susptCOLLISIONS] = false;
		for ( int q = susptNPCSCRIPTS; q < susptFFCSCRIPTS; ++q )
		{
			Game->Suspend[q] = false;
		}
	}
}

Put the first on the screen with the cut-scene, add or remove entries as needed from the suspend types enum (std_constants, line 2900 in <std> v1.7109), and restore those engine sections on the screen visited after the cutscene. These literally turn off components of the engine, and you can suspend other things such as combo scripts, conveyors and other elements that interfere with your cut-scene. 

[Twilight Knight]

Thank you Zoria, I didn't even know those kind of things were possible now!

[Emily]

One problem, @Zoria; 'susptLink' being on prevents warps from working.