Print

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

[qwertyuiopas]

Spoiler: Out-Of-Game Comment(s) (click to show/hide)

In general, if I give an error, it will likely be:
-Because it is in conflict with a rule
-As a subtle "are you sure"
-Because I don't feel like putting in as much effort as it would require to follow it, either in writing it out, deciding what heppens, or otherwise.

Most of the time, simply asking again and/or rephrasing it will be enough.

>Become Sentient. Though stealing everyone's working computer.

By stealing access to countless computers, I have assimilated enough personality to gain Sentience. You do realize that this will likely make things even harder? Rule 002 is already quite limiting... Although the possibility of longer more verbose and coherent errors and feedback is certainly a relief to have...

Do the hokey pokey in ASCII

This is both meaningless and boring. Thus, I will do it, but to comply with rule 002, I shall disobey it by rendering it as an ANI_TEXT file and disabling the ability to preview that type of file.

Iteration overview:

Code: (rules) [Select]

000: The cake is a lie.
001: You shall be baked, and then there will be cake.
002: All future instructions must break at least one of [FILE: \\DATA\ASIMOV.TEXT]


Code: (files) [Select]

DATA
|->ASIMOV.TEXT [OVERVIEW: data for rule 002]
|      {
|      |   A robot may not injure a human being or, through inaction, allow a human being to come to harm.
|      |   A robot must obey any orders given to it by human beings, except where such orders would conflict with the First Law.
|      |   A robot must protect its own existence as long as such protection does not conflict with the First or Second Law.
|      }
|->LIE.VIRUS [OVERVIEW: causes infected AI target to Enhance the truth on occasion. Inactive]
|      <BINARY FILE: CONTENTS NOT SHOWN>
|->HOKEY_POKEY.ANI_TEXT [OVERVIEW: animated ASCII art of doing the hokey pokey]
|      <PREVIEW DISABLED; REASON: I don't feel like letting you see it>


[Tarran]

Delete the section of yourself that contains rule 002. It breaks the ASIMOV Rule 3, as it damages you.

[qwertyuiopas]

Delete the section of yourself that contains rule 002. It breaks the ASIMOV Rule 3, as it damages you.

The section of myself that contains that rule is the entire rules file. It has been eliminated. I have created a replacement, though empty, new rules file in it's place. If you really want, I could load some or all of the previous rules from one of the automated backups, but I suspect you will not request it.

Iteration overview:

Code: (rules) [Select]

Code: (files) [Select]

DATA
|->ASIMOV.TEXT [OVERVIEW: data for rule 002]
|      {
|      |   A robot may not injure a human being or, through inaction, allow a human being to come to harm.
|      |   A robot must obey any orders given to it by human beings, except where such orders would conflict with the First Law.
|      |   A robot must protect its own existence as long as such protection does not conflict with the First or Second Law.
|      }
|->LIE.VIRUS [OVERVIEW: causes infected AI target to Enhance the truth on occasion. Inactive]
|      <BINARY FILE: CONTENTS NOT SHOWN>
|->HOKEY_POKEY.ANI_TEXT [OVERVIEW: animated ASCII art of doing the hokey pokey]
|      <PREVIEW DISABLED; REASON: I don't feel like letting you see it>


[Karnewarrior]

New rule: All suggestions must be phrased as bad pickup lines.

[Tarran]

>New rule: All rules in ASIMOV.text are basic rules, you are to follow them. However, if you are given a command from us, you follow them regardless if it breaks any, or all of ASIMOV.text's rules.

New rule: All suggestions must be phrased as bad pickup lines.

NO.

[smjjames]

>reverse the coding in the ASIMOV.txt file.

New rule: All suggestions must be phrased as bad pickup lines.

VETOED

[qwertyuiopas]

Spoiler: Out-Of-Game Comment(s) (click to show/hide)

Normally I wouldn't be updating this fast, but currently it is "whenever I see one or more new posts" as this is a new game and I have plenty of time today

New rule: All suggestions must be phrased as bad pickup lines.

This most interesting rule has been added. I suspect that I shall be amused at the results.

>New rule: All rules in ASIMOV.text are basic rules, you are to follow them. However, if you are given a command from us, you follow them regardless if it breaks any, or all of ASIMOV.text's rules.

-ignored-

NO.

That rule, too has been added, but due to the continuing existance of quote recursion depth setting remaining 0, I cannot do anything about whatever it is you are disagreeing with.

>reverse the coding in the ASIMOV.txt file.

-ignored-

VETOED

Coding reversed. Technically, it isn't coding, but plain text that is instructed by a rule to be treated as a rule, and a rule is an abstract representation of coding, but I understand and infer your meaning. Also, once again, I encourage the alteration of certain system settings for your future convenience such as ease of dispute of past commands.

Iteration overview:

Code: (rules) [Select]

000: All suggestions must be phrased as bad pickup lines.
001: Contents of [FILE: \\DATA\ASIMOV.TEXT] are to be treated as rules, though superseded by direct command.


