Hello all forum-goers,
I've just finished compiling and writing a mega list of all the manual commands I know. Unfortunately, I wrote it all up with 'Markdown' syntax because I had reddit in mind, so a straight-up copy-paste won't look very pretty. Also, that would double the amount of work I have to do to update it... So with that said, please forgive me for simply linking to it from this thread. If you really hate reddit, feel free to drop any useful information in this thread and I will see that it gets updated. If you really really hate reddit and refuse to even read it over there, I'm sorry.
z << Manual Command (http://www.reddit.com/r/Cogmind/comments/372yj8/z_manual_command/)
Still trying to get the schematics for those Biomechanical Wings... Soon...
Heehee! I've gotten schematics a lot, but actually fabbing things is a frustrating process. Not only do you need to get a schematic (which requires lots of hacking or scanalyzing), you need to load the schematic in the fabber (hack) and then start the build (really difficult hack). This is all assuming you were carrying at least a Med. Matter Storage Unit in your inventory and it was nearly full. Finally, you need to wait 50~100 turns for the process to complete. Ding! One item. Rinse repeat. Bleh.
Some item suggestions, based on what I've downloaded:
- Schematic(Lrn. Sensor Array)
- Schematic(Mic. Fission Core)
- Schematic(Adv. Signal Interpreter)
- Schematic(Powered Armor)
- Schematic(KE Penetrator)
- Schematic(Centrium Greatsword) ;)
- Schematic(Adv. Targeting Computer)
And for shits and giggles, someone needs to try:
- Schematic(B-99 Colossus)
Fabbers seem to have different tech levels though. They can't all produce high level items.
Someone really needs to help identify some drones, because twice now I've found a drone bay, but never figured out how to get drones...
None the less, I love watching these, I've successfully fabbed a mic. fission core. Still trying for those biomechanical wings though.
Quote from: ironpotato on May 26, 2015, 07:41:13 AM
Someone really needs to help identify some drones, because twice now I've found a drone bay, but never figured out how to get drones...
None the less, I love watching these, I've successfully fabbed a mic. fission core. Still trying for those biomechanical wings though.
Haha! Congrats! One time I got a Long-Range Sensory Array on my very first try on the Terminal I spawned next to. That was a good feeling. 'Course, what the game gives, the game takes, and an unavoidable fight with a single goblin turned into a fight with 8 goblins. gg -10
Uh, drones are super simple stuff. I take it you've found a Drone Bay? Equip it (it takes two Utility slots), online it, and wait two turns. Congrats! You have two cute little drones next to you. Use the 'o' key to give them orders (and '0' [that's zero] to give orders to both of them). Most people, I think, will be telling them to e'x'plore, whereupon they run away only to die in the next room to a group of goblins or swarmers. They aren't incredibly useful, especially since they always travel together. They'd be better if they at least when in separate directions.
Ahhh, that makes so much sense. I've been trying to find some alternate strategies, and I thought drones might be useful for a couple of them. I knew all the ordering commands, just wasn't sure how that whole obtaining drones spiel went.
Observed
Enumerate(Surveilance)
Shows up as [Surveliance Status], have no idea what it is, hack failed. All deployed watchers?
Speaking of drones, when drones are dead is there a way to build new ones, or drone bay is useless at this point?
Thanks! I'll update the reddit post. No idea on how to build more drones. I usually just launch them and ditch the part.
Recall(Squad) says is not a valid command.
Also, people, FWI, if you stop hacking before the trace is complete you can attempt again in 50 turns (The manual even says so). Playing it safe will make terminals last quite a bit.
Haha, thanks for checking that. I haven't done much research lately. Also, 50 turns isn't enough on the higher floors... I've reconnected after longer than that with there still being a shred of trace left.
You can always get a trace at the time of accessing after the first try (the manual says "subsequent connections are tested for detection before even the first hack."), but sometimes you don't, so as long as the trace isn't completed you can always try again in 50 more turns. Also, 25% trace means that most terminal commands won't make it go overboard (I have been hacking heavily and only one time this proved untrue) so you can do one command, fail spectacularly, and still leave the terminal operational.
Index(Machines) shows all machines on the map. It's glorious.
Scanalyzers can identify prototype parts.
A couple of more things: there is a Reinforcement kind of squad, so
Recall(Reinforcement)
Enumerate(Reinforcements)
Both tested and work.
Also Alert levels appear not to be per-floor as you say here, but rather persist from floor to floor, don't know if they drop overtime or not, but this bumps a lot the usefulness of Alert(Purge) before ascending further.
Aight! Updating the reddit post. And you're right, I should have known that about Alert(Purge).
Quote from: biomatter on May 25, 2015, 08:11:08 PM
Fabbers seem to have different tech levels though. They can't all produce high level items.
Yeah, you guys are getting schematics out of early Terminals that I thought you shouldn't have been able to. This will need to be fixed, so enjoy it while you can ;).
Quote from: biomatter on May 25, 2015, 08:11:08 PM
Ding! One item. Rinse repeat. Bleh.
This, however, is going to get better. In a not-so-distant release you'll be able to produce batches of parts, rather than one at a time.
Quote from: biomatter on May 26, 2015, 08:38:34 AM
They aren't incredibly useful, especially since they always travel together. They'd be better if they at least when in separate directions.
That's because they use the same exploration algorithm so they're unlikely to split if you launch them at the same time. You can either 1) tell one to explore and let the other one wait around a bit first or 2) let one explore randomly and manually instruct the second to head in a different direction,
then tell it to start exploring.
ohhhh im going to enjoy this....
hi everyone!
I love hacking
hey kyzrati I joined the forum after sending in my form, I need the alpha badge.
Welcome to the forums endlessblaze! Please take note of the fact that I only keep the reddit post updated - the one you see above is slightly out of date. As a matter of fact, I have to go touch it up right now.
If you haven't already, I highly suggest reading the manual. One thing I want to highlight is that manual commands suffer from a base -15% success penalty. With that information in mind, I would personally recommend treating indirect hacking as a side bonus if it works, but not something to focus on (unless you find Deep Network Scanners, that is). That's info I need to put in the guide...
already read it ;)
I am glad to see this though because I tried manual commands and I must have been typing them wrong.
Quote from: endlessblaze on May 30, 2015, 09:34:31 AM
hey kyzrati I joined the forum after sending in my form, I need the alpha badge.
Certainly, I do that in batches every day or two when I check the form data, but I'll go add yours now since you've asked and I know you.
And welcome! We have a lot more activity over here than on Bay 12 (since a number of the main Bay 12 players are here, too, anyway...), though it's nice to have the occasional conversation over there to bump that thread and let more people find the game!
thanks.
and yha I will probly carry on discussions in both forums. I already spend lots of time on bay12 anyways.
hehehehehh hahahahahhaha!
.....................................th commands still wont work for me. I always get unknown command
Things to check: Are you being case-sensitive? If you don't use a capital key when you are supposed to, it gets rejected. What kinds of commands are you trying to use? Also, are you using the right command at the right type of machine? All commands are specific to a type of machine - e.g. you can't use Terminal commands at a Scanalyzer.
Quote from: biomatter on May 30, 2015, 10:59:33 AM
Things to check: Are you being case-sensitive? If you don't use a capital key when you are supposed to, it gets rejected. What kinds of commands are you trying to use? Also, are you using the right command at the right type of machine? All commands are specific to a type of machine - e.g. you can't use Terminal commands at a Scanalyzer.
I don't know, I've had "Access(Main)" fail on me before (yes, using a Terminal). And I've input it just as I've typed it here.
Quote from: Draco18s on September 06, 2015, 05:42:32 PM
I don't know, I've had "Access(Main)" fail on me before (yes, using a Terminal). And I've input it just as I've typed it here.
By 'fail', do you mean the terminal failed to
recognize the command, or that the attempt didn't succeed? Manual commands are subject to the same chance-to-succeed they would have if they were a direct hack at that terminal, but with a -15% stacked on top. (this makes indirectly hacking Access(Main) very hard to successfully pull off without multiple hacking utilities)
Quote from: Adraius on September 06, 2015, 07:27:52 PM
Quote from: Draco18s on September 06, 2015, 05:42:32 PM
I don't know, I've had "Access(Main)" fail on me before (yes, using a Terminal). And I've input it just as I've typed it here.
By 'fail', do you mean the terminal failed to recognize the command, or that the attempt didn't succeed?
Former. "ACCESS(MAIN) NOT RECOGNIZED"
Quote from: Draco18s on September 06, 2015, 07:38:45 PM
Quote from: Adraius on September 06, 2015, 07:27:52 PM
Quote from: Draco18s on September 06, 2015, 05:42:32 PM
I don't know, I've had "Access(Main)" fail on me before (yes, using a Terminal). And I've input it just as I've typed it here.
By 'fail', do you mean the terminal failed to recognize the command, or that the attempt didn't succeed?
Former. "ACCESS(MAIN) NOT RECOGNIZED"
If so, that's a bug. Next time it happens, take a screenshot and post it in the bugs section. That said, I use indirect Access(Main) pretty often, and I've never had issues with it.
In theory this is impossible (and I've heard of many players using that command indirectly), so it would be a bug if you can confirm that nothing was mistyped (like you may have had an extra space at the beginning or end?).
If you see it again take that screenshot and drop it in the Bugs board, thanks!
Will do. I didn't capture it at the time because I wasn't able to confirm to myself that there wasn't a typo or that I'd misremembered the command.
I thought one time I had a similar error, but it's also possible that I was mistyping it somehow. Too long ago to remember now.
Is there a command that list all sentries on the map? Given that Sentries often guard stairs, knowledge of all sentries could be a poor man's Access(Main).
Btw, there's some commands for traps:
Traps(Locate)
- Shows the location of traps
Traps(Disarm)
- Disarms traps
Traps(Reprogram)
- Reprograms traps
Quote from: Happylisk on September 15, 2015, 07:01:21 AM
Is there a command that list all sentries on the map? Given that Sentries often guard stairs, knowledge of all sentries could be a poor man's Access(Main).
That's an interesting tactic. biomatter's list isn't 100% complete--there's also Enumerate(Security), but you'll find that it only works in the local area. Still, it's useful.
Quote from: Kyzrati on September 15, 2015, 08:08:54 PM
Quote from: Happylisk on September 15, 2015, 07:01:21 AM
Is there a command that list all sentries on the map? Given that Sentries often guard stairs, knowledge of all sentries could be a poor man's Access(Main).
That's an interesting tactic. biomatter's list isn't 100% complete--there's also Enumerate(Security), but you'll find that it only works in the local area. Still, it's useful.
With sensors, you get the locations of sentries very easily, and then it's a matter of just checking if they're on exits or not. This is one of the best uses for the optics item I think, because you must have LOS to the sentry to see if there is an exit or not.
Man, I've never used a manual command ever. I get they're the fancy-pants stuff, but I sort of file them as 'wringing everything possible out of the game' rather than playing-as-intended. But terminals tend to have so little to offer I might just have to start memorising the things after all.
A small wish: Terminals would stop blinking after they've cooled down; and/or that the blinking was at least related to cooldown. I keep trusting it and getting caught; manually counting turns is no fun and I lack the ability to wait because my laptop trackpad doesn't have a scroll wheel. :P
I should probably check what Deep Network Scans do too, come to think of it. I used one all last game for hacking... mostly on good faith. ;)
Quote from: Reiver on September 15, 2015, 11:13:46 PM
Man, I've never used a manual command ever. I get they're the fancy-pants stuff, but I sort of file them as 'wringing everything possible out of the game' rather than playing-as-intended. But terminals tend to have so little to offer I might just have to start memorising the things after all.
A small wish: Terminals would stop blinking after they've cooled down; and/or that the blinking was at least related to cooldown. I keep trusting it and getting caught; manually counting turns is no fun and I lack the ability to wait because my laptop trackpad doesn't have a scroll wheel. :P
I should probably check what Deep Network Scans do too, come to think of it. I used one all last game for hacking... mostly on good faith. ;)
Terminals do stop blinking when they've cooled down. You're not waiting long enough if they're still blinking.
Deep Network Scanners boost indirect hacks - manual hacks, the sort you have been avoiding!
Quote from: Reiver on September 15, 2015, 11:13:46 PM
But terminals tend to have so little to offer I might just have to start memorising the things after all.
I sometimes play purely by using direct hacks available from terminals, because if anything they're easier and the chance of success is a known variable.
Quote from: Reiver on September 15, 2015, 11:13:46 PM
A small wish: Terminals would stop blinking after they've cooled down; and/or that the blinking was at least related to cooldown. I keep trusting it and getting caught; manually counting turns is no fun and I lack the ability to wait because my laptop trackpad doesn't have a scroll wheel. :P
The waiting bit will be easier when I add the commands to "wait X turns" and "wait until something notable happens."
For now, if you don't have a scroll wheel why not just wait via the keyboard commands?