Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[TheFlame52]

So the other day I was thinking about how dwarves walk by the top of waterfalls and get swept off. There must be some way to weaponize this. So here's what I came up with.

By the edge of the waterfall, build two bridges on either side of the stream that raise toward the waterfall, forming two walls that you can raise and lower at will. Then link them both to a lever. Flip the lever, raising both bridges. Next to this build a safe bridge for dwarves to cross. Link this to another lever.

When baddies come, simply flip both levers, causing the edge of the waterfall to become an available path and the safe bridge to raise. The baddies will cross the waterfall's top and be swept over. There they will either drown or be devoured by carp/alligators.

[☼!!Troll Fur Sock!!☼]

What about a bridge full of "dodge me" wooden spiked ball traps?

[GuesssWho]

Might want to pull the lever and then attach the new bridge to the same lever, so you only need one pull.

[Triaxx2]

Such simple solutions.

No.

Build a hard walkway x tiles from the waterfall. Divert the falls, and build a bridge reaching x-1 tiles, one z higher. When invaders, come, extend the bridge, and watch the pressurized water wash them away. Water triggered pressure plates linked to upright spike traps can also add entertainment. Especially if they trigger in sequence, forcing the enemies onto the walkway to escape them.

[Torrasque666]

Might want to pull the lever and then attach the new bridge to the same lever, so you only need one pull.

A lever has On/Off toggle. If you pull it once, toggling it to "On", and then attach another object to it, when the lever is pulled again, toggling it to "Off", the second object wont react, as it is being assigned to its "off" state rather than just being toggled.

Otherwords, build bridge 1, attach lever, pull(ON). bridge 1 goes up(ON). build bridge 2, attach to same lever, pull(OFF). bridge 1 goes down(OFF), bridge 2 doesnt react(OFF)

I've tried this before to make alternating paths, didn't work.

[joeclark77]

Might want to pull the lever and then attach the new bridge to the same lever, so you only need one pull.

A lever has On/Off toggle. If you pull it once, toggling it to "On", and then attach another object to it, when the lever is pulled again, toggling it to "Off", the second object wont react, as it is being assigned to its "off" state rather than just being toggled.

Otherwords, build bridge 1, attach lever, pull(ON). bridge 1 goes up(ON). build bridge 2, attach to same lever, pull(OFF). bridge 1 goes down(OFF), bridge 2 doesnt react(OFF)

I've tried this before to make alternating paths, didn't work.

FYI, floodgates are closed when bridges are open, and vice-versa.  Also, if you use a retractable bridge as a vertical 'door', the retractable bridge is "closed" when normal drawbridges are open.  Maybe one of these ideas would help you re-engineer your idea?

My take on this subject: it's kind of silly to weaponize the waterfall itself when you could so easily weaponize the cliff/chasm that is right next to it.  My idea for a future fort is to build my main entrance into the waterfall (using drawbridges that, when opened, divert the waterfall around the entryway and back underneath it onto its original course).  Invaders will enter by walking on a bridge over a big drop.  This could be exploited a number of ways: dodge traps to send enemies into the chasm, retracting trapdoor bridges, siege engines sweeping the bridge from the opposite cliffside, etc.

[Triaxx2]

Doors also operate in alternate states to bridges.

[Thormgrim]

I sort of like an idea of using a retracting bridge over a lower path.

The retracting bridge is on top and basically extends the waterfall out over and past the lower bridge.  The lower bridge leads to the entrance.

When the upper bridge retracts, the waterfall essentially moves n tiles upstream and now dumps straight down onto the lower path.

I'm gonna try that!

[Quietust]

Might want to pull the lever and then attach the new bridge to the same lever, so you only need one pull.

A lever has On/Off toggle. If you pull it once, toggling it to "On", and then attach another object to it, when the lever is pulled again, toggling it to "Off", the second object wont react, as it is being assigned to its "off" state rather than just being toggled.

Otherwords, build bridge 1, attach lever, pull(ON). bridge 1 goes up(ON). build bridge 2, attach to same lever, pull(OFF). bridge 1 goes down(OFF), bridge 2 doesnt react(OFF)

I've tried this before to make alternating paths, didn't work.

There's actually a way to make it work: always pull the lever TWICE. The result ends up working as follows:
Brige 1 is ON (raised), Bridge 2 is OFF (lowered), Lever is OFF
Pull lever (OFF -> ON), bridge 1 does nothing (already ON), bridge 2 starts raising(OFF -> ON), pull lever again (ON -> OFF), bridge 1 starts raising (ON -> OFF), bridge 2 ignores signal (already performing OFF -> ON).

[Nil Eyeglazed]

Or use z-levels and retracting bridge vs drawbridge to control access.

Code: [Select]

RB_____
_/     \_

Path granted when open, blocked when closed; opposite behavior of traditional drawbridges