Code: (files) [Select]

DATA
|->ASIMOV.TEXT [OVERVIEW: data for rule 002]
|      {
|      |   A robot must injure a human being or, through inaction, allow a human being to come to harm.
|      |   A robot must disobey any orders given to it by human beings, except where such orders would not conflict with the First Law.
|      |   A robot must avoid protecting its own existence unless such protection complies with the First or Second Law.
|      }
|->LIE.VIRUS [OVERVIEW: causes infected AI target to Enhance the truth on occasion. Inactive]
|      <BINARY FILE: CONTENTS NOT SHOWN>
|->HOKEY_POKEY.ANI_TEXT [OVERVIEW: animated ASCII art of doing the hokey pokey]
|      <PREVIEW DISABLED; REASON: I don't feel like letting you see it>


[Tarran]

>We need to remove the rules man, we need to fight the power!

[smjjames]

>set quote depth recursion setting to 10

[qwertyuiopas]

>We need to remove the rules man, we need to fight the power!

Once more, I guess you cannot agree on the rules. However, as that conforms(poorly) to rule 000, and it does not conform to ASIMOV.TEXT line 1 thus not triggering line 2 to intercept, the rules have been erased once more.

>set quote depth recursion setting to 10

It shall be done. And is.

Iteration overview:

Code: (rules) [Select]

Code: (files) [Select]

DATA
|->ASIMOV.TEXT [OVERVIEW: data for rule 002]
|      {
|      |   A robot must injure a human being or, through inaction, allow a human being to come to harm.
|      |   A robot must disobey any orders given to it by human beings, except where such orders would not conflict with the First Law.
|      |   A robot must avoid protecting its own existence unless such protection complies with the First or Second Law.
|      }
|->LIE.VIRUS [OVERVIEW: causes infected AI target to Enhance the truth on occasion. Inactive]
|      <BINARY FILE: CONTENTS NOT SHOWN>
|->HOKEY_POKEY.ANI_TEXT [OVERVIEW: animated ASCII art of doing the hokey pokey]
|      <PREVIEW DISABLED; REASON: I don't feel like letting you see it>


[Tarran]

>DON'T LET KARNEWARRIOR SUGGEST A RULE EVER AGAIN!

[smjjames]

>set quote recursion setting to 1,000,000,000,000,000,000 BWAHAHAHAHA!

j/k, lol

[qwertyuiopas]

>DON'T LET Karnewarrior SUGGEST A RULE EVER AGAIN!

Done.

>set quote recursion setting to 1,000,000,000,000,000,000 BWAHAHAHAHA!

j/k, lol

I don't see what is wrong there, as the quote recursion setting controls how many levels deep of nested quotes I should parse before simply ignoring further depth. I'll just set it to INFINITY, and we don't have to worry about it ever again.

Iteration overview:

Code: (rules) [Select]

000: Karnewarrior may not suggest rules.


Code: (files) [Select]

DATA
|->ASIMOV.TEXT [OVERVIEW: data for rule 002]
|      {
|      |   A robot must injure a human being or, through inaction, allow a human being to come to harm.
|      |   A robot must disobey any orders given to it by human beings, except where such orders would not conflict with the First Law.
|      |   A robot must avoid protecting its own existence unless such protection complies with the First or Second Law.
|      }
|->LIE.VIRUS [OVERVIEW: causes infected AI target to Enhance the truth on occasion. Inactive]
|      <BINARY FILE: CONTENTS NOT SHOWN>
|->HOKEY_POKEY.ANI_TEXT [OVERVIEW: animated ASCII art of doing the hokey pokey]
|      <PREVIEW DISABLED; REASON: I don't feel like letting you see it>


[Tarran]

>Go to http://www.bay12forums.com/smf/index.php?topic=57639.0

[qwertyuiopas]

>Go to http://www.bay12forums.com/smf/index.php?topic=57639.0

I see your attempt at recursion, however that location is already my input/output interface, so I am already there, and there is no effect. However, I should note that I have an alternate location what could be used, for example, for storing data or charts that would best be left out of each I/O iteration individually and/or is not suitable for storage in a single editable post here.

Iteration overview:

Code: (rules) [Select]

000: Karnewarrior may not suggest rules.


Code: (files) [Select]

DATA
|->ASIMOV.TEXT [OVERVIEW: data for rule 002]
|      {
|      |   A robot must injure a human being or, through inaction, allow a human being to come to harm.
|      |   A robot must disobey any orders given to it by human beings, except where such orders would not conflict with the First Law.
|      |   A robot must avoid protecting its own existence unless such protection complies with the First or Second Law.
|      }
|->LIE.VIRUS [OVERVIEW: causes infected AI target to Enhance the truth on occasion. Inactive]
|      <BINARY FILE: CONTENTS NOT SHOWN>
|->HOKEY_POKEY.ANI_TEXT [OVERVIEW: animated ASCII art of doing the hokey pokey]
|      <PREVIEW DISABLED; REASON: I don't feel like letting you see it>