Changing spiny block ActAs causes its code not to run

[spooonsss]

On version 5.12, after initialization:

1. Open rom in LM, open Map16, change tile 2A0 ActAs to 290
2. Save Map16.
3. The tooltip for 2A0 shows the tooltip for 290 instead. In-game, 2A0 behaves like 290. GPS gets tile 290 from LM in-game -- the custom 2A0 block code is not run.

A callisto full rebuild fixes it. Changing the ActAs to a vanilla tile instead seems to work fine.

https://www.twitch.tv/drkrdnk/clip/BovineCourageousSalsifyDansGame-CdCxhDGi_1_KAAnc

[AmperSam-git]

This is normal. You can't make custom blocks act as other custom blocks, there isn't nesting functionality. The act as will simply make that tile use the target tile number's behaviour.

[spooonsss]

Hey Amper, I do think there is a problem here.

1. Try 1-3 and a full rebuild. The nested functionality works fine.
2. I really think that doing a full rebuild shouldn't change anything. It's not part of the usual workflow.

[AmperSam-git]

I'm not clear what the problem is. A full rebuild will reinsert all blocks and any map16 change will be overwritten since act-as is specified in GPS's list.txt–so the spiny block will be inserted once again as act-as 25. If you don't want that to happen you can remove the :0025 from the block in the list and it will keep your map16 edit.