- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
Difference between revisions of "User:Jfredett"
(→Ideas) |
|||
| Line 34: | Line 34: | ||
I'd really like to see some kind of ability to hook gear assemblies to lever states in both directions. As it stands now, you can connect a lever to connect/disconnect gear assemblies. I'd really like to go from gear assemblies back to some kind of switch. This would make doing [computing] a bit easier, since rather than using the pump/plate method. I find that this is typically unreliable as a means of controlling things with logic gates, since they can get overpushed/whatever. There is some ability to protect against this with flipflops, since you could simply send the same signal to the "set" gate repeatedly without changing the state of the flipflop, and send the reset manually, but this requires ''even more'' parts and space, making any real system generally prohibitively expensive. Basically, I think putting in a "connect lever to state of gear assembly" option would be _brilliant_, so that when the gear assembly is powered, the lever is in the green (pointing right) position, when it is unpowered, it is in the negative position. Heck, even allowing levers to just connect to power, with the same semantics, would make life ''much'' easier. | I'd really like to see some kind of ability to hook gear assemblies to lever states in both directions. As it stands now, you can connect a lever to connect/disconnect gear assemblies. I'd really like to go from gear assemblies back to some kind of switch. This would make doing [computing] a bit easier, since rather than using the pump/plate method. I find that this is typically unreliable as a means of controlling things with logic gates, since they can get overpushed/whatever. There is some ability to protect against this with flipflops, since you could simply send the same signal to the "set" gate repeatedly without changing the state of the flipflop, and send the reset manually, but this requires ''even more'' parts and space, making any real system generally prohibitively expensive. Basically, I think putting in a "connect lever to state of gear assembly" option would be _brilliant_, so that when the gear assembly is powered, the lever is in the green (pointing right) position, when it is unpowered, it is in the negative position. Heck, even allowing levers to just connect to power, with the same semantics, would make life ''much'' easier. | ||
| + | |||
| + | === Lever connections === | ||
| + | |||
| + | It'd be ''super'' if we cold just issue a "connect to" order, and then switch to a "look" or "query" mode and choose what we want manually instead of dealing with the long list. Also, when we have issued orders to connect to something, it should say so in an obvious manner (change the color of the object?) | ||
=== Washout Defense === | === Washout Defense === | ||
TBA | TBA | ||
Latest revision as of 23:47, 17 August 2009
Fortress Logs[edit]
Being a Star Trek fan, I thought it might be fun to keep a "Captain's Log" -- from the perspective of my Expedition Leader, The dates correspond to actual dates I played, along with timestamps of when I took the notes (more or less). The dates are in mmddyy, 24hourtime format, a entry marked with only a time indicates a supplemental log.
Current Fortress[edit]
Endokodshith "Atticclams"[edit]
A new fortress, again with a Magma Pipe and an Underground River, located in a Wilderness Woodland.
Old Fortresses[edit]
Rirassodel "Greatershield"[edit]
This is the first fortress I started keeping logs on. UG River and Mag Pipe are on the map (somewhere), sparse trees and IIRC I'm in a serene area. Sandy area easily accessible (for once... I can't tell you how many times I have had to hunt for arable land for the early fortress farm...
Play style[edit]
I tend to play till I screw something up or the game crashes -- something is amiss with my version, and pressing F11 to go to fullscreen causes a game crash. I occasionally do silly things, like drop cut a "Helm's Deep" into the side of whatever mountain I start near -- effectively caving in a large, sheer, straight cliff on three sides. I had been playing a fortress like that, but it crashed as I was about to finish the plumbing for a (if I do say so myself) brilliant plumbing system, see the ideas section for more info on that. Largely my interest is less in military and fighting and more in interesting defense systems. Among my favorites is the washout technique, I don't know if someone has come up with that idea before, but it's pretty neat.
Ideas[edit]
Some fun ideas and suggestions for future DF stuff.
Most of this is TBA, you have been warned.
Plumbing[edit]
Computing[edit]
I'd really like to see some kind of ability to hook gear assemblies to lever states in both directions. As it stands now, you can connect a lever to connect/disconnect gear assemblies. I'd really like to go from gear assemblies back to some kind of switch. This would make doing [computing] a bit easier, since rather than using the pump/plate method. I find that this is typically unreliable as a means of controlling things with logic gates, since they can get overpushed/whatever. There is some ability to protect against this with flipflops, since you could simply send the same signal to the "set" gate repeatedly without changing the state of the flipflop, and send the reset manually, but this requires even more parts and space, making any real system generally prohibitively expensive. Basically, I think putting in a "connect lever to state of gear assembly" option would be _brilliant_, so that when the gear assembly is powered, the lever is in the green (pointing right) position, when it is unpowered, it is in the negative position. Heck, even allowing levers to just connect to power, with the same semantics, would make life much easier.
Lever connections[edit]
It'd be super if we cold just issue a "connect to" order, and then switch to a "look" or "query" mode and choose what we want manually instead of dealing with the long list. Also, when we have issued orders to connect to something, it should say so in an obvious manner (change the color of the object?)
Washout Defense[edit]
TBA