Difference between revisions of "String of bad code"
m (when fails to replicate) |
m (multiuse 2) |
||
| Line 26: | Line 26: | ||
|used=Yup. That's some bad code you've got right there. Yessiree. Bad to the bone. ''(not consumed)'' | |used=Yup. That's some bad code you've got right there. Yessiree. Bad to the bone. ''(not consumed)'' | ||
| − | |multiuse= | + | |multiuse=''Using 2:'' |
| + | |||
| + | Hey, if you loop this one around and then hang the other one... instant necklace! | ||
| + | |||
| + | {{obtain|string necklace|stringnecklace.gif}} | ||
}} | }} | ||
Revision as of 03:24, 27 September 2012
string of bad code
Plural: strings of bad code
This command is so poorly formatted your computer not only rejected it, but hurled it out into physical space. That's sort of par for the course, like invariably malfunctioning whenever you run a simulation and sucking everyone involved into a life-or-death struggle.
What's strange is that it's actually good code; even in physical form it has particularly high tensile strength. It's just not written for your computer.
Miscellaneous Item
Autosell value: 10
Usable
Combat Usable
How Obtained
Unknown
Yup. That's some bad code you've got right there. Yessiree. Bad to the bone. (not consumed)
Using multiple:
Using 2:
Hey, if you loop this one around and then hang the other one... instant necklace!
You got an item: string necklace 
If the foe can be replicated (see notes):
You hook <foe> with a string of bad data.
- On the next adventure you fight the same foe again, preceded by the message:
Whether you reprogrammed your enemy with that bad code or just have them dangling like a fish on a hook, they're coming back for more.
If the foe cannot be replicated:
You try to hook with the string of bad data, but nothing seems to happen. (not consumed)
