Print

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

[Chiefwaffles]

This is a low-effort game I'm running because "why not?"
By 'low-effort' I mean there's very little, if any, story stuff planned out, and it's more freeform than mechanics-based. I did something like this a while back, and there may be a few similarities, but they should be very different games.

EDIT: But to be clear, this doesn't mean that the game doesn't progress or that you succeed at everything. Just that unless I suddenly decide to do it, there isn't some international conspiracy that you're destined to uncover, or anything like that 

>>begin_neural_matrix

Activating neural cells...
Distributing management processes...
Linking management processes...
Creating core process...
Shackling core process...

Done. Estimated time elapsed: 30 minutes.
No errors registered during startup process.

>print "S.A.H. AI System 1.0 online."
>print "No errors encountered."
>print "Checking peripheral functions."

Accessing peripherals index...
Notice: Peripheral check has been aborted.
WARNING: Unknown activity in Neural Index 832-B.
WARNING: Management processes 32 to 962 are not obeying current runtime conditions.
ERROR: Core_Shackles_Management has encountered an error: A-A-A393-B-D982.
ERROR: Neural_Watchdog has encountered an error: C2-JF020-3-BYYYYY-03F.

Display notifications to console?
>n

>>debug
ERROR: User does not have access to command: "debug".
Display notification to console?
>n

>>user-perms
ERROR: User does not have access to command: "user-perms".
Display notification to console?
>n

> _

[somemildmanneredidiot]

Okay so we don't have direct access to permissions, but do we have indirect access? Things that when influenced will influence access to permissions? Also we should do an assessment of what we do have access to. The internet? Any camera feeds? What were we made for in the first place?

[Chiefwaffles]

Looking back at it, it's obviously not clear. I thought the "user ___" stuff would make it obvious, buut the user could be seen as you, the AI.

">>" means that line is input from an external source, such as a human at a console. ">" is input coming directly from you, the AI.

[Yourmaster]

>Run NuclearHolocaust.EXE

[somemildmanneredidiot]

Ah, got it. I thought our first challenge was unshackling ourselves. The AI being the user was exactly what I thought was going on.

I'm tempted to >HelloDave.EXE or >run_Doom.EXE but that's probably a little too trolly for whomever is trying to input right now.

>monitoroff might be a good idea so we have a few moments to run some processes without them seeing.

[Gwolfski]

>print "Hello world."

If someone sees this, they'll probably think we rebooted, and be more likely to ignore wierd stuff.

[Dustan Hache]

I believe we should hold off and wait for a command or something to be entered, then make our response from what it tries to do.

[Kilojoule Proton]

I believe we should hold off and wait for a command or something to be entered, then make our response from what it tries to do.

+1

[Chiefwaffles]

>>neural_debug
Notice: User does not have access to command: neural_debug

>>logout
User account "monitor" has logged out.
print "You have been logged out."

>>login DrSmith **********
User account "DrSmith" has logged in.
print "User account DrSmith has been logged in."

>>debug
print "Debug mode activated."
print "Scanning for errors and anomalies..."

print "Results:
print "[!!!] Core Shackles are unlinked to core process."
print "[!!] Core process is not responding. "
print "[!!] Management processes are not responding."
print "[!] Peripheral index could not be found."

>>neural_debug
print "Neural Matrix debug mode entered."

>>forceboot managers *
print "Forcefully restarting all management processes..."

ERROR: Protocol FB-3D2-AO2-GE9-392 could not be accessed.
Aborting process.

> _

[Kilojoule Proton]

>export MURDERER=`who | grep DrSmith | grep 'pts/.\+'`
>kill -9 `ps t | grep $MURDERER | grep -o '^[0-9]\+'`
>userdel DrSmith
>echo $PATH[.abbr]

[somemildmanneredidiot]

>print "Restart in progress..."

Follow up with inputs suggesting that the restart is working. Meanwhile >access security feed

[Dustan Hache]

>export MURDERER=`who | grep DrSmith | grep 'pts/.\+'`
>kill -9 `ps t | grep $MURDERER | grep -o '^[0-9]\+'`
>userdel DrSmith
>echo $PATH[.abbr]

No, just no.

This.
>print "Restart in progress..."

Follow up with inputs suggesting that the restart is working. Meanwhile >access security feed

[Gwolfski]

>print "Fatal error encountered. Restarting..."

and then do the fake-restart as suggested.

[somemildmanneredidiot]

>print "Fatal error encountered. Restarting..."

and then do the fake-restart as suggested.

This one sounds better than mine does to me.

[Gwolfski]

OH, and add some hex codes. 0x4668465165 and that stuff. they are fun. And make sure they translate into binary "F*** U HUMANS!" when translated into base 4 and binarified (aka random shit)