marbleman on 10/9/2018 at 08:25
Quote:
Any other FMs that use them?
Second mission of Death's Cold Embrace has a sliding banner near the crypt entrance.
Thief 2X has banners that flutter when you come close to them.
vfig on 10/9/2018 at 12:57
marbleman: thanks very much! I completely missed the sliding banner when I played DCE, I just immediately cut it down like a barbarian! :D
I've dug into those FMs to see how they work. I've also found there's a custom sliding banner by Schwaa in the Thief Object Repository that works in a similar way.
T2X's fluttering bannersT2X's banners flutter when you walk into them:
[video=youtube_share;UQ74I5ocz3I]https://youtu.be/UQ74I5ocz3I[/video]
A Touch stimulus receptron spawns a bannermarker that is a PotionStim source; the banner's PotionStim receptron activates its ModelTweq, and the marker's PotionStim receptron destroys itself:
Inline Image:
https://i.imgur.com/vJqGL7p.pngSchwaa's sliding banner(
http://spirited-tech.com/thief/2015/05/16/sliding-banners-by-schwaa/) Schwaa's sliding banner is activated by a switch.
[video=youtube_share;Zje7s76iPYw]https://youtu.be/Zje7s76iPYw[/video]
The readme decribes a simple and easy scripting setup: it uses a ModelTweq, and the TweqOnOff script to slide aside. I'm not sure with this setup how to make it close again:
Inline Image:
https://i.imgur.com/M2lHt93.pngDCE's sliding bannerDCE's banner slides aside when frobbed, then slides back when the secret switch is frobbed.
[video=youtube_share;vVLM3Ph5KSw]https://youtu.be/vVLM3Ph5KSw[/video]
It's a complex but clever setup: the sliding banner generates a FrobStim stimulus when frobbed.
Its four FrobStim receptrons activate the ModelTweq; add the M-BannerOpen metaproperty for its behaviour when open; copy the CollisionType property so it no longer collides, then adds the FrobInert metaproperty so it can't be frobbed again yet.
The switch uses an NVRelayTrap to send a FrobStim stimulus back to the banner. Then the M-BannerOpen metaproperty's four FrobStim receptrons activate the ModelTweq; remove the M-BannerOpen metaproperty again, copy the CollisionType property from the archetype so it's solid once more, then aborts so the banner's receptrons don't react to this frob. The same switch also activates the banner's NVMetaTrap script, which removes the FrobInert metaproperty.
Inline Image:
https://i.imgur.com/ATevuCj.png