2 replies to this topic

[Jenny]

i have this screen where the objective is to push the blocks into the holes so you can create a path to proceed. i need the blocks to stay in the holes when you leave/re-enter the screen for this purpose.

 

this is "technically" possible in engine but it restricts you to one possible solution. i need the player to be able to push any block in any hole.

[Deedee]

Okay so this is a bit experimental because it uses a feature I never used before and does some complex stuff, so please let me know if it breaks.

The Script

ffc script PermanentBlockHole
{
	void run()
	{
		if (Screen->DataSize < 1) 
		{
			Screen->DataSize = 1;
			Screen->Data[0] = 0;
		}
		int numholes = 0;
		int holes[176*3];
		int holevalue[176*3];
		int combos[176*3];
		if (Screen->Data[0] > 0)
		{
			for (int i = 0; i < Screen->Data[0]; ++i)
			{
				combos[i] = Screen->Data[1 + (i*4)];
				int replayer = Floor(Screen->Data[2 + (i*4)] / 176);
				int repcombo = (Screen->Data[2 + (i*4)] % 176);
				mapdata m = Game->LoadTempScreen(replayer);
				m->ComboD[repcombo] = Screen->Data[3 + (i*4)];
				m->ComboC[repcombo] = Screen->Data[4 + (i*4)];
			}
		}
		for (int k = 0; k <= 2; ++k)
		{
			unless (k == 0 || Screen->LayerMap(k) > 0) continue;
			mapdata m = Game->LoadTempScreen(k);
			for (int i = 0; i < 176; ++i)
			{
				if (Screen->Data[0] > 0)
				{
					for (int j = 0; j < Screen->Data[0]; ++j)
					{
						if (m->ComboD[i] == combos[j])
						{
							m->ComboD[i] = m->UnderCombo;
						}
					}
				}
				if (m->ComboF[i]== 91 || m->ComboI[i] == 91)
				{
					holes[numholes] = i + (k*176);
					holevalue[numholes] = m->ComboD[i];
					++numholes;
				}
			}
		}
		if (numholes <= 0) Quit();
		while(true)
		{
			for (int i = 0; i < numholes;)
			{
				int layer = Floor(holes[i] / 176);
				int combo = holes[i] % 176;
				mapdata m = Game->LoadTempScreen(layer);
				if (m->ComboD[combo] != holevalue[i])
				{
					Screen->DataSize+=4;
					Screen->Data[1 + (Screen->Data[0]*4)] = m->ComboD[combo]-1;
					Screen->Data[2 + (Screen->Data[0]*4)] = holes[i];
					Screen->Data[3 + (Screen->Data[0]*4)] = m->ComboD[combo];
					Screen->Data[4 + (Screen->Data[0]*4)] = m->ComboC[combo];
					Screen->Data[0]++;
					holes[i] = holes[numholes-1];
					holevalue[i] = holevalue[numholes-1];
					numholes--;
				}
				else 
				{
					++i;
				}
			}
			if (numholes <= 0) Quit();
			Waitframe();
		}
	}
}

Place the ffc on the screen you wish to have block holes remembered on, make sure to check the "run at screen init" flag. All block holes need to be present on the very first frame of the screen, so things that cycle into block holes won't work, and secrets that turn into block holes won't work unless you reload the screen after triggering it or it's a carryover. All push blocks and the combo afterwards (the combo of the block in the hole) need to use a unique combo that isn't present elsewhere on the screen, and like block holes they need to be present on the very first frame of the screen so the script can find it and remove it (though unlike block holes, blocks that are revealed by triggering a secret don't need the screen to be reloaded for them to save, just as long as whenever you return the script can find them on the very first frame).

2.55 obvously; I don't know which alpha added the thing I'm using, but it should work on latest at the very least.

The big thing preventing built in 2.55 features from doing this is there's no way to know which block hole was filled in; you can tell which block was pushed in because it'll always turn into the next combo in the list, but not which block hole.

[Jenny]

Appears to work without issue. Much appreciated!!