Love the update and layout improvement, thank you!
I can add data from FNIX Rising DLC as well but it would be a spoiler to every console player since they don’t have that DLC yet. Then again, this whole topic is one big spoiler if you haven’t finished the game.
Edit: Additional data from FNIX Rising added.
With all due respect: why the bloody Tank has this topic not been pinned?
It is, without a shred of doubt, the nigh most important post EVER written in the history of GZ…
PIN THIS, DARN IT!!!
Pretty, pretty please? *puppy eyes *
Well, since this topic does contain a lot of GZ’s lore and is helpful to anyone to make sense of the story , i guess it could be pinned, yes.
BAH, be honest.
It were the eyes.
Thank you, miss.
credit to pufty
Who unpinned this?
Please repin!
It is very relevant information for many, unpinning this is just not right.
Thank you.
No-one.
Topic is still pinned, sort-of.
Explanation + fix
Searching around official Discourse help forum and i found the reason why pins act as “read once” rather than “always”;
I think a lot depends on how you think of Pinned.
If like last century’s forums, you might think Pinned would be a kind of “sticky post” and always listed first.
If like Discourse, Pinned is more like “should be read at least once”.True, if Pinned are used more as an “easy to find reference topic”, having them become automatically unPinned doesn’t help, If members want to keep it readily available they need to use the topics Pin button or Bookmark the topic. (or be good at using Search)
The problem with Pinned topics to consider is that they occupy valuable space - the beginning of topic lists.
If you have too many of them, they “bump” often more active topics down the list.If the unPin when read isn’t a good fit for a forum there is an Admin Setting to disable it from happening.
No “default” will ever suit every forum. That’s why they’re options.
source: https://meta.discourse.org/t/pinned-topic-how-do-we-always-keep-it-pinned/46369/5
As far as “options” go, under user Profile -> Preferences -> Interface, there is “Automatically unpin topics when I reach the bottom.” setting. Unchecking the setting should not unpin pinned topics you’ve read (scrolled to the bottom).
Since this setting is enabled by default, each user needs to manually disable it. Also, it may take some time before effect kicks in (24h or so).
I’ve unchecked this setting and so far, all pinned topics remain pinned for me.
True, but it is a work of reference, which could be visited many a time to look up events, for instance in discussion.
But, I will leave this at your discretion, good miss.
Here however, it shows as unpinned for some weird reason, which is why I replied.
Thank you very much, miss, for the explanation.
Click on the pin to get it pinned again.
OOOH, that is a neat trick.
Ah, I love magic. XD
Keeps unpinning…
Any way around this?
Did you uncheck the setting in your profile settings?
I actually have, I put it on, just checked again…
Deactivated both Adblocks, I activated it, de-activated it, turned both AB back on.
Maybe one of them that buggered it up?
Hopefully it’ll work now and stay pinned.
Umm dude…
The “laws of robotics” isn’t a thing.
It’s something a science fiction writer made up for his stories.
It’s not like you can’t build a robot without programming those laws into them.
They’re completely irrelevant.
Whether you want to call them robots or machines, those laws are no actual laws.
So they’re not “suppressing” anything. They simply don’t have anything like that programmed into them.
That’s right.
Isaac Asimov had set it up then. Nevertheless, they have a certain relevance.
Of course, when I program a six-axis articulated arm robot that takes the drive shaft of a car from a turntable and puts it in another processing station, it doesn’t need Asimov’s robot laws, but only a safety switch that switches it off when I open the housing, otherwise I will slain by the robot (machine safety law).
But if I put this articulated arm robot on a self-propelled mount and instead of a gripper mount a MG on the arm, install a control (which is ultimately only programmed) and give this robot certain freedom in its actions, one should think about these laws, otherwise I’ll have my own combat robot on my tail.
IRL already happened when the American Army tested it in field conditions.
Quote Wikipedia (germ. Side)
The SWORDS robots were decommissioned in April 2008 by the US Department of Defense. After the weapon arm had rotated in several incidents, although this was not intended in the respective situation, the robots were classified as unsafe for the time being and the field mission was canceled. Nobody was injured in the incidents. [1]
End of quote (source Wikipedia German)
Although, the Machines in Generation Zero are well past the early prototype stage. They are fully developed war machines, able to be remote controlled and commit to logical problem-solving. So, at some point, someone at FOA most likely threw any thoughts of moral obligations out the window. Probably due to the amount of funding they got from the military.
Story spoiler below.
Summary
The Machines were never meant to operate on their own, but rather to be controlled at a distance, similar to today’s drone technology. At first with computer equipment, and at it’s last prototype, with a direct neural link. When FNIX became self aware, the first thing it probably did was to merge both it’s neural network, and the computerized to spread it’s influence to all Machines connected to it.
Thank you for the explanation,
I thought something like that, that on the one hand the robots are controlled by someone, similar to a drone. However, I thought that they have their own rudimentary, artificial intelligence to e.g. Avoiding obstacles, tracking down an enemy, or tracking targets, similar to Mars rovers. But that does not seem to be the case. This means that they are completely controlled by FNIX, which would also explain the delayed reaction of the robots.
It is obvious that the person who developed the robots has thrown any moral concerns overboard.
interesting discussion