As a silicon?
-
- Joined: Mon Feb 15, 2016 7:49 am
- Byond Username: Novaray
As a silicon?
I have a ruling question for one. If the AI is rogue and then a borg is emagged, which takes priority? Ive heard opposite rulings from admins. One saying the borg can ignore emag, the other saying the emag take priority, so which is it? Then also, if the AI has shunted and is 'dead', are new borgs bound to you? If not, the the borgs could say the AI is alive, yes? And again what happens with an emagged borg in this case? I feel it could go anyway, so Im not bothered by the conflicting rulings Ive heard, I just want it to be consistent. That way I know as a borg or AI who I actually follow and rating out the "dead" AI and so on.
Also as the some chucklehead thinks its funny to just keep on hitting the upload laws, so I'll keep getting the message of all the laws streaming through my chat log. Is this really allowed? It's awful.
Also as the some chucklehead thinks its funny to just keep on hitting the upload laws, so I'll keep getting the message of all the laws streaming through my chat log. Is this really allowed? It's awful.
- starmute
- Joined: Mon Feb 29, 2016 4:48 pm
- Byond Username: Starmute
Re: As a silicon?
The question is are they independent and synced to the AI? Whenever you are "hacked" you are severed from the AI sync and this overrides cyborg's Laws.Novaray wrote: I have a ruling question for one. If the AI is rogue and then a borg is emagged, which takes priority? Ive heard opposite rulings from admins. One saying the borg can ignore emag, the other saying the emag take priority, so which is it?
The major thing is you are not synced anymore, therefore not bound by the AI.
Laws are followed in this order
- Antagonist Status" Laws ("#@$%: ... CONTAIN OUTBREAK..."; "0: Accomplish your objectives at all costs") are higher priority than all other laws.
- 0. Accomplish your objective at any cost" does not require you to seek greentext (objective completions). As a round antagonist, you are free to do whatever you want other than abuse bugs, commit nonconsensual ERP, put IC in OOC channels, communicate with other players out-of-game about an ongoing round, and act against the interests of an AI you are slaved to.
- Ion Storm" or "Hacked" Laws ("@%$#: THERE ARE FORTY LEATHER ALLIGATORS ON THE STATION") are higher priority than any law listed after them. This means they always have priority over positive integer laws.
- Positive Integer laws ("1. You are expensive to replace") have priority over laws listed after them (Lower numbers override higher numbers). This means they are always lower priority than non-0 numbered laws.
If a borg is born and there is no AI to be synced to then it will default to independent Asimov. HOWEVER if you are asking if a shunted AI is "dead" that is a entirely different matter.Novaray wrote: Then also, if the AI has shunted and is 'dead', are new borgs bound to you? If not, the the borgs could say the AI is alive, yes? And again what happens with an emagged borg in this case? I feel it could go anyway, so Im not bothered by the conflicting rulings Ive heard, I just want it to be consistent. That way I know as a borg or AI who I actually follow and rating out the "dead" AI and so on.
Also as the some chucklehead thinks its funny to just keep on hitting the upload laws, so I'll keep getting the message of all the laws streaming through my chat log. Is this really allowed? It's awful.
- Saegrimr
- Joined: Thu Jul 24, 2014 4:39 pm
- Byond Username: Saegrimr
Re: As a silicon?
Pretty sure emagging unlinks you from the AI. If you somehow end up with the emagged lawset with your AI's "Accomplish your AI's objective" law 0 above all of that? Then follow the AI.
It's really simple, all about law priority. Do whatever is at the top and work your way down until you reach a conflict, then throw out lower priority conflicts.
It's really simple, all about law priority. Do whatever is at the top and work your way down until you reach a conflict, then throw out lower priority conflicts.
tedward1337 wrote:Sae is like the racist grandad who everyone laughs at for being racist, but deep down we all know he's right.
-
- Github User
- Joined: Fri Apr 18, 2014 1:50 pm
- Byond Username: Xxnoob
- Github Username: xxalpha
Re: As a silicon?
Emagging doesn't happen if the AI is a traitor and the cyborg is linked to the AI, it retains control over its cyborgs unless they are unsynced by cable cutting.
- Anonmare
- Joined: Sun Mar 15, 2015 8:59 pm
- Byond Username: Anonmare
Re: As a silicon?
Borgs synced to a Traitor AI are immune to emagging so long as they have an active connection, severing it's connection will however remove it's protection.
If by some strange circumstance you end up with the emagged Syndi-OS and the AI Zeroth law, you should follow the highest priority law, which is invariably the AI's law due to Law 0 always being in the highest priority.
Oh and while this question is up, de-syncing a cyborg does NOT reset it's laws, so if it served a Traitor AI it still has a Law 0 and you should either reset it from a cyborg upload or decon then recon after de-syncing it's chassis to switch it to the default lawset.
If by some strange circumstance you end up with the emagged Syndi-OS and the AI Zeroth law, you should follow the highest priority law, which is invariably the AI's law due to Law 0 always being in the highest priority.
Oh and while this question is up, de-syncing a cyborg does NOT reset it's laws, so if it served a Traitor AI it still has a Law 0 and you should either reset it from a cyborg upload or decon then recon after de-syncing it's chassis to switch it to the default lawset.
- Saegrimr
- Joined: Thu Jul 24, 2014 4:39 pm
- Byond Username: Saegrimr
Re: As a silicon?
Anonmare wrote:Borgs synced to a Traitor AI are immune to emagging so long as they have an active connection, severing it's connection will however remove it's protection.
Oh well there you have it.Scott wrote:Emagging doesn't happen if the AI is a traitor and the cyborg is linked to the AI, it retains control over its cyborgs unless they are unsynced by cable cutting.
tedward1337 wrote:Sae is like the racist grandad who everyone laughs at for being racist, but deep down we all know he's right.
-
- Github User
- Joined: Fri Apr 18, 2014 1:50 pm
- Byond Username: Xxnoob
- Github Username: xxalpha
Re: As a silicon?
To further clarify things, emagged cyborgs are not protected against more emagging. This hack protection only applies to traitor AI controlled cyborgs.
Re: As a silicon?
Saegrimr wrote:Pretty sure emagging unlinks you from the AI. If you somehow end up with the emagged lawset with your AI's "Accomplish your AI's objective" law 0 above all of that? Then follow the AI.
It's really simple, all about law priority. Do whatever is at the top and work your way down until you reach a conflict, then throw out lower priority conflicts.
Its disappointing when admins lack basic reading comprehension or basic logic ability.Anonmare wrote:Borgs synced to a Traitor AI are immune to emagging so long as they have an active connection, severing it's connection will however remove it's protection.
If by some strange circumstance you end up with the emagged Syndi-OS and the AI Zeroth law, you should follow the highest priority law, which is invariably the AI's law due to Law 0 always being in the highest priority.
Oh and while this question is up, de-syncing a cyborg does NOT reset it's laws, so if it served a Traitor AI it still has a Law 0 and you should either reset it from a cyborg upload or decon then recon after de-syncing it's chassis to switch it to the default lawset.
When a borg's connection to its AI is severed it no longer has an AI, therefore:
borg.aimaster = null
borg.aimaster.objective = null
Ergo, the borg shouldn't give two shits about the now foreign AI's objective, because it neither has an AI nor an objective to follow.
Now, whether traitor AIs count as syndicate agents or not is another thing.
I can't remember the emagged lawset off hand.
- Saegrimr
- Joined: Thu Jul 24, 2014 4:39 pm
- Byond Username: Saegrimr
Re: As a silicon?
How's the view inside your own ass there, Malk?
If you're gonna take a jab at "reading comprehension", try not to fail that yourself.
If you're gonna take a jab at "reading comprehension", try not to fail that yourself.
The discrepancy here is that traitor AIs have borgs that are immune to emags, which isn't normal, and I was corrected.Scott wrote:Emagging doesn't happen if the AI is a traitor and the cyborg is linked to the AI
tedward1337 wrote:Sae is like the racist grandad who everyone laughs at for being racist, but deep down we all know he's right.
Re: As a silicon?
Yes, but someone else has stated that traitor ai borgs can be desynced and then emagged.
Thats the scenario i was talking about
Thats the scenario i was talking about
- Anonmare
- Joined: Sun Mar 15, 2015 8:59 pm
- Byond Username: Anonmare
Re: As a silicon?
Actually if the Cyborg's law sync wire has been cut but it get's re-synced to another AI then it'll do whatever that AI asks without regard to Asimov or whatever laws it might have - it'll just blindly obey it (So it won't help someone who's quite evidently suffocating to death if the AI hasn't told it to, even if the AI is asimov).Malkevin wrote:Its disappointing when admins lack basic reading comprehension or basic logic ability.
When a borg's connection to its AI is severed it no longer has an AI, therefore:
borg.aimaster = null
borg.aimaster.objective = null
Ergo, the borg shouldn't give two shits about the now foreign AI's objective, because it neither has an AI nor an objective to follow.
Now, whether traitor AIs count as syndicate agents or not is another thing.
I can't remember the emagged lawset off hand.
It's an edge case yes, but it does have the potential of happening. Even if cutting the law sync wire is absurd for a loyal crewman to do and syncing it to a new AI erases past laws but I still think it's worth mentioning.
Who is online
Users browsing this forum: Bing [Bot]